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.

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

Update handling-n-plus-one.mdx #3175

Merged
merged 1 commit into from
Oct 28, 2024
Merged

Update handling-n-plus-one.mdx #3175

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
2 changes: 1 addition & 1 deletion docs/source/entities/handling-n-plus-one.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ type Product @key(fields: "id") {
</CodeColumns>


Most subgraph implementations use _reference resolvers_ to returns the entity object corresponding to a key.
Most subgraph implementations use _reference resolvers_ to return the entity object corresponding to a key.
Although this pattern is straightforward, it can diminish performance when a client operation requests fields from many entities.
Recall the `topReviews` query, now in the context of a federated graph:

Expand Down