Closed wayheyha closed 2 years ago
Hi,
Thanks for this report.
Please know that this issue has been fixed with ra-navigation v4.0.4 (already available), and will also be included in the upcoming ra-enterprise v6.0.3 (soon to be released).
Besides, please note that this issue tracker is for the community version of react-admin only.
If you are a pro member, you can reach the Enterprise Support Desk by writing an email at support@react-admin-enterprise-edition.zendesk.com
What you were expecting: I can open the show/edit view of a ressource without an "element does not exist" notification and an redirect back to the list view.
What happened instead: If you have an layout wrapped inside an AppLocationContext-Component from the ra-navigation package following happens if you try to go to the edit or show view of an ressource:
What i found out so far: When the AppLocationContext is used following happens: Show-Button of a ressource is clicked -> the dataproviders getList is called -> query.js "Missing queryFn" error is triggered -> the getOne method is called.
Without the usage of the AppLocationContext only the getOne method is called and everything works fine.
Steps to reproduce:
Related code:
Other information:
Environment
Content of package.json: