Skip to content

fix: deprecated reason non-nullable#735

Merged
pavelnikolov merged 1 commit into
mainfrom
deprecated-arg-non-null
Apr 25, 2026
Merged

fix: deprecated reason non-nullable#735
pavelnikolov merged 1 commit into
mainfrom
deprecated-arg-non-null

Conversation

@pavelnikolov

Copy link
Copy Markdown
Member

Make the reason for deprecation non-nullable to match the spec graphql/graphql-spec#1040.

Copilot AI review requested due to automatic review settings April 25, 2026 23:10

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the built-in GraphQL meta-schema to align with the updated GraphQL spec by making the @deprecated directive’s reason argument non-nullable (while retaining its default), and adjusts introspection test expectations accordingly.

Changes:

  • Change @deprecated(reason: ...) argument type from String to String! in the internal meta-schema.
  • Update introspection test expected JSON to reflect reason as NON_NULL wrapping String.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
internal/schema/meta.go Updates the meta-schema definition of @deprecated so reason is String! with the same default.
graphql_test.go Updates introspection expectations to match the new non-null type structure for reason.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@pavelnikolov pavelnikolov force-pushed the deprecated-arg-non-null branch from 7ad65dc to 6c596ce Compare April 25, 2026 23:16
@pavelnikolov pavelnikolov merged commit 2794fa3 into main Apr 25, 2026
2 checks passed
@pavelnikolov pavelnikolov deleted the deprecated-arg-non-null branch April 25, 2026 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants