noDuplicateEnumValueNames (GraphQL)

Language GraphQL

Summary

• Rule available since: v2.3.12
• Diagnostic Category: lint/correctness/noDuplicateEnumValueNames
• This rule is recommended, meaning it is enabled by default.
• This rule doesn’t have a fix.
• The default severity of this rule is error.
• Sources:
  • Same as @graphql-eslint/unique-enum-value-names

How to configure

biome.json

{
  "linter": {
    "rules": {
      "correctness": {
        "noDuplicateEnumValueNames": "error"
      }
    }
  }
}

Description

Disallow duplicate names in GraphQL enums.

This rule compares enum values without regard to letter case, so TEST and Test are treated as the same name.

Examples

Invalid

enum A {
  TEST
  OTHER
  TEST
}

code-block.graphql:3:8 lint/correctness/noDuplicateEnumValueNames ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Duplicate enum value name.
  
    1 │ enum A {
    2 │   TEST
  > 3 │   OTHER
      │        
  > 4 │   TEST
      │   ^^^^
    5 │ }
    6 │ 
  
  ℹ A GraphQL enum type is only valid if all its values are uniquely named. Make sure to name every enum value differently.
  

enum B {
  TEST
  TesT
}

code-block.graphql:2:7 lint/correctness/noDuplicateEnumValueNames ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Duplicate enum value name.
  
    1 │ enum B {
  > 2 │   TEST
      │       
  > 3 │   TesT
      │   ^^^^
    4 │ }
    5 │ 
  
  ℹ A GraphQL enum type is only valid if all its values are uniquely named. Make sure to name every enum value differently.
  

Valid

enum A {
  TEST
  OTHER
}

Related links

• Disable a rule
• Configure the code fix
• Rule options
• Source Code (Edit this Page)
• Test Cases
• Try in the playground