We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
library
In version 6.29, even when the future flag v7_relativeSplatPath is set to false, a warning is still logged.
v7_relativeSplatPath
Instead of a falsy check, and undefined check would get rid of the warning when v7_relativeSplatPath is set to false.
Existing check:
if ((renderFuture == null ? void 0 : renderFuture.v7_relativeSplatPath) === undefined && (!routerFuture || !routerFuture.v7_relativeSplatPath)) { logDeprecation("v7_relativeSplatPath", "Relative route resolution within Splat routes is changing in v7", "https://reactrouter.com/v6/upgrading/future#v7_relativesplatpath"); }
System: OS: macOS 15.2 CPU: (12) arm64 Apple M2 Max Memory: 719.77 MB / 32.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm Browsers: Chrome: 133.0.6943.54 Safari: 18.2
npm
No future warning is logged when v7_relativeSplatPath is set to false
A future warning is logged when v7_relativeSplatPath is set to false
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm using React Router as a...
library
Reproduction
In version 6.29, even when the future flag
v7_relativeSplatPath
is set to false, a warning is still logged.Instead of a falsy check, and undefined check would get rid of the warning when
v7_relativeSplatPath
is set to false.Existing check:
System Info
Used Package Manager
npm
Expected Behavior
No future warning is logged when
v7_relativeSplatPath
is set to falseActual Behavior
A future warning is logged when
v7_relativeSplatPath
is set to falseThe text was updated successfully, but these errors were encountered: