Skip to content

[2024-02] EVERYONE - check that changing SHOULD to MUST for error paths won't break your implementations #1482

@benjie

Description

@benjie

Ref: graphql/graphql-spec#1073

This spec PR immediately jumped to RFC2 status as it already seems to be the status quo, but none the less since it's technically a breaking change (should -> must) we're passing it through the RFC process. We will be merging it in as stage 3 in the spec next month, unless you tell us why we shouldn't - so please check your implementations are compliant!


Note: Action Item issues are reviewed and closed during Working Group
meetings.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions