jmespath / jmespath/jmespath.js
Update Readme.md with the rationale to use JMES Path vs JSON Path
Open
- Dominant language
- JavaScript
- Stars
- 847
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
Help me understand the shortcomings of IETF's JSON PATH that motivated you to create JMES Path. Clearly you leveraged many of the existing capabilities of JSON PATH.
Are you planning to submit this to IETF as a future version of JSON PATH to gain further adoption?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading Readme.md and the issue's questions about JMESPath versus JSON Path. Done means the README documents the rationale for JMESPath and addresses whether a future IETF submission is planned.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100