Skip to content

Commit 3ad80e4

Browse files
authored
polish: fix switched comments in GraphQLScalarTypeConfig (#4306)
I was just trying to understand the new flows for how scalar values are represented/parsed/serialized, and noticed that the comments for a couple of these methods looked backwards. Really hoping I am not just confused about the terminology, and that these aren't actually correct 😅
1 parent 79ad146 commit 3ad80e4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/type/definition.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -785,9 +785,9 @@ export interface GraphQLScalarTypeConfig<TInternal, TExternal> {
785785
/** Parses an externally provided literal value to use as an input. */
786786
/** @deprecated use `replaceVariables()` and `coerceInputLiteral()` instead, `parseLiteral()` will be removed in v18 */
787787
parseLiteral?: GraphQLScalarLiteralParser<TInternal> | undefined;
788-
/** Coerces an externally provided value to use as an input. */
789-
coerceOutputValue?: GraphQLScalarOutputValueCoercer<TExternal> | undefined;
790788
/** Coerces an internal value to include in a response. */
789+
coerceOutputValue?: GraphQLScalarOutputValueCoercer<TExternal> | undefined;
790+
/** Coerces an externally provided value to use as an input. */
791791
coerceInputValue?: GraphQLScalarInputValueCoercer<TInternal> | undefined;
792792
/** Coerces an externally provided const literal value to use as an input. */
793793
coerceInputLiteral?: GraphQLScalarInputLiteralCoercer<TInternal> | undefined;

0 commit comments

Comments
 (0)