Array query arguments expecting type definition

[henser]

Hi there 👋

First of all, big thanks to all the community involved in contributing to this GraphQL PHP implementation! 🙌

I'm raising up this issue as I've come across a recurring error in my Webonyx GraphQL PHP integration related to query arguments types.

When a client passes an array argument to a query as shown in the example below:

{
  myQuery(argument: ["someValue"]) {
    property
  }
}

this produces the following type exception:

GraphQL\Type\Definition\Type::getNullableType(): Argument #1 ($type) must be of type GraphQL\Type\Definition\Type, null given, called in webonyx/graphql-php/src/Validator/Rules/ValuesOfCorrectType.php on line 75

resulting in the request returning a 200 status code with an empty response.

Performing the same query with a boolean, integer, string, object or null argument value does not produce the same error and runs as expected.

Should this be handled differently where we allow for array type arguments even if they're not defining a type, but simply holding array values? If not possible or intended by design, would it make sense to adjust the error handling in this case so the request returns a readable and contextual error?

[spawnia]

What does the schema definition for myQuery look like?

[henser]

ok, I see the 14.11.5 release package here from Jan 24 but so these releases don't get reflected when installed via composer? Is 14.9.0 the last composer available package release? Do you have an estimation when the new v15 will be released and available?

[spawnia]

14.x is a separate branch. v15 will take a few weeks, but you can use dev-master in the meantime. It is well tested.

[henser]

cool! thanks for the info 👍 Got quite confused on the release package contents there for a while but I get it now 😅 🙌

[tim-hanssen]

Hey @spawnia any idea on when v15 will be released? If not I will update to the current master but that has some breaking changes so we need to find them.

[spawnia]

I have no timeline for that.