Add more customizable pattern for `tag` about ts-graphql-plugin HOT 2 CLOSED

I agree "adding more complex tag pattern" .

Because some GraphQL clients don't use template literal tag function.

For example, with octokit/graphql.js :

const { repository } = await graphql(
  `
    {
      repository(owner: "octokit", name: "graphql.js") {
        issues(last: 3) {
          edges {
            node {
              title
            }
          }
        }
      }
    }
  `,
  {
    headers: {
      authorization: `token secret123`,
    },
  }
);

But I will not care TypeScript Template Literal Types pattern (e.g. Query<"query { data }"> ).

But I will not use this in my plugin because I think lexing / parsing queries should be responsible for graphql-js . And recursive descent parser with string type literal can exceed TypeScript's recursive type limitation.

#117 (comment)

from ts-graphql-plugin.

@Quramy about

But I will not care TypeScript Template Literal Types pattern (e.g. Query<"query { data }"> ).

I don't mean to actually infer type or whatever, just when you specify the pattern do not ignore ts types if they are matched by the pattern. I.e. here type Data = Query<'query { data }'> there is no some predefined Query type that cause some special behavior of ts-graphql-plugin. So as i understand the task of the plugin is match part of the file text, parse it as GraphQL and provide autocomplete.

So yes, i agree that this plugin should not provide some types inference out of the box, but delegate it to some other third party libraries. However, it would be good to have autocomplete in such cases

from ts-graphql-plugin.