[WIP] feat(frontend): replace Reach Router v1 to React Router v6 #60
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
trivikr
changed the title
|
React Router v6.3.0 makes migration easier remix-run/react-router#8753 |
trivikr
force-pushed
the
use-react-router
branch
from
e8c810c to
5d1981a
Compare
trivikr
force-pushed
the
use-react-router
branch
from
4d7df84 to
19b4016
Compare
|
Superceded by #162 |
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.
Issue
Fixes: #26
Description
Switches from Reach Router v1 to React Router v6.
Testing
ToDo: Verify that routes work in the frontend.
Additional context
Refs: https://reactrouter.com/docs/en/v6/upgrading/reach#first-non-breaking-updates
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.