Azure / Azure/data-api-builder

Support Nested GraphQL Mutations

Open
#990 3 comments 2 reactions 0 assignees View on GitHub
graphql needs discussion rfc
Dominant language
C#
Stars
1.5k
Forks
370
Avg merge
3d 22h
Merged PRs (30d)
9

Description

# 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 https://github.com/graphql/graphql-spec/issues/252 but not yet approved

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the nested-mutation proposal and the referenced GraphQL specification issue #252. No implementation entry point, file, or test is named; clarify the circular-reference and nested-mutation requirements before defining acceptance tests and an implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, graphql
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.