Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
validateResponseFormat triggers error when calling a dataProvider custom method
See original GitHub issueIf you implement a data provider with a custom method, then call that method as documented here then validateResponseFormat() throws an error if the returned object doesn’t contain a ‘data’ key
The response to 'action' must be like { data: ... }, but the received response does not have a 'data' key. The dataProvider is probably wrong for 'action'.
I think if it’s a custom method, there should not be any validation of the returned object (how could react-admin know?)
Otherwise, maybe the type of DataProvider should be typed better than [key: string]: any
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sure, please do!
Thanks for your pertinent report.
IMHO,
validateResponseFormat()should be perfectly un-opinionated about custom methods and we should harmonize the documentation and types accordingly. Change would not introduce breaking changes as it lower data requirements.Feedback on this topic will be very gladly welcomed!