Repository navigation
Treat a type's forbidden [!key] as an absent key #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have doubts about this line:
Why do we parse only the first selector? We have this code for a long time already. But let's put a comment to come back here later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, and it is worth a comment - added one at that line.
Short answer: the remaining selectors are alternative OSM spellings of the same type, while the style has to be evaluated against a single canonical tag set, and the first selector is it. E.g.
natural|water|intermittentmatches[natural=water][intermittent=yes],[natural=water][seasonal?],[natural=water][basin=detention]- all the same classificator type, so its tags are those of the first one.The consequence is a real blind spot: on the current
mapcss-mapping.csv, 202 of 1378 live rows list several selectors and 179 of those carry keys the first selector lacks (37 distinct ones:seasonal,basin,leaf_type,location, ...). A style rule testing such a key is silently false for that type if another type makes it a static tag, and an "Unknown tag" error otherwise. Nothing in the current styles does that, so this is latent rather than broken.So the comment states why only the first selector is used and leaves a TODO: either take the tags of every selector into account, or validate styles against them.