Gql() variables are not type-safe

[ValentinH]

While playing with the new changes introduced in v5, I noticed that Apollo queries and mutations variables can now be made typesafe by using the typedGql helper (as documented here).

However, I noticed that the barebone version of using the Gql function isn't type-safe. Is it a known limitation?

From the examples (https://github.com/graphql-editor/graphql-zeus/blob/master/examples/typescript-node/src/index.ts#L241-L273):

  const aliasedQueryExecute = await Gql('query')(
    {
      listCards: {
        __alias: {
          namy: {
            name: true,
          },
          atak: {
            attack: [
              { cardID: $('cardIds', '[String!]!') },
              {
                name: true,
                __alias: {
                  bbb: {
                    Defense: true,
                  },
                  ccc: {
                    Children: true,
                  },
                },
              },
            ],
          },
        },
        id: true,
      },
    },
    {
      variables: {
        cardIds: ['aaa'],
      },
    },
  );

It is using the $() function and providing a graphql type but I can pass any data to cardIds without any type error.

[IceBlizz6]

Possible duplicate of #232 (???)

[ValentinH]

No this is a different topic.

[bintoll]

I also came to this topic with the same question, seems that unfortunately params are not typesafe

[IceBlizz6]

Sad to hear that this hasn't been solved, I'm not very familiar with this codebase but i hope they will try to solve it.
I still think this should be a priority 1 issue.
A type safe GraphQL client library loses a lot of its value without type safety.

I eventually ended up just creating my own type safe library which have worked fine for a year now, so it's clearly possible to do. Since i started that i noticed that there are many other existing libraries popped up, so maybe try to check out some of those to see if they have covered this need.
Otherwise i may just end up publishing the library i created in the near future.

[ValentinH]

On our side, we moved to https://the-guild.dev/graphql/codegen. It's great, nothing to complain about since then.

[bintoll]

On our side, we moved to https://the-guild.dev/graphql/codegen. It's great, nothing to complain about since then.

I am using this now with typed-document-node and it works great, but recently got the requirement to strictly mange data that FE requests from BE, so it is needed to build queries dynamically, and is not possible with codegen, unfortunatelly

[ValentinH]

What is dynamic: the returned data or the query args?

[aexol]

They are typesafe if you use with typed document node. @bintoll If you have dynamic queries do it without a lib. By the way @ValentinH of course codegen is a great library, but It's like comparing apples and oranges - 2 different use cases.

[bintoll]

What is dynamic: the returned data or the query args?

The data that is returned in response from BE should be dynamic in my case and I need a possibility to build a query with js.

[bintoll]

They are typesafe if you use with typed document node. @bintoll If you have dynamic queries do it without a lib. By the way @ValentinH of course codegen is a great library, but It's like comparing apples and oranges - 2 different use cases.

How this could be typesafe if all parameters has Variable<any, string> in index.ts after generating the code?
So $('Uid', 'Date!') does not raise an error, that Uid can only be ID! as per schema

Your suggestion no not to use lib unfortunately is not relevant in my case, I would like to use the typesafe dynamic query build, to build type document node in order to use later it request.