3 ms·
If GraphQL was actually a query language (as in: allowing you to change the result set, not only the result shape), maybe 1 would be easily possible. Intuitivel
by solarkraft 3y ago
If GraphQL was actually a query language (as in: allowing you to change the result set, not only the result shape), maybe 1 would be easily possible. Intuitively I would like that.
3 seems to be the most pragmatic option to me when you have good control over each side.
- klysm 3y agoSupporting the interface of graphql from the backend though is usually not very easy - you usually end up with a half baked database implementation that wraps a better database
- qazxcvbnm 3y agoCan you elaborate on what you mean by changing the result set as opposed to the shape?
- nicwolff 3y agoHuh? GraphQL field arguments are used to filter and paginate result sets.