jmespath: allow rhs_expression in a keyvalue - expression#687
Merged
danielaparker merged 1 commit intoMar 13, 2026
Merged
Conversation
… allow turning lhs_expression into e.g. a boolean using comparator
Owner
|
Thanks for contributing! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I tried the following jmespath expression and noticed that jsoncons_ext jmes_path could not compile the expression:
{value: foo.bar == 'baz'}because it expected '}' or ',' after the lhs_expression value part of a "key: value" and found a comparator ==, i.e. the start of a rhs_expression.
The jmespath grammar allows any expression as value in a multi select hash, so also those consisting of lhs and rhs part.