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
{{ message }}
This repository has been archived by the owner on Nov 8, 2021. It is now read-only.
Similarly to the create/delete api, I think this would be better off as a regular REST API - there's no apparent benefit from using GraphQL for it. Or am I missing a use case?
Yeah that's true, I guess I am coming at it from the original desire to have the requirements on the data access APIs, of which this GraphQL API subsumed that work. Having a coherent client API experience would be nice.
On the discussion of REST vs GraphQL I would say its simpler to have a single way of accessing and mutating data, so if there is no technical limitiation to having it all be GraphQL based it would most probably simplify the interface from an API consumers point of view.
This should be limited to admin users but should support:
The text was updated successfully, but these errors were encountered: