Skip to content

Fix Headings on Relational Data Guide #824

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.

Sign up for GitHub

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

Open
kheiner wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix Headings on Relational Data Guide #824

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions content/guides/04.connect/4.relations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,11 @@ data of a relational field [the `fields` parameter](/guides/connect/query-parame
queries in GraphQL. This allows you to retrieve the author of your article included in the articles data, or fetch
related log entry points for your app's analytics data for example.

### Creating / Updating / Deleting
## Creating / Updating / Deleting

Similarly to fetching, relational content can be modified deeply as well.

#### Many-to-One
### Many-to-One

Many-to-One relationships are fairly straightforward to manage relationally. You can submit the changes you want
as an object under the relational key in your collection. For example, if you wanted to create a new featured article on
Expand Down Expand Up @@ -49,7 +49,7 @@ nullifying the field:
}
```

#### One-to-Many and Many-to-Many
### One-to-Many and Many-to-Many

One-to-Many, and therefore Many-to-Many and Many-to-Any, relationships can be updated in one of two ways:

Expand Down Expand Up @@ -179,7 +179,7 @@ Alternatively, you can provide an object detailing the changes as follows:
This is useful if you need to have more tightly control on staged changes, or when you're working with a big relational
dataset.

#### Many-to-Any (Union Types)
### Many-to-Any (Union Types)

Many-to-Any fields work very similar to a "regular" many-to-many, with the exception that the related field can pull in
the fields from any of the related collections, for example:
Expand Down
Loading