Align KDL Query grammar with prose #507
Open
Conversation
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
The values() and props() accessors were only mentioned in the grammaer, with no explanation whatsoever about what they were supposed to do. The val() accessor required an argument in the grammar while the prose repeatedly mentions val() as equivalent to val(0).
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.
The values() and props() accessors were only mentioned in the grammaer, with no explanation whatsoever about what they were supposed to do.
The val() accessor required an argument in the grammar while the prose repeatedly mentions val() as equivalent to val(0).
This was mentioned in #489. The other changes proposed in that issue are a bit more impactful (rename
val()toarg(), introduce negation syntax, introduce equivalent to CSS:is()) so I wanted to get this one out of the way first.