Mapping schemas to different directories containing type configurations in a multi schema environment

[chemisus]

Q	A
Bug report?	no
Feature request?	yes
BC Break report?	no
RFC?	no
Version/Branch	~0.8.0

I am trying to set up a multi schema environment, however, some of our schemas have a collision in type names. I've looked into mapping, but that does not look like it would tie in to the schema name. I'd like to avoid adding prefixes to our type names.

GET /graphql/A
-> loads types from /config/graphql/A

GET /graphql/B
-> loads types from /config/graphql/B

Is this possible?

[mcg-web]

Hi @chemisus,

This is not possible right now but this could be a feature, we decided to not invest to much time on multiple schema because this was not in graphQL specs and seem to not be used in the bundle by many...

[chemisus]

@mcg-web I think this would be a great feature to have, especially when it comes to versioning the graphql endpoint.

We are working on a new version of our schema, which includes major changes to schema structure and some new resolvers. Instead of forcing all applications that use our API to update, we would like to roll out the new schema along side our current, and gradually move all the clients over.

Do you have any suggestions as to how one would start to implement this feature in a fork?

[mcg-web]

This can be release in 0.9 I think, because it don't ask for a lot of work. We will try to work on feature as soon as possible.

[mcg-web]

this will be first job in 0.10 version, missing time to work on this right now

[chemisus]

Sounds good. Thanks @mcg-web .

[mcg-web]

After some time, we finally start working on this issue, #289 is the first step to make multi schema a little more flexible...

TODO:

• only need type is loaded for a given schema (Impose explicit declaration of non detected types #289)
• separate types generation (under different directories and namespace)
• possibility to map config files directly in schema

[mcg-web]

It is possible to fulfilled this without mapping files for specific schema (as we load only types that we actually needs). I'm closing this I'll add some examples to demo and some more doc here if needed.