New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Come up with proper solution for keys being strings or atoms #12

Open

seanabrahams opened this issue Mar 2, 2016 · 0 comments

Member

seanabrahams commented Mar 2, 2016

In practice, clientMutationID is null on mutation responses due to the code expecting an atom key but receiving a string key.

I've updated the codebase to check for both but this "dirtiness" is not acceptable.

https://github.com/graphql-elixir/graphql-relay-elixir/blob/master/lib/graphql/relay/mutation.ex#L49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment