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
GraphQL is meant to make querying simpler, with a set schema independently used by the client and server.
Currently, the approach is to create a new Query/Mutation every time we want to add some client/server functionality. What we should be doing instead is making more generic Queries/Mutations that make use of optional arguments. For example instead of having separate element data and permission updates, instead, create a updateElement that allows changing all attributes, with fully customizable options passed in.
A similar thing goes for queries. Instead of having a separate query for getting elements with/without children, we should just put this in one query with an optional argument to adjust the results.
On the caching side, we can choose how to perceive the changes dependent on the arguments.
The text was updated successfully, but these errors were encountered:
GraphQL is meant to make querying simpler, with a set schema independently used by the client and server.
Currently, the approach is to create a new Query/Mutation every time we want to add some client/server functionality. What we should be doing instead is making more generic Queries/Mutations that make use of optional arguments. For example instead of having separate element data and permission updates, instead, create a
updateElement
that allows changing all attributes, with fully customizable options passed in.A similar thing goes for queries. Instead of having a separate query for getting elements with/without children, we should just put this in one query with an optional argument to adjust the results.
On the caching side, we can choose how to perceive the changes dependent on the arguments.
The text was updated successfully, but these errors were encountered: