Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Nested GraphQL Mutations #990

Open
sajeetharan opened this issue Nov 21, 2022 · 3 comments
Open

Support Nested GraphQL Mutations #990

sajeetharan opened this issue Nov 21, 2022 · 3 comments
Labels

Comments

@sajeetharan
Copy link
Member

sajeetharan commented Nov 21, 2022

Summary

This RFC outlines a proposal to implement support for nested Graphql Mutations.Nested mutations is the ability to perform mutations on a type other than the root type in GraphQL and how to define circular dependency schema files

Motivation

Most developers find it easier to think of "changes" in a sequential fashion. Databases can and do perform many update/insert/delete transactions concurrently. Any modern databases exposing any API (including GraphQL) has to be ready for concurrently arriving requests as well as nested mutations

Functional Specifications

Circular Reference

Nested Mutation Types

Referene

Nested mutations have been graphql/graphql-spec#252 but not yet approved

@sajeetharan sajeetharan added needs discussion rfc Request for comment labels Nov 21, 2022
@aaronpowell
Copy link
Contributor

aaronpowell commented Nov 25, 2022

Linking #906 as it has context on an outstanding bug that this poses

@aaronpowell
Copy link
Contributor

https://hasura.io/docs/latest/schema/common-patterns/data-modeling/many-to-many/ is how Hasura exposes relationships (specifically many-to-many as that's the cause of #906) and could serve as inspiration for how the structures could be defined.

@aaronpowell
Copy link
Contributor

This is probably a duplicate of #479

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants