Jimmy Rishe
Jimmy Rishe
If you use namespaces correctly, you should be able to use a full path just fine: ```js /ns:html/ns:body/ns:child/ns:child2 ``` However, this library has an HTML mode which ignores namespaces on...
I will add it to the documentation. Thank you for pointing that out. The example in your pastebin doesn't work because the path is wrong. `head` and `title` are both...
Thank you for catching this. I agree that `SelectReturnType` makes more sense as the parameter type for `isArrayOfNodes`, but hopefully @cjbarth can sign off on that as well. One question...
I see. Yes, I can see why `XPathResult.STRING_TYPE` would fail at runtime. I hadn't noticed that line in your original comment and thought this was about the return type of...
On line 4588, this is called on `exports`: ```js installDOM3XPathSupport(exports, new XPathParser()); ``` And the `exports` function you indicated (which indirectly calls `XPathExpression#evaluate`) is attached to `exports`. Unlike `createExpression` and...
@lukeggchapman You're probably not the only person using `evaluate` so I think we should add it back. However, you may also want to consider using a [parsed expression](https://github.com/goto100/xpath/blob/master/docs/parsed%20expressions.md) (though this...
> We shouldn't have to work around it. There really isn't a need to work around it. Both `xpath.useNamespaces()` and the evaluator on parsed expressions accept a `Record` as a...
> So there would be no need to add that type back in? No, as I've said, it has already been in the .d.ts for 6 years, which means removing...
As explained [here](https://github.com/goto100/xpath/issues/36#issuecomment-188710185), there is no way to do what you're describing because it would not be compliant with the XPath 1.0 spec. There is no concept of a default...