# no-mixed-definitions

Source: https://api-genie.dev/docs/linter/graphql/rules/no-mixed-definitions

A rule of the GraphQL linter, which reads GraphQL schemas and operations. Since 0.9.0. In the rulesets: Recommended at error, Strict at error, All at error.

This rule checks that a document holds either a schema or operations, not both.

## Rule details

Schemas and operations have different owners and lifecycles: schema files are served, operation files are compiled into clients. Each operation and fragment of a document with type system definitions is reported.

The rule applies to definitions. An `# apigenie-lint-disable no-mixed-definitions` comment on a node
turns it off for the node and everything nested in it; at the top of the file, separated from the
first definition by a blank line, the comment turns it off for the whole file.

## Examples

**Good**.

```graphql
type Query { me: User }
```

**Bad**. The linter reports `Operation 'Me' should not be in a document with type system definitions`.

```graphql
type Query { me: User }
query Me { me { id } }
```
