Skip to content

Docs on populatedByOperation #284

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
angrykoala merged 2 commits into from
Dec 17, 2025
Merged

Docs on populatedByOperation #284

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9529472
Docs on populatedByOperation
angrykoala Dec 9, 2025
3ffa999
Apply suggestions from code review
angrykoala Dec 15, 2025
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
23 changes: 22 additions & 1 deletion modules/ROOT/pages/directives/custom-logic.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -597,4 +597,25 @@ new Neo4jGraphQL({
})
----

Note that the second positional argument, in this case `_args`, has a type of `Record<string, never>`, and as such it will always be an empty object.
Note that the second positional argument, in this case `_args`, has a type of `Record<string, never>`, and as such it is always an empty object.
This is to maintain a compatible signature with GraphQL resolvers.


**`populatedByOperation`**

The `context` argument contains the field `populatedByOperation`.
This field is the mutation type that triggered the callback (`CREATE` or `UPDATE`).
`populatedByOperation` allows for different logic to be executed depending on the type of operation.
For example:

[source, javascript, indent=0]
----
const modifiedByCallback = async (_parent, _args, context) => {
if(context.populatedByOperation === "UPDATE"){
return context.username;
} else {
return "";
}
}
----