Rearrange the Policy API's speed limit example #482
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
Rearrange the Policy API's speed-limit examples from most specific to least specific, per the API's "order of operations" system.
jrheard
changed the title
|
@Karcass can you take a look at it and see if we should include wording clarifications to the order of operation spec? |
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.
Rearrange the Policy API's speed-limit examples from most specific to least specific, per the API's "order of operations" system.
Explain pull request
Right now, these two examples are in (least specific, most specific) order, which should mean that the "Venice Beach on weekend afternoons" Rule never applies to any vehicle, which seems like probably a mistake!
Is this a breaking change
Impacted Spec
Which spec(s) will this pull request impact?
policy