You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ 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
The text was updated successfully, but these errors were encountered:
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
Description
React.startTransition
in v7. You can use thev7_startTransition
future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_starttransition.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
The text was updated successfully, but these errors were encountered: