Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
eslint-plugin-graphql
Advanced tools
eslint-plugin-graphql - npm Package Versions
apollo-bot
published 4.0.0 • Changelog
v4.0.0
- Improve identity template literal tag docs. PR #254 by Jayden Seric.
- Add support for GraphQL 15. PR #271 by Scott Taylor.
- Update all
devDependencies- upgrades the project to use Babel 7 and ESLint 6. PR #271 by Scott Taylor. - BREAKING: Minimum supported Node.js version is now Node.js 10; Dropped support for Node.js 8. PR #271 by Scott Taylor.
Changelog
v3.1.1
- Update the
required-fieldsrule to handle inline fragments without field ancestors. PR #240 by Henry Q. Dineen
Changelog
v3.1.0
- Fix an issue that caused
graphql/required-fieldsto throw on non-existent field references. PR #231 by Vitor Balocco - chore: Update dependency
graphql-toolstov4.0.5. PR #239 - chore: Update dependency
eslinttov5.16.0. PR #218 - chore: Update dependency
graphqltov14.4.2. PR #220 - chore: Update dependency
test-all-versionstov4.1.1. PR #230 - chore: Update dependency
lodashtov4.17.13. PR #234 - chore: Update dependency
mochatov6. PR #213 - chore: Running
prettieron all files PR #237
apollo-bot
published 3.0.2 • Changelog
v3.0.2
- Fix regression which caused
graphql/required-fieldsto throw on non-existent field references. PR #203 by Matt Bretl
Changelog
v3.0.0
- BREAKING: The
required-fieldsrule has been significantly changed to make it a completely reliable method of ensuring anidfield (or any other field name) is always requested when available. PR #199 Here is the behavior, let's say we are requiring fieldid:- On any field whose return type defines a field called
id, the selection set must directly containid. - In any named fragment declaration whose type defines a field called
id, the selection set must directly containid. - An inline fragment whose type defines a field called
idmust containidin its selection set unless its parent is also an inline fragment that contains the fieldid. - Here's a specific case which is no longer valid:
query { greetings { hello ... on Greetings { id } } }- This must now be written as
query { greetings { id hello ... on Greetings { id } } }
- This is a more conservative approach than before, driven by the fact that it's quite hard to ensure that a combination of inline fragments actually covers all of the possible types of a selection set.
- On any field whose return type defines a field called
- Fix breaking change in
graphql@^14.0.0that renamedProvidedNonNullArgumentstoProvidedRequiredArguments#192 - Update dependencies to graphql-tools 4 and eslint 5.9 #193
Changelog
v2.1.1
- Fix support for InlineFragments with the
required-fieldsrule in #140 by Steve Hollaar - Fix error location information for literal .graphql files and strings with leading newlines in #122 by Dan Freeman
- Add
fraqlenvironment
Changelog
v2.1.0
- Retrieves
.graphqlconfigrelative to the file being linted, which re-enables support forvscode-eslintusing.graphqlconfigin #108 by [Jon Wong][https://github.com/jnwng/] - Cache schema reading/parsing results each time a rule is created in #137 by Kristján Oddsson