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 Feb 10, 2022. It is now read-only.
In order to be friendly with Relay and graphql-relay-js lib, the API needs to allow the user to append some fields directly to an Object or an Interface.
Example would be to use the globalIdField or the mutationWithClientMutationId helpers from graphql-relay-js.
I was tempted to hack the field method but then it breaks the promise that it's a field you can build on (add some args and define the resolve method) because the passed object literal define all of those already.
I suspect to avoid any confusion, we should have an explicit method to handle this.
May be appendField(name:String,field:Object) and it would do :
In order to be friendly with Relay and graphql-relay-js lib, the API needs to allow the user to append some fields directly to an Object or an Interface.
Example would be to use the
globalIdField
or themutationWithClientMutationId
helpers from graphql-relay-js.I was tempted to hack the field method but then it breaks the promise that it's a field you can build on (add some args and define the resolve method) because the passed object literal define all of those already.
I suspect to avoid any confusion, we should have an explicit method to handle this.
May be appendField(name:String,field:Object) and it would do :
What do you think ?
The text was updated successfully, but these errors were encountered: