field arguments in query_collection are not validated correctly

[lorenzo]

Version Information

Server Version: 2.8.1

Environment

OSS

What is the expected behaviour?

Queries in query_collection should be validated against the schema and be marked as inconsistent. This is not the case when using the new naming convention.

Keywords

naming convention, graphql-default

What is the current behaviour?

While testing the new naming convention with an existing setup, I had an error with a REST endpoint. The query look something like this:

query {
   myFunction(args: {foo_bar: "baz"}) {
      id
   }
}

The query is incorrect, as with the new query convention, the arguments are now camelCased. The correct query should have been:

query {
   myFunction(args: {fooBar: "baz"}) {
      id
   }
}

Storing the former query in the metadata was possible, but resulted in a runtime error when running it.

If the bug is confirmed, would you be willing to submit a PR?

No

[lorenzo]

related to #8640