Skip to content

Tracking spec change: non-nullable reason for @deprecated #3736

Closed
@dondonz

Description

@dondonz

Keeping a note here for us to return to later, this small spec change may get merged in soon graphql/graphql-spec#1040

It changes @deprecated's reason to be non-nullable. There's a default value for the reason already, so the migration pathway isn't a big deal, it's more about removing an odd edge case.

This is not yet in the spec, this issue is a reminder to check in on this topic again later

Metadata

Metadata

Assignees

No one assigned

    Labels

    spec-changeTracking GraphQL specification changes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions