Extend the extensions possibilities

[kbrandwijk]

Using different config extensions in the graphql-cli, I have noticed there is a gap between what the extensions can provide, and what custom behavior the cli needs. I think part of this needs to be solved in the cli, but the other part probably in graphql-config.

For example, retrieving an endpoint is part of the graphql-config extensions, and loading a schema is part of the core, and can't be influenced by extensions.

This is not a 'ready to be implemented' kind of issue, but food for thought...

[kamilkisiela]

Hi there, it's The Guild :) We're working on a new version of GraphQL Config. The goal is to make it platform agnostic, flexible enough to use with any tool and framework, reduce the bundle size and a lot more and what's even more important, bring it back to life and keep maintaining.

New changes #162 are already merged into master and v3.0.0-alpha.13 is released.

With new GraphQL Config we decided to make extensions a first class citizen and let them actually extend GraphQL Config's logic.

Right now extensions can enable Config to load a Schema from different sources, an example can be found here. Because we moved the schema loading logic outside GraphQL Config, we named it Loaders, it was possible to introduce a loader for files on GitHub or a loader to extract schema from typescript and javascript files. I think it opens up the Config for variety of use cases.