use route-recognizer 0.2 #607
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
|
@jbr this will prevent us from publishing new releases. Happy to release a new version tho! |
|
Published route-recognizer 0.2.0; think we can update to that now! |
|
Yay! That’s the result I was hoping for, but it sounded like that was unlikely to happen. Didn’t know whose call that was |
Fishrock123
approved these changes
Jun 19, 2020
jbr
force-pushed
the
use-route-recognizer-master
branch
from
3491675
to
5b4e111
Compare
jbr
force-pushed
the
use-route-recognizer-master
branch
from
5b4e111
to
439f4d6
Compare
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.
closes #593
refs http-rs/route-recognizer#40
This doesn't seem like an ideal solution, but this resolves the conflicting routes issue until there's a route-recognizer release