Docs: Add useMatch section in upgrade docs
#8280
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
jacob-ebey
approved these changes
Nov 8, 2021
mcansh
approved these changes
Nov 8, 2021
brophdawg11
added a commit
that referenced
this pull request
Mar 27, 2024
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Matt Brophy <matt@brophy.org>
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.
Our v5 migration docs do not mention that we replaced
useRouteMatchwithuseMatch(thanks to @eps1lon for pointing that out in #7133).This change begins to address it, though we should probably add a few code examples to make refactoring much simpler. I'm actually not 100% sure how to capture the nuance in a few situations, but I think this is better than nothing for now. Will circle back to that later after discussing with the team.