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
The docs/readme needs to be updated to specify that not all conventional input names follows graphql-relay js, Like the clientMutationId which is normally used in graphql-relay needs to be specified as clientMutationID graphql-relay-go.
Just updated my version to the latest.
I guess you need to update the blog post also?
The text was updated successfully, but these errors were encountered:
Yeah you are right, the documentation is seriously lacking. I just updated the APIs for graphql-relay-go with the following changes
update the import path for graphql-go to github.com/chris-ramon/graphql and its new APIs
used golint suggestions for e.g. to use clientMutationID over clientMutationId.
I'll definitely would highlight the differences. My initial plan is to bring this library on par with graphql-relay-js v0.3.5 first (currently it is at v0.3.2). (Of course, I welcome PR contributions 😃)
Regarding the blog post, I've just updated it, thanks for the reminder! 👍🏻
The docs/readme needs to be updated to specify that not all conventional input names follows graphql-relay js, Like the
clientMutationId
which is normally used in graphql-relay needs to be specified asclientMutationID
graphql-relay-go.Just updated my version to the latest.
I guess you need to update the blog post also?
The text was updated successfully, but these errors were encountered: