Nested input object does not work about graphql-clj

[xsc]

world is a TextInput in your example, not a String, so the correct query should be (but I haven't run it):

{
  hello(world: {text: {value: "World"}})
}

So, the query is indeed invalid but the error message is a bit misleading.
(Or the schema/query you supplied is not the one that produced the error?)

[bjonica]

My mistake. Corrected the query to yours, but same problem.

{
  "errors": [
    {
      "error": "Argument 'world' of type 'WorldInput' has invalid value: {text: [:object-value {:value World}]}. Reason: Expected 'WorldInput', found not an object.",
      "loc": {
        "line": 2,
        "column": 16
      }
    }
  ]
}

[tendant]

I am not sure whether nested input type are supposed to work or not.

Input Type is defined in GraphQL Spec:

GraphQL describes the types of data expected by query variables. Input types may be lists of another input type, or a non‐null variant of any other input type.

Variables can only be scalars, enums, input objects, or lists and non‐null variants of those types. These are known as input types. Objects, unions, and interfaces cannot be used as inputs.

[tendant]

Just found this from type system definition:

An Input Object defines a set of input fields; the input fields are either scalars, enums, or other input objects. This allows arguments to accept arbitrarily complex structs.

Nested input type should be supported.

[tendant]

Currently parser treats input values as object values which is incorrect.

We need enhance the parser and validator to support this case.

[tendant]

This issue is fixed in latest version.