1094 Enhanced lookup expressions #1125
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
michaelhkay
added
XPath
Closed
|
The CG agreed to merge this issue at meeting 074 |
michaelhkay
force-pushed
the
1094-enhanced-lookup-expressions
branch
from
2ba18de
to
0ddaa64
Compare
michaelhkay
removed
the
Blocked
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.
Fix #1094
Lookup expressions (both deep and shallow) are enhanced in two ways:
(a) the syntax is extended to provide options that avoid flattening the result. For example
$V?pairs::Kdelivers the result as a sequence of key-value pairs.(b) a new KeySpecifier format is provided to filter the results by type. For example
$V??type(record(first, last))selects all items in the recursive content that are of typerecord(first, last). This replaces the previous syntax$V??*::record(first, last)which caused ambiguities with occurrence indicators.