Parsing the slice selector #431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Parser is now tests with the official [JSONPath Compliance Test Suite](https://github.com/jsonpath-standard/jsonpath-compliance-test-suite)
- dot format was temporarily broken by doubling double quotes in labels
- Characters U+001A through U+001F were erroneously accepted unescaped. This is now a hard error.
V0ldek
force-pushed
the
v0ldek/separate-parser-crate
branch
from
cc66ea0
to
969bbc7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Short description
Parser support for slice selectors.
rqwill give an "unsupported feature" error, but it will be correctly parsed byrsonpath-syntax.Issue
Part of: #152 #116
Checklist
All of these should be ticked off before you submit the PR.
just verifylocally and it succeeded.