graphql-spec

graphql-spec copied to clipboard

[RFC] Type system ordering of: object interfaces, directive arguments, input object fields, enum values

7

**UPDATE 2025-06-26**: The motivation of this PR is **to make introspection stable** (and, related, to make `printSchema()` stable, and to make `printSchema(buildSchema(printSchema(schema))) === printSchema(schema)`). **UPDATE 2024-04-05**: Following [last night's WG...

benjie

[RFC] List coercion algorithm

1

Fixes #1002. Previously, list coercion does not detail what to do with variables at all, and that could lead to either a null pointer exception, or to double-coercion of the...

benjie

Is there a reason graphql floats do not support Infinity and NaN?

3

Is there a reason graphql floats do not support Infinity and NaN? Would a proposal to add infinity and/or NaN be seriously considered?

dopry

enhance(ResolveFieldValue): add async collection language

3

and some baseline collection language for comparison extracted from #742

yaacovCR

Fix formatting and typo in `MapSourceToResponseEvent`

3

Based on https://github.com/graphql/graphql-spec/pull/1069; that PR needs merging first (hence this is marked as a draft). If reviewing this, **just look at the final commit only**. Lee did an editorial edit...

benjie

3.10 Input Objects - clarify lists are permitted as Input fields

2

A minor omission in 3.10 Input Objects confused me briefly today by suggesting lists might not be permitted as the type of an input field. However, they are (and are...

msolomon

Fix CoerceArgumentValues() hasValue

3

Fixes a bug discovered whilst carefully evaluating `CoerceArgumentValues()` that leads to "undefined value leakage" and potential null pointer exception if strictly following the spec. GraphQL.js does **not** suffer this, so...

benjie

[RFC] Introduce Strict and Legacy All Variable Usages Are Allowed

1

For the following schema: ```graphql type Query { sum(numbers:[Int!]!): Int } ``` The following query is currently valid: ```graphql query Q ($number: Int = 3) { sum(numbers: [1, $number, 3])...

benjie

[RFC] Implementations may not deprecate a field that the interface hasn't deprecated

1

This PR addresses a spec validation omission; if an interface field is not deprecated then any implementation of that interface field should also not be deprecated. I.e. the following schema...

benjie

deferred fragments should not change ordering of fields within initial response

2

builds on #1052 and so the diff from that should be useful: https://github.com/yaacovCR/graphql-spec/compare/deduplicate3...yaacovCR:graphql-spec:deduplicate4

yaacovCR