yume/juniper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix typos in dataloader docs

Browse source
This commit is contained in:
Christian Legnitto 2020-04-25 20:26:16 -10:00 committed by GitHub
parent 9e554981ee
commit 892619a35b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/book/content/advanced/dataloaders.md
View file

@ -1,7 +1,7 @@
# Avoiding the N+1 Problem With Dataloaders # Avoiding the N+1 Problem With Dataloaders
A common issue with graphql servers is how the resolvers query their datasource. A common issue with graphql servers is how the resolvers query their datasource.
his issue results in a large number of unneccessary database queries or http requests. This issue results in a large number of unneccessary database queries or http requests.
Say you were wanting to list a bunch of cults people were in Say you were wanting to list a bunch of cults people were in
```graphql ```graphql
@ -129,7 +129,7 @@ impl Cult {
Once created, a dataloader has the functions `.load()` and `.load_many()`. Once created, a dataloader has the functions `.load()` and `.load_many()`.
When called these return a Future. When called these return a Future.
In the above example `cult_loader.load(id: i32)` returns `Future<Cult>`. If we had used `cult_loader.load_may(Vec<i32>)` it would have returned `Future<Vec<Cult>>`. In the above example `cult_loader.load(id: i32)` returns `Future<Cult>`. If we had used `cult_loader.load_many(Vec<i32>)` it would have returned `Future<Vec<Cult>>`.
### Where do I create my dataloaders? ### Where do I create my dataloaders?