noDuplicateGraphqlOperationName (GraphQL)

Language GraphQL

Summary

Rule available since: v2.3.6
Diagnostic Category: lint/suspicious/noDuplicateGraphqlOperationName
This rule isn’t recommended, so you need to enable it.
This rule doesn’t have a fix.
The default severity of this rule is warning.
Sources:
- Inspired from @graphql-eslint/unique-operation-name

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "suspicious": {
5
        "noDuplicateGraphqlOperationName": "error"
6
      }
7
    }
8
  }
9
}

Description

Require unique operation names within a GraphQL document.

Distinct names let clients, logs, and debugging tools identify each query, mutation, or subscription without ambiguity.

Examples

Invalid

1
query user {
2
  user {
3
    id
4
  }
5
}
6

7
query user {
8
  me {
9
    id
10
  }
11
}

code-block.graphql:7:1 lint/suspicious/noDuplicateGraphqlOperationName ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Operation named "user" is already defined.
  
     5 │ }
     6 │ 
   > 7 │ query user {
       │ ^^^^^^^^^^^^
   > 8 │   me {
   > 9 │     id
  > 10 │   }
  > 11 │ }
       │ ^
    12 │ 
  
  ℹ GraphQL operation names must be unique to ensure proper identification.
  
  ℹ Rename the operation to have a unique name.

Valid

1
query user {
2
  user {
3
    id
4
  }
5
}
6

7
query me {
8
  me {
9
    id
10
  }
11
}

noDuplicateGraphqlOperationName (GraphQL)

Summary

How to configure

Description

Examples

Invalid

Valid

Related links