Update graphql to the latest version 🚀 #67
Merged
Conversation
This file contains 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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
|
Looks like the error message thrown changed in 0.10 for no reason, unfortunate! |
|
@jnwng I've fixed the tests, feel free to merge and publish whenever. It looks like you bumped the version last time when GraphQL.js was upgraded. Also, might it be worth it to jump to 1.0.0? |
jnwng
approved these changes
May 30, 2017
|
definitely. will merge and bump to 1.0 on wednesday. |
|
@jnwng maybe we should bump |
jnwng
force-pushed
the
greenkeeper/graphql-0.10.0
branch
from
ed04b21 to
38e63ef
Compare
jtschulz
pushed a commit
to jtschulz/eslint-plugin-graphql
that referenced
this pull request
Jul 12, 2017
* fix(package): update graphql to version 0.10.0 * Fix tests * Bumping to `graphql@0.10.1`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.10.0 of graphql just got published.
The version 0.10.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.10.0New
isValidValue()andisValidLiteral()added to Scalar and enum types (#861).graphql()may now take aSourceobject, in addition to the existing support forstring(#866).graphql()may now take an object with named parameters (#867).Breaking
Intvalues toInt(#837).Fixes
GraphQLErrorstack trace includes error message (#718).Commits
The new version differs by 57 commits.
797e7e30.10.0845a45bMerge pull request #878 from gabelevi/flowfe5f544Flow v0.47.0 finds 3 errors in master. This is important to fix, because the87b24eeFreshen yarn.lock704a97dMerge pull request #877 from graphql/greenkeeper/mocha-3.4.20f186dechore(package): update mocha to version 3.4.21ff4932Freshen yarn.locke989de8Merge pull request #875 from graphql/greenkeeper/sane-1.7.09811d06chore(package): update sane to version 1.7.0f6f26fdHandle abrupt closing in mapAsyncIterator() (#870)50504b9remove unnecessary null arguments in test562ceadAllow providing an object of arguments to graphql(). (#867)1b41959Allow graphql() to accept a Source instance. (#866)bf352a8json is hard5510c75Allow providing custom default field resolver. (#865)There are 57 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 🌴