Skip to content
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

Upgrade Router to V7 #1987

Closed
scottqueen-bixal opened this issue Dec 9, 2024 · 1 comment · Fixed by #2011
Closed

Upgrade Router to V7 #1987

scottqueen-bixal opened this issue Dec 9, 2024 · 1 comment · Fixed by #2011
Assignees
Labels
V1 Final V1 handoff work

Comments

@scottqueen-bixal
Copy link
Collaborator

Description

⚠️ React Router Future Flag Warning: React Router will begin wrapping state updates in React.startTransition in v7. You can use the v7_startTransition future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_starttransition.
⚠️ React Router Future Flag Warning: Relative route resolution within Splat routes is changing in v7. You can use the v7_relativeSplatPath future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_relativesplatpath.

User Story

No response

Acceptance Criteria

No response

@scottqueen-bixal scottqueen-bixal self-assigned this Dec 9, 2024
@scottqueen-bixal scottqueen-bixal added the V1 Final V1 handoff work label Dec 10, 2024
@scottqueen-bixal
Copy link
Collaborator Author

https://reactrouter.com/upgrading/v6#v7_relativesplatpath
https://reactrouter.com/upgrading/v6#v7_starttransition

The two items triggered as warnings include relative splat path, and start transition notices. After reviewing our code and the recommended upgrade path, we have determine that these two do not impact our current code.

Update any elements within that route tree to include the extra .. relative segment to continue linking to the same place:

we have no <Link /> to relative paths in our application

You don't need to update anything unless you are using React.lazy inside of a component.

We are not using React.lazy

We will opt into the future features to avoid the console warnings and watch for potential need of updates with new features

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
V1 Final V1 handoff work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant