Skip to content

Tracking spec change: Implementations may not deprecate a field that the interface hasn't deprecated #3766

Open
@dondonz

Description

@dondonz

Potential spec change coming in to improve validation, ensuring an implementation cannot deprecate a field that the interface hasn't deprecated

This RFC was promoted to RFC 2 (Draft) stage yesterday graphql/graphql-spec#1053.

Metadata

Metadata

Assignees

No one assigned

    Labels

    keep-openTells Stale Bot to keep PRs and issues openspec-changeTracking GraphQL specification changes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions