Fixes #3051 This change solves the problem of default values defined via SDL not always resolving correctly through introspection by preserving the original GraphQL literal in the schema definition. This changes argument and input field definitions `defaultValue` field from just the "value" to a new `GraphQLDefaultValueUsage` type which contains either or both "value" and "literal" fields. Since either of these fields may be set, new functions for resolving a value or literal from either have been added - `getLiteralDefaultValue` and `getCoercedDefaultValue` - these replace uses that either assumed a set value or were manually converting a value back to a literal. Here is the flow for how a default value defined in an SDL would be converted into a functional schema and back to an SDL: **Before this change:** ``` (SDL) --parse-> (AST) --coerceInputLiteral--> (defaultValue config) --valueToAST--> (AST) --print --> (SDL) ``` `coerceInputLiteral` performs coercion which is a one-way function, and `valueToAST` is unsafe and set to be deprecated in #3049. **After this change:** ``` (SDL) --parse-> (defaultValue literal config) --print --> (SDL) ```

Preserve defaultValue literals#3074leebyron wants to merge 1 commit intocoerce-input-literalgraphql/graphql-js:coerce-input-literalfrom default-value-literalsgraphql/graphql-js:default-value-literalsCopy head branch name to clipboard

Commits

Commits on Jun 3, 2021

Preserve defaultValue literals

Preserve defaultValue literals#3074
leebyron wants to merge 1 commit intocoerce-input-literalfrom
default-value-literals