Search results

Defaulting includeDeprecated to false is an industry wide mistake - it should default to true and make tooling make a choice

Status: Open.

#1181 In graphql/graphql-spec;

·bbakerman openedon Jul 9, 2025

Relax the validation of field selection on mutually exclusive types

Status: Open.

#1171 In graphql/graphql-spec;

·oprypkhantc openedon Jun 12, 2025

Add a section about schema evolution?

Status: Open.

#1169 In graphql/graphql-spec;

·BoD openedon Jun 3, 2025

[RFC] Field extensions

Status: Open.

#1162 In graphql/graphql-spec;

·martinbonnin openedon Apr 25, 2025

Specifying the literal value type of a custom scalar

Status: Open.

#1139 In graphql/graphql-spec;

·mindplay-dk openedon Feb 25, 2025

Uniqueness of field aliases

Status: Open.

#1128 In graphql/graphql-spec;

·wutsch0 openedon Nov 21, 2024

Make the unadorned type non-null?

Status: Open.

#1122 In graphql/graphql-spec;

·martinbonnin openedon Oct 30, 2024

Spec Bug...? ProvidedRequiredArgumentsRule fails to evaluate all potential runtime types

💭 Strawman (RFC 0)RFC Stage 0 (See CONTRIBUTING.md)RFC Stage 0 (See CONTRIBUTING.md)

Status: Open.

#1121 In graphql/graphql-spec;

·yaacovCR openedon Oct 30, 2024

Expand Deprecation Use Cases For Better Client Support and Service Support

Status: Open.

#1119 In graphql/graphql-spec;

·gwardwell openedon Oct 17, 2024

Fragment spread on interface type with no implementers

Status: Open.

#1109 In graphql/graphql-spec;

·goto-bus-stop openedon Aug 20, 2024

Allow empty object type _extensions_ in schema

Status: Open.

#1106 In graphql/graphql-spec;

·ychescale9 openedon Jul 19, 2024

Interface conditions fragments may not be used across spreads, discouraging reusability

Status: Open.

#1085 In graphql/graphql-spec;

·duckki openedon Mar 18, 2024