Skip to content

Update _POP references #271

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

Merged
merged 1 commit into from
Jun 26, 2025
+5 −5
Merged

Update _POP references #271

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
10 changes: 5 additions & 5 deletions modules/ROOT/pages/mutations/update.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,9 +221,9 @@ a|
|===
====

=== `_POP`
=== `pop`

`_POP` expects a single `Int` value as input.
`pop` expects a single `Int` value as input.

Consider the following type definitions, a `Movie` with a property array called `tags`:

Expand All @@ -237,7 +237,7 @@ type Movie @node {

You can pop from this `tags` property array:

.Mutation with a single `_POP`
.Mutation with a single `pop`
====
[source, graphql, indent=0]
----
Expand Down Expand Up @@ -268,7 +268,7 @@ tags: ['a', 'b']

Or, for more than one property from the array:

.Mutation with two `_POP`
.Mutation with two `pop`
====
[source, graphql, indent=0]
----
Expand Down Expand Up @@ -311,7 +311,7 @@ type Movie @node {

Then, you can pop from both the `tags` and `moreTags` property arrays:

.Mutation with `_POP` from two different arrays
.Mutation with `pop` from two different arrays
====
[source, graphql, indent=0]
----
Expand Down