# possible-type-extensions

Source: https://apigenie.pl/docs/linter/graphql/rules/possible-type-extensions

This rule checks that extended types have the same kind as their definition, as the GraphQL specification requires.

## Rule Details

The rule reports the issues of the validation rule of the same name, with the messages of graphql-js. A document that breaks it is rejected by GraphQL servers and tools, so the rule should stay enabled with the `error` severity.

## Configuration

This rule has no options.

```yaml
version: "1.0"
commands:
  lint:
    graphql:
      rules:
        possible-type-extensions: warning
```

The rule can be disabled for a node and everything nested in it with an `# apigenie-lint-disable possible-type-extensions` comment on the node, or for a whole file with the comment at the top of the file, separated from the first definition by a blank line. It applies to definitions.

## Examples

**Good**.

```graphql
type User { id: ID! }
extend type User { name: String }
```

**Bad**. The linter reports `Cannot extend non-object type "User".`.

```graphql
scalar User
extend type User { name: String }
```