Configuration options to control parser behavior
If enabled, the parser will understand and parse Client Controlled Nullability
Designators contained in Fields. They’ll be represented in the
nullabilityAssertion field of the FieldNode.
The syntax looks like the following:
Note: this feature is experimental and may change or be removed in the future.
Parser CPU and memory usage is linear to the number of tokens in a document however in extreme cases it becomes quadratic due to memory exhaustion. Parsing happens before validation so even invalid queries can burn lots of CPU time and memory. To prevent this you can set a maximum number of tokens allowed within a document.
By default, the parser creates AST nodes that know the location in the source that they correspond to. This configuration flag disables that behavior for performance or testing.