Option to generate type definitions side by side with *.gql files

It would be awesome if there was a option to just generate fragments and services side by side with the *.gql files.

This example

[Component A]
  - query.gql
[Component B]
  - query.gql

resulted in this output.

[Component A]
  - query.gql
  - query.ts
[Component B]
  - query.gql
  - query.ts

Then i could define an angular component’s specific fragments without worrying about naming collisions, like I needed to do here because some other component’s grapql query had a fragment defined with the name location, and the same goes for query and mutation names.

fragment locationSelect on Location {
  id
  name
}

query GetPositionModalData {
  locations: locationsConnection(pagesize: -1) {
    edges {
      node {
        ...locationSelect
      }
    }
  }
}

[adam1658]

Here’s how I’ve solved this in my codebase: Rather than using the graphql-code-generator CLI with a wildcard for all my documents, I run it using the API, once for each document:

(async function() {
  const files = await globPromise('./src/**/*.graphql');

  await Promise.all(
    files.map(filename => {
      const parsedPath = path.parse(filename);
      return generate({
        overwrite: true,
        schema: ['../graphql-schema.graphqls'],
        documents: filename,
        generates: {
          [`${parsedPath.dir}/${parsedPath.name}.generated.tsx`]: {
            plugins: [
              'typescript-common',
              // ...,
            ]
          },
        },
      });
    }),
  );
})();

It’s a new project so I have very few documents at the moment, and I haven’t seen how well it scales yet.

[dotansimha]

@furier @adam1658 @vreality64 @Morphexe It took some time, but it’s available (as alpha) now after this PR: https://github.com/dotansimha/graphql-code-generator/pull/1846