refactor: migrate to use upstream GraphQL #1
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.
An attempt to fix the issue: aerogear/graphql-link#41.
Based on discussions in PR: aerogear/graphql-link#57.
Checklist of Imports
Following is a list of imports that
graphql-link
uses from this fork ofgraphql
.I have planned to work on one package at a time and update this checklist as soon as that package is successfully converted to make use of the upstream GraphQL repo.
graphql-link
)Further comments
The commit currently attached to this PR makes the
"github.com/chirino/graphql/qerrors"
package to import and use the"github.com/graph-gophers/graphql-go/errors"
package of upstream repo by making some changes in the relevant files.Once this commit change gets approved, I'll move on to work on any of the remaining packages from the checklist above, by adding further commits to this PR itself.
If there is any fault in my approach then please let me know, I would be happy to make the necessary changes according to the requirements.