[Routing] fix static route reordering when a previous dynamic route conflicts #33363
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
OskarStark
reviewed
Aug 28, 2019
5e2992c to
cba3b62
Compare
nicolas-grekas
added a commit
that referenced
this pull request
Aug 30, 2019
…mic route conflicts (nicolas-grekas) This PR was merged into the 4.3 branch. Discussion ---------- [Routing] fix static route reordering when a previous dynamic route conflicts | Q | A | ------------- | --- | Branch? | 4.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | - | License | MIT | Doc PR | - Spotted while playing with the code. I confirm the test case is green on 3.4 too (but route reordering didn't exist then.) Commits ------- cba3b62 [Routing] fix static route reordering when a previous dynamic route conflicts
Merged
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.
Spotted while playing with the code.
I confirm the test case is green on 3.4 too (but route reordering didn't exist then.)