Get multiple schemas without merging

[quant-daddy]

Apollo federation exposes a function to validate composition of federated schemas. However, this requires the separate type definitions of the each schema without merging them. Currently graphql codegen automatically merges the schemas when creating a plugin. May be we can add an option to get the raw type definitions without merging?

[ardatan]

You can generate seperate files for each service like below;

generates:
   a-service.ts:
       schema: pointertoservicea
       plugins:
         - typescript
         - typescript-resolvers
       config:
          federation: true
   b-service.ts:
       schema: pointertoserviceb
       plugins:
         - typescript
         - typescript-resolvers
       config:
          federation: true

[quant-daddy]

Yes this works in the case when you just need to download the schemas and create type definitions for each of them separately. I wanted to create a plugin that could get access to all the schemas. Is that currently possible?

[dotansimha]

Yes this works in the case when you just need to download the schemas and create type definitions for each of them separately. I wanted to create a plugin that could get access to all the schemas. Is that currently possible?

At the moment, no :( plugins have access only to a single schema.

[quant-daddy]

It'd be great to have this feature :). The use case is when you want to compose and validate federated schemas. Currently I am downloading the federated schemas from github to compose and validate.

[dotansimha]

you

I'm not sure this is something we'll be able to provide with the current plugin API, maybe only for future major versions. Mainly because adding that means that we need to change the YAML API (to define multiple schemas without merging), the core orchestrator, and the plugins API (and then probably some of the plugins).

If you wish to use that for a custom plugin, I recommend to implement a custom loader, or load the schemas as part of your custom plugin.

[quant-daddy]

makes sense :)