Upcoming Release Changes (alpha) #1845
Merged
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
masteris currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmaster.Releases
@graphql-eslint/[email protected]
Major Changes
#1794
4079167eThanks @B2o5T! - - bring back
possible-type-extensionrule toschema-recommendedconfigunique-operation-nameandunique-fragment-namerules tooperations-recommendedconfigThe concept of sibling operations provided by graphql-config's
documentsfields is based onuniquely named operations and fragments, for omitting false-positive/negative cases when
operations and fragments are located in separate files. For this reason, these rules must be
included in the recommended config
relayconfig toschema-relay#1812
bf475e88Thanks @B2o5T! - -
alphabetizerule changesadd
definitions: trueoption forschema-all/operations-allconfigsrename
values: ['EnumTypeDefinition']tovalues: truerename
variables: ['OperationDefinition']tovariables: trueadd
groups: ['id', '*', 'createdAt', 'updatedAt']forschema-all/operations-allconfigsrequire-id-when-availablerule changesrequire-selectionsupdate
schema-all/operations-allconfigsrequire-descriptionrule changesrootField: trueoption forschema-recommendedconfigrequire
eslintat least>=8.44.0as peerDependencynaming-conventionschema-recommendedconfigremove graphql-js'
unique-enum-value-namesrulerename
no-case-insensitive-enum-values-duplicatestounique-enum-value-namesrequire-nullable-result-in-rootrule changesDo not check subscriptions
#1795
2f46a717Thanks @B2o5T! - - remove
parserOptions.schemaremove
parserOptions.documentsremove
parserOptions.extensionsremove
parserOptions.includeremove
parserOptions.excluderemove
parserOptions.projectsremove
parserOptions.schemaOptionsremove
parserOptions.graphQLParserOptionsremove
parserOptions.skipGraphQLConfigremove
parserOptions.operationsadd
parserOptions.graphQLConfig?: IGraphQLConfigfor programmatic usage#1793
6593482bThanks @B2o5T! - drop support of Node.js 12/14/16, GraphQL 14/15
#1792
804f8b61Thanks @B2o5T! - Remove
GraphQLRuleTesterfrom bundle, to test yourrules use regular
RuleTesterfrom eslintPatch Changes
#1813
1c2d220Thanks @B2o5T! - dependencies updates:
graphql-config@^4.5.0↗︎ (from^4.4.0, independencies)@babel/code-frame@^7.18.6↗︎ (fromdependencies)chalk@^4.1.2↗︎ (fromdependencies)tslib@^2.4.1↗︎ (fromdependencies)graphql@^16↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0,in
peerDependencies)eslint@>=8.44.0↗︎ (topeerDependencies)#1792
804f8b61Thanks @B2o5T! - dependencies updates:
@babel/code-frame@^7.18.6↗︎ (fromdependencies)