Nested type declarations for complex objects.

[RuBAN-GT]

Hi everyone,

First of all thank you for this amazing library! But I found a strange behaviour related to type definition for an object with nested inputs.

Example:
I have a field assets which contains another field metadata that supports input arguments therefore I should define it using zeus autogenerated client:

const response = await client.query()({
  assets: [
    {
      input: {
        where: { ids: ['1234'] },
      },
    },
    {
      assets: {
        id: true,
        metadata: [
          {},
          {
            metadata: {
              field: {
                tagName: true,
                valueType: true,
              },
              '...on TextMetadata': {
                value: true,
              },
            },
          },
        ],
      },
    },
  ],
});

From output I'll have the next structure:

{
  "data": {
    "assets": {
      "assets": [
        {
          "id": "1234",
          "metadata": {
            "metadata": [
              {
                "field": {
                  "tagName": "ID",
                  "valueType": "NUMBER"
                }
              }
            ]
          }
        }
      ]
    }
  }
}

But Typescript type definition for the response is only supporting first-level declaration and an another deep objects with inputs will be defined as query array.

I suppose that is a unexpected library behaviour and probably a new bug.

Thank you!

[aexol]

Can you check on @beta version?

[RuBAN-GT]

Hi @aexol,

Now it takes an input as the type declaration:

P.S. I used 3.0.0-16 and generated a schema with
zeus $API__URL ./lib/generated --typescript --node