Support full set of REST calls expected by react-admin
See original GitHub issueThe combination of a react-admin
interface for a SQLite
backend could be a really lightweight solution to many problems. But, there isn’t (yet) a REST wrapper for SQLite that is capable of integrating with react-admin
It now looks like soul
may be the missing component to getting this working. But, the Soul API needs to be extended, just a little:
https://marmelab.com/react-admin/DataProviderWriting.html#request-format
Issue Analytics
- State:
- Created a year ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
React-admin - Using Data Providers - Marmelab
Note: The simple REST client expects the API to include a Content-Range header in the response to getList calls. The value must be...
Read more >Data Providers - React-admin - Marmelab
Note: The simple REST client expects the API to include a Content-Range header in the response to getList calls. The value must be...
Read more >React-admin - Querying the API - Marmelab
Just like the dataProvider injected prop, the <Query> component expects three parameters: type , resource , and payload . It fetches the data...
Read more >Writing A Data Provider - React-admin - Marmelab
Tip: If your API supports more request types, you can add more methods to the ... here are example responses matching the format...
Read more >Data Providers - React-admin - Marmelab
Note: The simple REST client expects the API to include a Content-Range header in the response to GET_LIST calls. The value must be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey - hold on to your hats everyone. @thevahidal is “moving fast and breaking things”. It’s great to be part of the journey 🤸 🤸 🤸
I know it’s two calls, but I think the
1,2,3
could be a tidy way of doing it. As the client app is collating theTracks
data, it get thetracks/_filters=RockGod:true
. Then it loops through the rows and collates theAlbums
it needs data about then callsalbums/1,3,4?_schema=AlbumId, Title
(or something like that 😃. If there is only onealbumId
(albums/4
) then the call may even have been cached - one of the aims of REST.