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
I'm working on an integration between the dstore/Rest with a RESTful server. However, I'm struggling to fetch resources such as "/authors/1/books", as the current dstore implementation just appends the "id" of a resource.
I can have a Rest store which fetches the authors, but I can't have a Rest store which fetches the books from a selected author. I'd like to have something like this in the "target" of the store: "/authors/{id}/books".
This looks very basic, but I don't get it the purpose of this architecture. That's why I'm asking: how is the correct approach to my case? Changing the REST API doesn't seem reasonable from my point of view.
Best regards,
Charles.
The text was updated successfully, but these errors were encountered:
Hi there,
I'm working on an integration between the dstore/Rest with a RESTful server. However, I'm struggling to fetch resources such as "/authors/1/books", as the current dstore implementation just appends the "id" of a resource.
I can have a Rest store which fetches the authors, but I can't have a Rest store which fetches the books from a selected author. I'd like to have something like this in the "target" of the store: "/authors/{id}/books".
This looks very basic, but I don't get it the purpose of this architecture. That's why I'm asking: how is the correct approach to my case? Changing the REST API doesn't seem reasonable from my point of view.
Best regards,
Charles.
The text was updated successfully, but these errors were encountered: