Update graphql to the latest version 🚀#31
Open
greenkeeper[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
Collaborator
|
not yet compatible with graphql-tool, we'll have to wait for a few days until they upgrade |
Author
Version 0.9.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits .
See the full diff. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 0.9.0 of graphql just got published.
The version 0.9.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of graphql.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v0.9.0New:
Added isNamedType() and assertNamedType() #589
Default field resolvers now get full execution info as a third argument #615
ObjectType.isTypeOf() and InterfaceType.resolveType() may now return Promises #631
Support and fixes for flow type v0.38 #671
Added TypeInfo.getEnumValue() and EnumType.getValue(name) #674
Added findDeprecatedUsages() #676
Fixes:
Enforce spec that no non-meta field may start with "__" #600 (Potentially breaking for existing non-compliant uses).
isValidJSValue() reports if coercion results in error #602
Executor throws friendlier error if no document is provided #614
Fixed import circular dependency, improving compressed builds #644
Commits
The new version differs by 127 commits .
43cd3bb0.9.0e7b4bc7Update dependencies5b26da9Improve type definitions15d2184Merge pull request #631 from dherault/master0417aadSimplify default resolver functiona3c746cFactor out checking isTypeOf from subfield exe9239253Pass lint & flowc53efbeMissing commab40d427Fix completeObjectValue call bug1fb45d3Factor out runtime type validation1305360Reduce scope7064b9dMerge pull request #675 from robzhu/masterd1f586eMerge pull request #676 from graphql/find-deprecated3a53f25Freshen yarn.lockd7d6110Merge pull request #686 from graphql/greenkeeper/babel-cli-6.22.2There are 127 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