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
What you were expecting:
When navigating to an edit route that uses TabbedForm the inputs should be displayed.
What happened instead:
When navigating to an edit route that uses TabbedForm the inputs are not displayed.
Steps to reproduce:
Related code:
https://github.com/armandosg/react-admin-v5
Other information:
I'm seeing that this only happens when the id of the resource contains special characters.
Environment
The text was updated successfully, but these errors were encountered:
Confirmed, thanks.
Tested on https://codesandbox.io/p/devbox/github/armandosg/react-admin-v5/tree/main, it seems the bug only occurs on the first resource, the one with a colon in its id ("1:prod:resource1"). So it seems to be that the TabbedForm routing is too strict on the id it accepts.
Sorry, something went wrong.
This issue has been introduced by remix-run/react-router#11199 released in react-router@6.22.1.
react-router@6.22.1
The location returned by useLocation is "/resource/1:prod:resource1/" while useResolvedPath now returns "/resource/1%3Aprod%3Aresource1"
useLocation
"/resource/1:prod:resource1/"
useResolvedPath
"/resource/1%3Aprod%3Aresource1"
Successfully merging a pull request may close this issue.
What you were expecting:
When navigating to an edit route that uses TabbedForm the inputs should be displayed.
What happened instead:
When navigating to an edit route that uses TabbedForm the inputs are not displayed.
Steps to reproduce:
Related code:
https://github.com/armandosg/react-admin-v5
Other information:
I'm seeing that this only happens when the id of the resource contains special characters.
Environment
The text was updated successfully, but these errors were encountered: