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
What you were expecting:
When a basename has been set in the <Admin> component and one of the resources has the same name as the basename, it should correctly parse the id for fetching getOne.
/sponsored-recipes/sponsored-recipes/1 should fetch with the following: { resource: "sponsored-recipes", id: "1" }
What happened instead:
Instead it uses the resource name as id for fetching getOne.
/sponsored-recipes/sponsored-recipes/1 will try to fetch with the following: { resource: "sponsored-recipes", id: "sponsored-recipes" }
Steps to reproduce:
Set a basepath with the same name as resource
Open a detail page or even on list page already
Check console
Related code:
Haven't got time for a example yet, can add later if needed
Environment
React-admin version: 4.16.18
React version: 18.2.0
Browser: Chrome
Stack trace (in case of a JS error):
The text was updated successfully, but these errors were encountered:
What you were expecting:
When a basename has been set in the
<Admin>
component and one of the resources has the same name as the basename, it should correctly parse the id for fetching getOne./sponsored-recipes/sponsored-recipes/1
should fetch with the following: { resource: "sponsored-recipes", id: "1" }What happened instead:
Instead it uses the resource name as id for fetching getOne.
/sponsored-recipes/sponsored-recipes/1
will try to fetch with the following: { resource: "sponsored-recipes", id: "sponsored-recipes" }Steps to reproduce:
Related code:
Haven't got time for a example yet, can add later if needed
Environment
The text was updated successfully, but these errors were encountered: