Adding support for [email protected] and [email protected]

[jnwng]

Also added some infra to make sure we run tests against all possible versions.

This is a major breaking change — it fails a few tests and its not worth diverging the tests based on version to avoid the major bump. There's also some complications with libraries like graphql-config not properly supporting custom named "Query" types, but shouldn't affect a large amount of people.

TODO:

• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests pass
• Update CHANGELOG.md with your change
• If this was a change that affects the external API, update the README

Pull Request Labels

• feature
• blocking
• docs

[lgandecki]

This would be fantastic to have, for now, I'm using a custom npm package based on @jnwng fork :
https://www.npmjs.com/package/eslint-plugin-graphql-next