[Feature Request] Add XPath 2.0 support for XML response filtering
- Dominant language
- TypeScript
- Stars
- 40k
- Forks
- 2.4k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
Filtering XML responses with current **XPath 1.0** is total pain when lot of namespaces and default namespaces are present (i.e. VMWave API). Simple things like finding some element required ugly `//*[local-name() = 'tagName' ]` expressions.
**XPath 2.0** will allow much simpler expressions, you can use [this module](https://www.npmjs.com/package/xpath2.js) for upgrade.
I tried to do it myself, but haven't succeeded in building project, so it might be very helpful if someone could provide proper **Dockerfile** for app development and building.
Contributor guide
Research direction
Locate the current XPath 1.0 response-filtering implementation and the project’s development build setup. Evaluate the linked xpath2.js module and determine the compatibility and integration work required. Done means XML response filters support XPath 2.0 expressions and a Dockerfile can build the app for development.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100