[New rule] Add strict-id-in-types rule (#333)

Author: eddeee888

.changeset/happy-trainers-doubt.md

@@ -0,0 +1,5 @@
+---
+'@graphql-eslint/eslint-plugin': minor
+---
+
+[New rule] strict-id-in-types: use this to enforce output types to have a unique indentifier field unless being in exceptions

docs/README.md

@@ -1,5 +1,6 @@
 ## Available Rules
 
+
 - [`no-unreachable-types`](./rules/no-unreachable-types.md)
 - [`no-deprecated`](./rules/no-deprecated.md)
 - [`unique-fragment-name`](./rules/unique-fragment-name.md)
@@ -18,6 +19,7 @@
 - [`avoid-duplicate-fields`](./rules/avoid-duplicate-fields.md)
 - [`naming-convention`](./rules/naming-convention.md)
 - [`input-name`](./rules/input-name.md)
+- [`strict-id-in-types`](./rules/strict-id-in-types.md)
 - [`prettier`](./rules/prettier.md)
 - [`executable-definitions`](./rules/executable-definitions.md)
 - [`fields-on-correct-type`](./rules/fields-on-correct-type.md)
@@ -55,4 +57,4 @@
 
 - [Writing Custom Rules](./custom-rules.md)
 - [How the parser works?](./parser.md)
-- [`parserOptions`](./parser-options.md)
+- [`parserOptions`](./parser-options.md)

docs/rules/executable-definitions.md

@@ -7,4 +7,4 @@
 
 A GraphQL document is only valid for execution if all definitions are either operation or fragment definitions.
 
-> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/ExecutableDefinitionsRule.js).
+> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/ExecutableDefinitions.js).

docs/rules/fields-on-correct-type.md

@@ -7,4 +7,4 @@
 
 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.
 
-> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/FieldsOnCorrectTypeRule.js).
+> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/FieldsOnCorrectType.js).

docs/rules/fragments-on-composite-type.md

@@ -7,4 +7,4 @@
 
 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.
 
-> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/FragmentsOnCompositeTypesRule.js).
+> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/FragmentsOnCompositeTypes.js).

docs/rules/input-name.md

@@ -50,4 +50,24 @@ The array object has the following properties:
 
 #### `checkInputType` (boolean)
 
-Default: `"true"`
+Check that the input type name follows the convention <mutationName>Input
+
+Default: `false`
+
+#### `caseSensitiveInputType` (boolean)
+
+Allow for case discrepancies in the input type name
+
+Default: `true`
+
+#### `checkQueries` (boolean)
+
+Apply the rule to Queries
+
+Default: `false`
+
+#### `checkMutations` (boolean)
+
+Apply the rule to Mutations
+
+Default: `true`

docs/rules/known-argument-names.md

@@ -7,4 +7,4 @@
 
 A GraphQL field is only valid if all supplied arguments are defined by that field.
 
-> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownArgumentNamesRule.js).
+> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownArgumentNames.js).

docs/rules/known-directives.md

@@ -7,4 +7,4 @@
 
 A GraphQL document is only valid if all `@directives` are known by the schema and legally positioned.
 
-> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownDirectivesRule.js).
+> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownDirectives.js).

docs/rules/known-fragment-names.md

@@ -7,4 +7,4 @@
 
 A GraphQL document is only valid if all `...Fragment` fragment spreads refer to fragments defined in the same document.
 
-> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownFragmentNamesRule.js).
+> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownFragmentNames.js).

docs/rules/known-type-names.md

@@ -7,4 +7,4 @@
 
 A GraphQL document is only valid if referenced types (specifically variable definitions and fragment conditions) are defined by the type schema.
 
-> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownTypeNamesRule.js).
+> This rule is a wrapper around a `graphql-js` validation function. [You can find it's source code here](https://github.com/graphql/graphql-js/blob/master/src/validation/rules/KnownTypeNames.js).