-
Notifications
You must be signed in to change notification settings - Fork 1.1k
How to use different GraphQLObjectType mutations in one root parameter of the schema? #289
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
If I understand correctly, you would like some capability to organize your mutations hierarchically? |
@robzhu exactly |
This is a duplicate of #252 |
My understanding is that @nikitamarcius wants to have separate mutation GraphQL Object Types for each kind of data. To me that sounds the same as being able to mark arbitrary GraphQL Object Types as a "mutation type", which is what #252 is about. (Note that AFAIK the mutation type can already appear anywhere, if you just return it from a field: |
Hi! I want to create different GraphQLObjectType mutation\queries for each separate model.
In present time in GraphQL server we have one schema with two parameters: queries and mutations.
Each of which accepts GraphQLObjectType and includes differents fields. In library we have some think like this on the example of mutations:
Mutations:
UserAdd
UserRemove
ArcicleAdd
MapAddPin
..etc
Root mutations include list of all fields, - yes because we import all fields in one GraphQLObjectType. I want to use for each separate model GraphQLObjectType, that i can get in my library next option:
Mutations:
UserAdd
UserRemove
ArcicleAdd
MapAddPin
Thanks.
The text was updated successfully, but these errors were encountered: