overblog / GraphQLBundle

This bundle provides tools to build a complete GraphQL API server in your Symfony App.
MIT License
780 stars 223 forks source link

Types with same name differents according to schema #1153

Open remi-vasco opened 6 months ago

remi-vasco commented 6 months ago
Q A
Bug report? no
Feature request? yes
BC Break report? no
RFC? no
Version/Branch 1.0.0

Hello all,

I have my private API, and I would like to create a API for my partners. The Two api does not have the same deprecation policies: for the private I can introduce breaking change because in the same release I am updating the webapp accordingly.

But for the partner I need to have an extended deprecation policy, up to 3 months.

So, I created a Partner schema with some requests and mutations. that's fine and meet my goals.

But If the two schemas shares the same type (i.e. User) I don't know how to configure GraphqlBundle to tell that types for default schema are in directory config/graphql/types/default and types for schema partner are in directory config/graphql/types/partner, so my internal type can evoluate differently

In fact, I think it is not possible for now.

Any ideas of how I can do that ? And if not, Is it a feature easy for me to implement as a PR ?