In some cases, the tool called xpath.select() with an object that was not a DOM element. With v0.0.33 of the xpath module, the error was silently ignored. But with v0.0.34 of the xpath module, this caused an error message like so:
Error: Context node does not appear to be a valid DOM node.
at XPath.evaluate (/Users/dchiesa/dev/apigeelint/node_modules/xpath/xpath.js:1359:19)
at XPathExpression.evaluate (/Users/dchiesa/dev/apigeelint/node_modules/xpath/xpath.js:4536:33)
at exports.selectWithResolver (/Users/dchiesa/dev/apigeelint/node_modules/xpath/xpath.js:4989:33)
at exports.select (/Users/dchiesa/dev/apigeelint/node_modules/xpath/xpath.js:4969:24)
at FlowPhase.getSteps (/Users/dchiesa/dev/apigeelint/lib/package/FlowPhase.js:50:21)
at /Users/dchiesa/dev/apigeelint/lib/package/Endpoint.js:306:35
at Array.forEach (<anonymous>)
at /Users/dchiesa/dev/apigeelint/lib/package/Endpoint.js:304:17
at Array.forEach (<anonymous>)
at Endpoint.getSteps (/Users/dchiesa/dev/apigeelint/lib/package/Endpoint.js:299:8)
The primary cause was sloppy initialization of child fields in Endpoint.js.
The problem was exacerbated by
a bug in the Flow.js module that treated all flows as sharedflows
In some cases, the tool called xpath.select() with an object that was not a DOM element. With v0.0.33 of the xpath module, the error was silently ignored. But with v0.0.34 of the xpath module, this caused an error message like so:
The primary cause was sloppy initialization of child fields in Endpoint.js.
The problem was exacerbated by