-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: Migrate react router from v3 to v6 #2828
Merged
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
cballevre
force-pushed
the
feat/migrate-react-router-from-v3-to-v6
branch
from
February 17, 2023 14:07
bc8d182
to
6a5604a
Compare
BundleMonFiles updated (5)
Unchanged files (14)
Total files change -74.6KB -1.59% Groups updated (4)
Unchanged groups (4)
Final result: ✅ View report in BundleMon website ➡️ |
cballevre
force-pushed
the
feat/migrate-react-router-from-v3-to-v6
branch
7 times, most recently
from
February 17, 2023 17:25
cddded3
to
7babba1
Compare
cballevre
force-pushed
the
feat/migrate-react-router-from-v3-to-v6
branch
from
March 10, 2023 16:36
720e40a
to
22c4a62
Compare
cballevre
force-pushed
the
feat/migrate-react-router-from-v3-to-v6
branch
3 times, most recently
from
April 3, 2023 11:23
abcd0e3
to
cd9397f
Compare
cballevre
force-pushed
the
feat/migrate-react-router-from-v3-to-v6
branch
2 times, most recently
from
May 23, 2023 08:46
42f28f3
to
ec57baa
Compare
Router history as is does not exist anymore in react-router-v6 - Remove router history from redux store - Use custom hooks instead of selectors using history from redux store - Remove toolbarContainer which has no purpose anymore fix: Remove unused PropTypes in DeleteItem fix(Selectors): Add useClient to search in client state
test: Remove deprecated todo. PR has been merged.
test: Fix skipped views/Recent test
I also homogenized test cases.
Co-authored-by: Célestin Ballèvre <[email protected]>
The notes back button access files route and this was creating an blank page
Album toolbar is render into cozy-bar which don't have access to react-router-dom. So we can't use hooks inside, we have to share it with props
Relative path doesn't work in this case instead I used the pathname from useLocation
react-router-dom is not available anymore in cozy-bar because we removed the context from Cozy Drive. However MoreMenu has been moved inside cozy-bar in the meantime and make extensives use of these hooks. We did not find any better solution that props drilling.
cballevre
force-pushed
the
feat/migrate-react-router-from-v3-to-v6
branch
from
July 3, 2023 14:48
ec57baa
to
64ac6bd
Compare
zatteo
approved these changes
Jul 3, 2023
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.
Related PRs: