Skip to content
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.

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

added context param to mutation resolve #77

Merged
merged 2 commits into from
Apr 15, 2016
Merged

Conversation

flipside
Copy link
Contributor

This is a fix for graphql@0.5.0 which changed the params passed to resolve.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.779% when pulling 427d32d on flipside:master into 977cbae on graphql:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.002%) to 99.782% when pulling 0f54efb on flipside:master into 977cbae on graphql:master.

@wincent
Copy link
Contributor

wincent commented Apr 15, 2016

Thank you! I tried to catch all of these in 4ed95bd but missed this one. I'll merge and cut a new release for this tomorrow.

@flipside
Copy link
Contributor Author

All good. I use rootValue and just updated my schema so it was an easy find.

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

Successfully merging this pull request may close these issues.

4 participants