Skip to content

Update error code references in "Provides on Non-Composite Field" rule #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
michaelstaib merged 1 commit into from
Oct 2, 2025
Merged

Update error code references in "Provides on Non-Composite Field" rule #201

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec/Section 4 -- Composition.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1771,7 +1771,7 @@ on the composite type it returns. If a field's base type is not an object or
interface type (e.g., `String`, `Int`, `Boolean`, `Enum`, `Union`, or an `Input`
type), it cannot hold nested fields for `@provides` to select. Consequently,
attaching `@provides` to such a field is invalid and raises a
`PROVIDES_ON_NON_OBJECT_FIELD` error.
`PROVIDES_ON_NON_COMPOSITE_FIELD` error.

**Examples**

Expand All @@ -1797,7 +1797,7 @@ type User {

In this counter-example, `email` has a scalar base type (`String`). Because
scalars do not expose sub-fields, attaching `@provides` to `email` triggers a
`PROVIDES_ON_NON_OBJECT_FIELD` error.
`PROVIDES_ON_NON_COMPOSITE_FIELD` error.

```graphql counter-example
type User {
Expand Down