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

Test fixes to use correct ResolveTypeFn and add types to Schema #27

Merged
merged 1 commit into from
Dec 8, 2017

Conversation

object88
Copy link
Contributor

@object88 object88 commented Jul 7, 2016

Fixes for tests, so they cooperate with the current version of graphql. See issue #26.

@object88
Copy link
Contributor Author

object88 commented Jul 7, 2016

Ah, sorry, I hadn't realized that the code in examples is tested separately. Will address this and try again.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.366% when pulling 5c3d4ee on object88:master into 9054c3f on graphql-go:master.

@object88
Copy link
Contributor Author

object88 commented Jul 7, 2016

Should be fixed now; seems to be passing the checks.

@dsoprea
Copy link

dsoprea commented Aug 30, 2016

Bump. Can we get this merged? Tests are currently failng for my PR on handler because of this bug.

@muhqu
Copy link

muhqu commented Sep 29, 2016

@sogko or @chris-ramon any chance you get this merged? …my PR (graphql-go/handler#14) is also failing due to this issue…

@johanoskarsson
Copy link

Bump again. I ran into this as well. Fix LGTM

@SCKelemen
Copy link

Bump

@danyim
Copy link

danyim commented Nov 16, 2017

Can we get this merged?

@whosthatknocking
Copy link

Any blockers to get this out?

@chris-ramon
Copy link
Member

thanks a lot guys! 🚢

@chris-ramon chris-ramon merged commit 5435009 into graphql-go:master Dec 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants