@graphql-eslint/eslint-plugin 3.0.1-alpha-86a9e78.0 → 3.0.1

package/configs/index.d.ts

@@ -44,7 +44,6 @@ export declare const configs: {
             '@graphql-eslint/strict-id-in-types': string;
             '@graphql-eslint/unique-directive-names': string;
             '@graphql-eslint/unique-directive-names-per-location': string;
-            '@graphql-eslint/unique-enum-value-names': string;
             '@graphql-eslint/unique-field-definition-names': string;
             '@graphql-eslint/unique-operation-types': string;
             '@graphql-eslint/unique-type-names': string;
@@ -59,10 +58,7 @@ export declare const configs: {
                 arguments: string[];
             })[];
             '@graphql-eslint/input-name': string;
-            '@graphql-eslint/no-root-type': string;
             '@graphql-eslint/no-scalar-result-type-on-mutation': string;
-            '@graphql-eslint/no-unused-fields': string;
-            '@graphql-eslint/possible-type-extension': string;
             '@graphql-eslint/require-deprecation-date': string;
             '@graphql-eslint/require-field-of-type-query-in-mutation-result': string;
         };

package/configs/schema-all.d.ts

@@ -7,10 +7,7 @@ declare const _default: {
             arguments: string[];
         })[];
         '@graphql-eslint/input-name': string;
-        '@graphql-eslint/no-root-type': string;
         '@graphql-eslint/no-scalar-result-type-on-mutation': string;
-        '@graphql-eslint/no-unused-fields': string;
-        '@graphql-eslint/possible-type-extension': string;
         '@graphql-eslint/require-deprecation-date': string;
         '@graphql-eslint/require-field-of-type-query-in-mutation-result': string;
     };

package/configs/schema-recommended.d.ts

