docs: Description + example of GraphQL dataloader #3290
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I had a problem recently with a cart of more than 15 items becoming incredibly slow to load. It turned out to be the n+1 problem. And although it ultimately turned out to be another kind of n+1 issue than I thought, I decided to return to the topic of
dataloadersand it turns out you can use them through standardnestjsSince dataloaders are an important part of the GraphQL toolbox, but not broadly understood or used, I have added documentation + an example with a re-usable skeleton so people can get around the performance related issues it solves with ease.
Breaking changes
No
Screenshots
Checklist
📌 Always:
👍 Most of the time: