AST: `IntValueNode` and `FloatValueNode` store values as string

[SeppahBaws]

Using the AST provided by the library, I'm doing some introspection on the queries to extract the default values passed in to a query.

I noticed that the IntValueNode and FloatValueNode types both use string to store the value instead of number.

graphql-js/src/language/ast.ts

Lines 478 to 482 in 2aedf25

	export interface IntValueNode {
	readonly kind: Kind.INT;
	readonly loc?: Location | undefined;
	readonly value: string;
	}

graphql-js/src/language/ast.ts

Lines 484 to 488 in 2aedf25

	export interface FloatValueNode {
	readonly kind: Kind.FLOAT;
	readonly loc?: Location | undefined;
	readonly value: string;
	}

This seems a bit counter-intuitive to me, and would require me to write some custom parsing code on top of the existing parsing that graphql-js does.
Is this an intentional decision to store the values in a string instead of a number, or is it something that should be changed?

[JoviDeCroock]

The parser will always parse the raw-value as a string and hence put it in the AST that way, you can use valueFromAST or valueFromASTUntyped to correctly have this coerced for you.

It also looks like the GraphQL specification defines all literal values, including integers, as strings. This enables reliably parsing and serializing integers and floats across different programming languages and environments.

[SeppahBaws]

Ah okay thanks for the insight, I did not know about that! 🙂