@@ -39,7 +39,6 @@ declare const _default: {
         '@graphql-eslint/strict-id-in-types': string;
         '@graphql-eslint/unique-directive-names': string;
         '@graphql-eslint/unique-directive-names-per-location': string;
-        '@graphql-eslint/unique-enum-value-names': string;
         '@graphql-eslint/unique-field-definition-names': string;
         '@graphql-eslint/unique-operation-types': string;
         '@graphql-eslint/unique-type-names': string;

package/docs/README.md

@@ -5,65 +5,66 @@ Each rule has emojis denoting:
 - 🚀 `graphql-eslint` rule
 - 🔮 `graphql-js` rule
 - 🔧 if some problems reported by the rule are automatically fixable by the `--fix` [command line](https://eslint.org/docs/user-guide/command-line-interface#fixing-problems) option
-- ✅ if it belongs to the `recommended` configuration
 
 <!-- 🚨 IMPORTANT! Do not manually modify this table. Run: `yarn generate:docs` -->
 <!-- prettier-ignore-start -->
-Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|Description|🚀&nbsp;/&nbsp;🔮|🔧|✅
--|-|:-:|-|-
-[alphabetize](rules/alphabetize.md)|Enforce arrange in alphabetical order for type fields, enum values, input object fields, operation selections and more.|🚀||
-[description-style](rules/description-style.md)|Require all comments to follow the same style (either block or inline).|🚀||✅
-[executable-definitions](rules/executable-definitions.md)|A GraphQL document is only valid for execution if all definitions are either operation or fragment definitions.|🔮||✅
-[fields-on-correct-type](rules/fields-on-correct-type.md)|A GraphQL document is only valid if all fields selected are defined by the parent type, or are an allowed meta field such as `__typename`.|🔮||✅
-[fragments-on-composite-type](rules/fragments-on-composite-type.md)|Fragments use a type condition to determine if they apply, since fragments can only be spread into a composite type (object, interface, or union), the type condition must also be a composite type.|🔮||✅
-[input-name](rules/input-name.md)|Require mutation argument to be always called "input" and input type to be called Mutation name + "Input".|🚀||
-[known-argument-names](rules/known-argument-names.md)|A GraphQL field is only valid if all supplied arguments are defined by that field.|🔮||✅
-[known-directives](rules/known-directives.md)|A GraphQL document is only valid if all `@directives` are known by the schema and legally positioned.|🔮||✅
-[known-fragment-names](rules/known-fragment-names.md)|A GraphQL document is only valid if all `...Fragment` fragment spreads refer to fragments defined in the same document.|🔮||✅
-[known-type-names](rules/known-type-names.md)|A GraphQL document is only valid if referenced types (specifically variable definitions and fragment conditions) are defined by the type schema.|🔮||✅
-[lone-anonymous-operation](rules/lone-anonymous-operation.md)|A GraphQL document is only valid if when it contains an anonymous operation (the query short-hand) that it contains only that one operation definition.|🔮||✅
-[lone-schema-definition](rules/lone-schema-definition.md)|A GraphQL document is only valid if it contains only one schema definition.|🔮||✅
-[match-document-filename](rules/match-document-filename.md)|This rule allows you to enforce that the file name should match the operation name.|🚀||
-[naming-convention](rules/naming-convention.md)|Require names to follow specified conventions.|🚀||✅
-[no-anonymous-operations](rules/no-anonymous-operations.md)|Require name for your GraphQL operations. This is useful since most GraphQL client libraries are using the operation name for caching purposes.|🚀||✅
-[no-case-insensitive-enum-values-duplicates](rules/no-case-insensitive-enum-values-duplicates.md)|Disallow case-insensitive enum values duplicates.|🚀|🔧|✅
-[no-deprecated](rules/no-deprecated.md)|Enforce that deprecated fields or enum values are not in use by operations.|🚀||✅
-[no-duplicate-fields](rules/no-duplicate-fields.md)|Checks for duplicate fields in selection set, variables in operation definition, or in arguments set of a field.|🚀||✅
-[no-fragment-cycles](rules/no-fragment-cycles.md)|A GraphQL fragment is only valid when it does not have cycles in fragments usage.|🔮||✅
-[no-hashtag-description](rules/no-hashtag-description.md)|Requires to use `"""` or `"` for adding a GraphQL description instead of `#`.|🚀||✅
-[no-root-type](rules/no-root-type.md)|Disallow using root types `mutation` and/or `subscription`.|🚀||
-[no-scalar-result-type-on-mutation](rules/no-scalar-result-type-on-mutation.md)|Avoid scalar result type on mutation type to make sure to return a valid state.|🚀||
-[no-typename-prefix](rules/no-typename-prefix.md)|Enforces users to avoid using the type name in a field name while defining your schema.|🚀||✅
-[no-undefined-variables](rules/no-undefined-variables.md)|A GraphQL operation is only valid if all variables encountered, both directly and via fragment spreads, are defined by that operation.|🔮||✅
-[no-unreachable-types](rules/no-unreachable-types.md)|Requires all types to be reachable at some level by root level fields.|🚀|🔧|✅
-[no-unused-fields](rules/no-unused-fields.md)|Requires all fields to be used at some level by siblings operations.|🚀|🔧|
-[no-unused-fragments](rules/no-unused-fragments.md)|A GraphQL document is only valid if all fragment definitions are spread within operations, or spread within other fragments spread within operations.|🔮||✅
-[no-unused-variables](rules/no-unused-variables.md)|A GraphQL operation is only valid if all variables defined by an operation are used, either directly or within a spread fragment.|🔮||✅
-[one-field-subscriptions](rules/one-field-subscriptions.md)|A GraphQL subscription is valid only if it contains a single root field.|🔮||✅
-[overlapping-fields-can-be-merged](rules/overlapping-fields-can-be-merged.md)|A selection set is only valid if all fields (including spreading any fragments) either correspond to distinct response names or can be merged without ambiguity.|🔮||✅
-[possible-fragment-spread](rules/possible-fragment-spread.md)|A fragment spread is only valid if the type condition could ever possibly be true: if there is a non-empty intersection of the possible parent types, and possible types which pass the type condition.|🔮||✅
-[possible-type-extension](rules/possible-type-extension.md)|A type extension is only valid if the type is defined and has the same kind.|🔮||
-[provided-required-arguments](rules/provided-required-arguments.md)|A field or directive is only valid if all required (non-null without a default value) field arguments have been provided.|🔮||✅
-[require-deprecation-date](rules/require-deprecation-date.md)|Require deletion date on `@deprecated` directive. Suggest removing deprecated things after deprecated date.|🚀||
-[require-deprecation-reason](rules/require-deprecation-reason.md)|Require all deprecation directives to specify a reason.|🚀||✅
-[require-description](rules/require-description.md)|Enforce descriptions in your type definitions.|🚀||✅
-[require-field-of-type-query-in-mutation-result](rules/require-field-of-type-query-in-mutation-result.md)|Allow the client in one round-trip not only to call mutation but also to get a wagon of data to update their application.|🚀||
-[require-id-when-available](rules/require-id-when-available.md)|Enforce selecting specific fields when they are available on the GraphQL type.|🚀||✅
-[scalar-leafs](rules/scalar-leafs.md)|A GraphQL document is valid only if all leaf fields (fields without sub selections) are of scalar or enum types.|🔮||✅
-[selection-set-depth](rules/selection-set-depth.md)|Limit the complexity of the GraphQL operations solely by their depth. Based on [graphql-depth-limit](https://github.com/stems/graphql-depth-limit).|🚀||✅
-[strict-id-in-types](rules/strict-id-in-types.md)|Requires output types to have one unique identifier unless they do not have a logical one. Exceptions can be used to ignore output types that do not have unique identifiers.|🚀||✅
-[unique-argument-names](rules/unique-argument-names.md)|A GraphQL field or directive is only valid if all supplied arguments are uniquely named.|🔮||✅
-[unique-directive-names](rules/unique-directive-names.md)|A GraphQL document is only valid if all defined directives have unique names.|🔮||✅
-[unique-directive-names-per-location](rules/unique-directive-names-per-location.md)|A GraphQL document is only valid if all non-repeatable directives at a given location are uniquely named.|🔮||✅
-[unique-enum-value-names](rules/unique-enum-value-names.md)|A GraphQL enum type is only valid if all its values are uniquely named.|🔮||✅
-[unique-field-definition-names](rules/unique-field-definition-names.md)|A GraphQL complex type is only valid if all its fields are uniquely named.|🔮||✅
-[unique-fragment-name](rules/unique-fragment-name.md)|Enforce unique fragment names across your project.|🚀||
-[unique-input-field-names](rules/unique-input-field-names.md)|A GraphQL input object value is only valid if all supplied fields are uniquely named.|🔮||✅
-[unique-operation-name](rules/unique-operation-name.md)|Enforce unique operation names across your project.|🚀||
-[unique-operation-types](rules/unique-operation-types.md)|A GraphQL document is only valid if it has only one type per operation.|🔮||✅
-[unique-type-names](rules/unique-type-names.md)|A GraphQL document is only valid if all defined types have unique names.|🔮||✅
-[unique-variable-names](rules/unique-variable-names.md)|A GraphQL operation is only valid if all its variables are uniquely named.|🔮||✅
-[value-literals-of-correct-type](rules/value-literals-of-correct-type.md)|A GraphQL document is only valid if all value literals are of the type expected at their position.|🔮||✅
-[variables-are-input-types](rules/variables-are-input-types.md)|A GraphQL operation is only valid if all the variables it defines are of input types (scalar, enum, or input object).|🔮||✅
-[variables-in-allowed-position](rules/variables-in-allowed-position.md)|Variables passed to field arguments conform to type.|🔮||✅
+Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|Description|&nbsp;&nbsp;&nbsp;&nbsp;Config&nbsp;&nbsp;&nbsp;&nbsp;|🚀&nbsp;/&nbsp;🔮|🔧
+-|-|:-:|:-:|-
+[alphabetize](rules/alphabetize.md)|Enforce arrange in alphabetical order for type fields, enum values, input object fields, operation selections and more.|![all][]|🚀|
+[description-style](rules/description-style.md)|Require all comments to follow the same style (either block or inline).|![recommended][]|🚀|
+[executable-definitions](rules/executable-definitions.md)|A GraphQL document is only valid for execution if all definitions are either operation or fragment definitions.|![recommended][]|🔮|
+[fields-on-correct-type](rules/fields-on-correct-type.md)|A GraphQL document is only valid if all fields selected are defined by the parent type, or are an allowed meta field such as `__typename`.|![recommended][]|🔮|
+[fragments-on-composite-type](rules/fragments-on-composite-type.md)|Fragments use a type condition to determine if they apply, since fragments can only be spread into a composite type (object, interface, or union), the type condition must also be a composite type.|![recommended][]|🔮|
+[input-name](rules/input-name.md)|Require mutation argument to be always called "input" and input type to be called Mutation name + "Input".|![all][]|🚀|
+[known-argument-names](rules/known-argument-names.md)|A GraphQL field is only valid if all supplied arguments are defined by that field.|![recommended][]|🔮|
+[known-directives](rules/known-directives.md)|A GraphQL document is only valid if all `@directives` are known by the schema and legally positioned.|![recommended][]|🔮|
+[known-fragment-names](rules/known-fragment-names.md)|A GraphQL document is only valid if all `...Fragment` fragment spreads refer to fragments defined in the same document.|![recommended][]|🔮|
+[known-type-names](rules/known-type-names.md)|A GraphQL document is only valid if referenced types (specifically variable definitions and fragment conditions) are defined by the type schema.|![recommended][]|🔮|
+[lone-anonymous-operation](rules/lone-anonymous-operation.md)|A GraphQL document is only valid if when it contains an anonymous operation (the query short-hand) that it contains only that one operation definition.|![recommended][]|🔮|
+[lone-schema-definition](rules/lone-schema-definition.md)|A GraphQL document is only valid if it contains only one schema definition.|![recommended][]|🔮|
+[match-document-filename](rules/match-document-filename.md)|This rule allows you to enforce that the file name should match the operation name.|![all][]|🚀|
+[naming-convention](rules/naming-convention.md)|Require names to follow specified conventions.|![recommended][]|🚀|
+[no-anonymous-operations](rules/no-anonymous-operations.md)|Require name for your GraphQL operations. This is useful since most GraphQL client libraries are using the operation name for caching purposes.|![recommended][]|🚀|
+[no-case-insensitive-enum-values-duplicates](rules/no-case-insensitive-enum-values-duplicates.md)|Disallow case-insensitive enum values duplicates.|![recommended][]|🚀|
+[no-deprecated](rules/no-deprecated.md)|Enforce that deprecated fields or enum values are not in use by operations.|![recommended][]|🚀|
+[no-duplicate-fields](rules/no-duplicate-fields.md)|Checks for duplicate fields in selection set, variables in operation definition, or in arguments set of a field.|![recommended][]|🚀|
+[no-fragment-cycles](rules/no-fragment-cycles.md)|A GraphQL fragment is only valid when it does not have cycles in fragments usage.|![recommended][]|🔮|
+[no-hashtag-description](rules/no-hashtag-description.md)|Requires to use `"""` or `"` for adding a GraphQL description instead of `#`.|![recommended][]|🚀|
+[no-root-type](rules/no-root-type.md)|Disallow using root types `mutation` and/or `subscription`.||🚀|
+[no-scalar-result-type-on-mutation](rules/no-scalar-result-type-on-mutation.md)|Avoid scalar result type on mutation type to make sure to return a valid state.|![all][]|🚀|
+[no-typename-prefix](rules/no-typename-prefix.md)|Enforces users to avoid using the type name in a field name while defining your schema.|![recommended][]|🚀|
+[no-undefined-variables](rules/no-undefined-variables.md)|A GraphQL operation is only valid if all variables encountered, both directly and via fragment spreads, are defined by that operation.|![recommended][]|🔮|
+[no-unreachable-types](rules/no-unreachable-types.md)|Requires all types to be reachable at some level by root level fields.|![recommended][]|🚀|🔧
+[no-unused-fields](rules/no-unused-fields.md)|Requires all fields to be used at some level by siblings operations.||🚀|🔧
+[no-unused-fragments](rules/no-unused-fragments.md)|A GraphQL document is only valid if all fragment definitions are spread within operations, or spread within other fragments spread within operations.|![recommended][]|🔮|
+[no-unused-variables](rules/no-unused-variables.md)|A GraphQL operation is only valid if all variables defined by an operation are used, either directly or within a spread fragment.|![recommended][]|🔮|
+[one-field-subscriptions](rules/one-field-subscriptions.md)|A GraphQL subscription is valid only if it contains a single root field.|![recommended][]|🔮|
+[overlapping-fields-can-be-merged](rules/overlapping-fields-can-be-merged.md)|A selection set is only valid if all fields (including spreading any fragments) either correspond to distinct response names or can be merged without ambiguity.|![recommended][]|🔮|
+[possible-fragment-spread](rules/possible-fragment-spread.md)|A fragment spread is only valid if the type condition could ever possibly be true: if there is a non-empty intersection of the possible parent types, and possible types which pass the type condition.|![recommended][]|🔮|
+[possible-type-extension](rules/possible-type-extension.md)|A type extension is only valid if the type is defined and has the same kind.||🔮|
+[provided-required-arguments](rules/provided-required-arguments.md)|A field or directive is only valid if all required (non-null without a default value) field arguments have been provided.|![recommended][]|🔮|
+[require-deprecation-date](rules/require-deprecation-date.md)|Require deletion date on `@deprecated` directive. Suggest removing deprecated things after deprecated date.|![all][]|🚀|
+[require-deprecation-reason](rules/require-deprecation-reason.md)|Require all deprecation directives to specify a reason.|![recommended][]|🚀|
+[require-description](rules/require-description.md)|Enforce descriptions in your type definitions.|![recommended][]|🚀|
+[require-field-of-type-query-in-mutation-result](rules/require-field-of-type-query-in-mutation-result.md)|Allow the client in one round-trip not only to call mutation but also to get a wagon of data to update their application.|![all][]|🚀|
+[require-id-when-available](rules/require-id-when-available.md)|Enforce selecting specific fields when they are available on the GraphQL type.|![recommended][]|🚀|
+[scalar-leafs](rules/scalar-leafs.md)|A GraphQL document is valid only if all leaf fields (fields without sub selections) are of scalar or enum types.|![recommended][]|🔮|
+[selection-set-depth](rules/selection-set-depth.md)|Limit the complexity of the GraphQL operations solely by their depth. Based on [graphql-depth-limit](https://github.com/stems/graphql-depth-limit).|![recommended][]|🚀|
+[strict-id-in-types](rules/strict-id-in-types.md)|Requires output types to have one unique identifier unless they do not have a logical one. Exceptions can be used to ignore output types that do not have unique identifiers.|![recommended][]|🚀|
+[unique-argument-names](rules/unique-argument-names.md)|A GraphQL field or directive is only valid if all supplied arguments are uniquely named.|![recommended][]|🔮|
+[unique-directive-names](rules/unique-directive-names.md)|A GraphQL document is only valid if all defined directives have unique names.|![recommended][]|🔮|
+[unique-directive-names-per-location](rules/unique-directive-names-per-location.md)|A GraphQL document is only valid if all non-repeatable directives at a given location are uniquely named.|![recommended][]|🔮|
+[unique-enum-value-names](rules/unique-enum-value-names.md)|A GraphQL enum type is only valid if all its values are uniquely named.||🔮|
+[unique-field-definition-names](rules/unique-field-definition-names.md)|A GraphQL complex type is only valid if all its fields are uniquely named.|![recommended][]|🔮|
+[unique-fragment-name](rules/unique-fragment-name.md)|Enforce unique fragment names across your project.|![all][]|🚀|
+[unique-input-field-names](rules/unique-input-field-names.md)|A GraphQL input object value is only valid if all supplied fields are uniquely named.|![recommended][]|🔮|
+[unique-operation-name](rules/unique-operation-name.md)|Enforce unique operation names across your project.|![all][]|🚀|
+[unique-operation-types](rules/unique-operation-types.md)|A GraphQL document is only valid if it has only one type per operation.|![recommended][]|🔮|
+[unique-type-names](rules/unique-type-names.md)|A GraphQL document is only valid if all defined types have unique names.|![recommended][]|🔮|
+[unique-variable-names](rules/unique-variable-names.md)|A GraphQL operation is only valid if all its variables are uniquely named.|![recommended][]|🔮|
+[value-literals-of-correct-type](rules/value-literals-of-correct-type.md)|A GraphQL document is only valid if all value literals are of the type expected at their position.|![recommended][]|🔮|
+[variables-are-input-types](rules/variables-are-input-types.md)|A GraphQL operation is only valid if all the variables it defines are of input types (scalar, enum, or input object).|![recommended][]|🔮|
+[variables-in-allowed-position](rules/variables-in-allowed-position.md)|Variables passed to field arguments conform to type.|![recommended][]|🔮|
 <!-- prettier-ignore-end -->
+[recommended]: https://img.shields.io/badge/-recommended-green.svg
+[all]: https://img.shields.io/badge/-all-blue.svg

package/docs/rules/no-case-insensitive-enum-values-duplicates.md

@@ -2,8 +2,6 @@
 
 ✅ The `"extends": "plugin:@graphql-eslint/schema-recommended"` property in a configuration file enables this rule.
 
-🔧 The `--fix` option on the [command line](https://eslint.org/docs/user-guide/command-line-interface#--fix) can automatically fix some of the problems reported by this rule.
-
 - Category: `Schema`
 - Rule name: `@graphql-eslint/no-case-insensitive-enum-values-duplicates`
 - Requires GraphQL Schema: `false` [ℹ️](../../README.md#extended-linting-rules-with-graphql-schema)
@@ -40,3 +38,4 @@ enum MyEnum {
 ## Resources
 
 - [Rule source](../../packages/plugin/src/rules/no-case-insensitive-enum-values-duplicates.ts)
+- [Test source](../../packages/plugin/tests/no-case-insensitive-enum-values-duplicates.spec.ts)

package/docs/rules/unique-enum-value-names.md

@@ -1,7 +1,5 @@
 # `unique-enum-value-names`
 
-✅ The `"extends": "plugin:@graphql-eslint/schema-recommended"` property in a configuration file enables this rule.
-
 - Category: `Schema`
 - Rule name: `@graphql-eslint/unique-enum-value-names`
 - Requires GraphQL Schema: `false` [ℹ️](../../README.md#extended-linting-rules-with-graphql-schema)

package/index.js

@@ -67,7 +67,6 @@ const schemaRecommendedConfig = {
         '@graphql-eslint/strict-id-in-types': 'error',
         '@graphql-eslint/unique-directive-names': 'error',
         '@graphql-eslint/unique-directive-names-per-location': 'error',
-        '@graphql-eslint/unique-enum-value-names': 'error',
         '@graphql-eslint/unique-field-definition-names': 'error',
         '@graphql-eslint/unique-operation-types': 'error',
         '@graphql-eslint/unique-type-names': 'error',
@@ -89,10 +88,7 @@ const schemaAllConfig = {
             },
         ],
         '@graphql-eslint/input-name': 'error',
-        '@graphql-eslint/no-root-type': 'off',
         '@graphql-eslint/no-scalar-result-type-on-mutation': 'error',
-        '@graphql-eslint/no-unused-fields': 'off',
-        '@graphql-eslint/possible-type-extension': 'off',
         '@graphql-eslint/require-deprecation-date': 'error',
         '@graphql-eslint/require-field-of-type-query-in-mutation-result': 'error',
     },
@@ -589,6 +585,7 @@ const GRAPHQL_JS_VALIDATIONS = Object.assign({}, validationToRule('executable-de
     category: 'Schema',
     description: `A GraphQL enum type is only valid if all its values are uniquely named.`,
     requiresSchema: false,
+    recommended: false,
 }), validationToRule('unique-field-definition-names', 'UniqueFieldDefinitionNames', {
     category: 'Schema',
     description: `A GraphQL complex type is only valid if all its fields are uniquely named.`,
@@ -1575,12 +1572,11 @@ const rule$5 = {
     },
 };
 
-const ERROR_MESSAGE_ID = 'NO_CASE_INSENSITIVE_ENUM_VALUES_DUPLICATES';
 const rule$6 = {
     meta: {
         type: 'suggestion',
         docs: {
-            url: 'https://github.com/dotansimha/graphql-eslint/blob/master/docs/rules/no-case-insensitive-enum-values-duplicates.md',
+            url: `https://github.com/dotansimha/graphql-eslint/blob/master/docs/rules/no-case-insensitive-enum-values-duplicates.md`,
             category: 'Schema',
             recommended: true,
             description: 'Disallow case-insensitive enum values duplicates.',
@@ -1607,23 +1603,18 @@ const rule$6 = {
                 },
             ],
         },
-        fixable: 'code',
-        messages: {
-            [ERROR_MESSAGE_ID]: `Case-insensitive enum values duplicates are not allowed! Found: "{{ found }}"`,
-        },
         schema: [],
     },
     create(context) {
+        const selector = [graphql.Kind.ENUM_TYPE_DEFINITION, graphql.Kind.ENUM_TYPE_EXTENSION].join(',');
         return {
-            EnumTypeDefinition(node) {
-                const foundDuplicates = node.values.filter((item, index) => node.values.findIndex(v => v.name.value.toLowerCase() === item.name.value.toLowerCase()) !== index);
-                for (const dup of foundDuplicates) {
+            [selector](node) {
+                const duplicates = node.values.filter((item, index, array) => array.findIndex(v => v.name.value.toLowerCase() === item.name.value.toLowerCase()) !== index);
+                for (const duplicate of duplicates) {
+                    const enumName = duplicate.name.value;
                     context.report({
-                        node: dup.name,
-                        data: {
-                            found: dup.name.value,
-                        },
-                        messageId: ERROR_MESSAGE_ID,
+                        loc: getLocation(duplicate.loc, enumName),
+                        message: `Case-insensitive enum values duplicates are not allowed! Found: "${enumName}"`,
                     });
                 }
             },
@@ -2041,13 +2032,11 @@ const rule$b = {
         }
         const selector = [
             `:matches(${graphql.Kind.OBJECT_TYPE_DEFINITION}, ${graphql.Kind.OBJECT_TYPE_EXTENSION})[name.value=${mutationType.name}]`,
-            '>',
-            graphql.Kind.FIELD_DEFINITION,
-            graphql.Kind.NAMED_TYPE,
+            `> ${graphql.Kind.FIELD_DEFINITION} > .gqlType ${graphql.Kind.NAME}`,
         ].join(' ');
         return {
             [selector](node) {
-                const typeName = node.name.value;
+                const typeName = node.value;
                 const graphQLType = schema.getType(typeName);
                 if (graphql.isScalarType(graphQLType)) {
                     context.report({

package/index.mjs

@@ -61,7 +61,6 @@ const schemaRecommendedConfig = {
         '@graphql-eslint/strict-id-in-types': 'error',
         '@graphql-eslint/unique-directive-names': 'error',
         '@graphql-eslint/unique-directive-names-per-location': 'error',
-        '@graphql-eslint/unique-enum-value-names': 'error',
         '@graphql-eslint/unique-field-definition-names': 'error',
         '@graphql-eslint/unique-operation-types': 'error',
         '@graphql-eslint/unique-type-names': 'error',
@@ -83,10 +82,7 @@ const schemaAllConfig = {
             },
         ],
         '@graphql-eslint/input-name': 'error',
-        '@graphql-eslint/no-root-type': 'off',
         '@graphql-eslint/no-scalar-result-type-on-mutation': 'error',
-        '@graphql-eslint/no-unused-fields': 'off',
-        '@graphql-eslint/possible-type-extension': 'off',
         '@graphql-eslint/require-deprecation-date': 'error',
         '@graphql-eslint/require-field-of-type-query-in-mutation-result': 'error',
     },
@@ -583,6 +579,7 @@ const GRAPHQL_JS_VALIDATIONS = Object.assign({}, validationToRule('executable-de
     category: 'Schema',
     description: `A GraphQL enum type is only valid if all its values are uniquely named.`,
     requiresSchema: false,
+    recommended: false,
 }), validationToRule('unique-field-definition-names', 'UniqueFieldDefinitionNames', {
     category: 'Schema',
     description: `A GraphQL complex type is only valid if all its fields are uniquely named.`,
@@ -1569,12 +1566,11 @@ const rule$5 = {
     },
 };
 
-const ERROR_MESSAGE_ID = 'NO_CASE_INSENSITIVE_ENUM_VALUES_DUPLICATES';
 const rule$6 = {
     meta: {
         type: 'suggestion',
         docs: {
-            url: 'https://github.com/dotansimha/graphql-eslint/blob/master/docs/rules/no-case-insensitive-enum-values-duplicates.md',
+            url: `https://github.com/dotansimha/graphql-eslint/blob/master/docs/rules/no-case-insensitive-enum-values-duplicates.md`,
             category: 'Schema',
             recommended: true,
             description: 'Disallow case-insensitive enum values duplicates.',
@@ -1601,23 +1597,18 @@ const rule$6 = {
                 },
             ],
         },
-        fixable: 'code',
-        messages: {
-            [ERROR_MESSAGE_ID]: `Case-insensitive enum values duplicates are not allowed! Found: "{{ found }}"`,
-        },
         schema: [],
     },
     create(context) {
+        const selector = [Kind.ENUM_TYPE_DEFINITION, Kind.ENUM_TYPE_EXTENSION].join(',');
         return {
-            EnumTypeDefinition(node) {
-                const foundDuplicates = node.values.filter((item, index) => node.values.findIndex(v => v.name.value.toLowerCase() === item.name.value.toLowerCase()) !== index);
-                for (const dup of foundDuplicates) {
+            [selector](node) {
+                const duplicates = node.values.filter((item, index, array) => array.findIndex(v => v.name.value.toLowerCase() === item.name.value.toLowerCase()) !== index);
+                for (const duplicate of duplicates) {
+                    const enumName = duplicate.name.value;
                     context.report({
-                        node: dup.name,
-                        data: {
-                            found: dup.name.value,
-                        },
-                        messageId: ERROR_MESSAGE_ID,
+                        loc: getLocation(duplicate.loc, enumName),
+                        message: `Case-insensitive enum values duplicates are not allowed! Found: "${enumName}"`,
                     });
                 }
             },
@@ -2035,13 +2026,11 @@ const rule$b = {
         }
         const selector = [
             `:matches(${Kind.OBJECT_TYPE_DEFINITION}, ${Kind.OBJECT_TYPE_EXTENSION})[name.value=${mutationType.name}]`,
-            '>',
-            Kind.FIELD_DEFINITION,
-            Kind.NAMED_TYPE,
+            `> ${Kind.FIELD_DEFINITION} > .gqlType ${Kind.NAME}`,
         ].join(' ');
         return {
             [selector](node) {
-                const typeName = node.name.value;
+                const typeName = node.value;
                 const graphQLType = schema.getType(typeName);
                 if (isScalarType(graphQLType)) {
                     context.report({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@graphql-eslint/eslint-plugin",
-  "version": "3.0.1-alpha-86a9e78.0",
+  "version": "3.0.1",
   "sideEffects": false,
   "peerDependencies": {
     "graphql": "^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"
@@ -8,7 +8,7 @@
   "dependencies": {
     "@babel/code-frame": "7.16.0",
     "@graphql-tools/code-file-loader": "7.2.2",
-    "@graphql-tools/graphql-tag-pluck": "7.1.3",
+    "@graphql-tools/graphql-tag-pluck": "7.1.4",
     "@graphql-tools/import": "6.6.1",
     "@graphql-tools/utils": "8.5.3",
     "graphql-config": "4.1.0",