Add option to disable Field Suggestions since LexicalDistance Constructor takes Too Long for Unknown Field-Names

[walterunt]

If someone sends a simple query with a very long unknown/invalid fieldname (e.g. millions of characters), the validation rule FieldsOnCorrectTypeRule takes very long. This may lead to a lot of unecessary processing power wasted, when not used.

See also files:

• https://github.com/graphql/graphql-js/blob/16.x.x/src/validation/rules/FieldsOnCorrectTypeRule.ts
• https://github.com/graphql/graphql-js/blob/16.x.x/src/jsutils/suggestionList.ts

It looks like that the LexicalDistance calculation constructor is very slow when generating the _inputArray and _rows members, if the fieldname is very long.

Example Query (e.g. the content is several MB big (e.g. 40mb)): {"query":"{ unknownfield_unknownfield_...unknownfield}"}.

This all comes in place, when calculating suggestions for fields.

Please make an option to completely disable the suggestion calculation, i.e. do not perform the calculation at all if an option is set.

I have found similar issues:

• Disable suggestions #3229
• Validation errors can be used to get schema details #2247

but it looks like that the calculation is still in place, when the DisableSuggestion plugin is activated.

[JoviDeCroock]

This will be implemented in v17 and has been in #4214