src/content/docs/linter/rules/use-lone-executable-definition.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="GraphQL" icon="seti:graphql"> :::caution This rule is part of the [nursery](/linter/#nursery) group. This means that it is experimental and the behavior can change at any time. ::: ## Summary - Rule available since: `v2.3.12` - Diagnostic Category: [`lint/nursery/useLoneExecutableDefinition`](/reference/diagnostics#diagnostic-category) - This rule doesn't have a fix. - The default severity of this rule is [**information**](/reference/diagnostics#information). - Sources: - Same as [`@graphql-eslint/lone-executable-definition`](https://the-guild.dev/graphql/eslint/rules/lone-executable-definition){
"linter": {
"rules": {
"nursery": {
"useLoneExecutableDefinition": "error"
}
}
}
}
Require queries, mutations, subscriptions or fragments each to be located in separate files.
This rule ensures that each GraphQL document only contains a single operation (query, mutation, or subscription) or fragment definition. Having multiple executable definitions in a single file can make code harder to maintain, test, and understand.
query Foo {
id
}
fragment Bar on Baz {
id
}
query Foo {
id
}
mutation ($name: String!) {
createUser {
id
}
}
query Foo {
id
}
query Bar {
id
}
query Foo {
id
}
fragment Bar on Baz {
id
}