issues
search
exAspArk
/
batch-loader
:zap: Powerful tool for avoiding N+1 DB or HTTP queries
https://engineering.universe.com/batching-a-powerful-way-to-solve-n-1-queries-every-rubyist-should-know-24e20c6e7b94
MIT License
1.04k
stars
52
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Modifying list of items in-place causes items to be loaded multiple times
#44
smcgivern
closed
5 years ago
4
Split `cache` keyword from method replacement
#43
smcgivern
closed
5 years ago
5
GraphQL: using value from BatchLoader in another field
#42
holic
closed
5 years ago
5
Support for new GraphQL Interpreter
#41
JanStevens
closed
4 years ago
7
batchloader || result
#40
terencechow
closed
5 years ago
1
Returning a single result for a 1:Many relationship
#39
ro-savage
closed
5 years ago
2
Many to many relationship
#38
Derenge
closed
5 years ago
3
usage with sort?
#37
terencechow
closed
5 years ago
4
This created a regression where resolvers that do not *return* a `BatchLoader::GraphQL` fail to call `BatchLoader::GraphQL` calls that the resolver uses.
#36
maletor
closed
5 years ago
3
"Prime" items
#35
maletor
closed
5 years ago
3
Fix keyword arguments
#34
snwfog
closed
5 years ago
1
__loader method proc kwargs behaves differently on rb 2.1.0 vs 2.4.0
#33
snwfog
closed
5 years ago
5
Make BatchLoader work with the latest GraphQL versions
#32
exAspArk
closed
5 years ago
1
undefined method to_ary on ActiveRecord objects
#31
caleb
closed
5 years ago
6
Best Practice Using Batch loader on Graphql 1.8.11
#30
im-not-a-robot
closed
5 years ago
14
Fix batch key example for README.md
#29
stanhu
closed
5 years ago
2
Test GraphQL ruby gem 1.8 as well
#28
exAspArk
closed
5 years ago
1
Identify item by key object instead of key string representation
#27
DouweM
closed
5 years ago
6
Stopped batching requests since upgrading to GraphqQL version 1.8.7
#26
DamirSvrtan
closed
5 years ago
1
Will generate multiple queries
#25
maletor
closed
5 years ago
4
Fix 1:Many example in README.md
#24
shinyaK14
closed
6 years ago
2
Batch Load in GraphQL without a field attached to it.
#23
DamirSvrtan
closed
6 years ago
4
GraphQL v1.8.7 not compatible with Batch Loader
#22
JanStevens
closed
5 years ago
8
Using with GraphQL Pro authorization
#21
benkimball
closed
6 years ago
1
Trouble with has_many through
#20
rlb3
closed
6 years ago
3
Error with has_many relationship.
#19
rlb3
closed
6 years ago
3
Question: how to handle through association
#18
cabello
closed
6 years ago
3
Loading multiple items, they get attached to the wrong parent (GraphQL)
#17
alxx
closed
6 years ago
2
Batching 1:many loads all records on first object
#16
chadwilken
closed
6 years ago
2
Best practice for has_many relationship
#15
chadwilken
closed
6 years ago
0
Do not depend on #method_missing for #respond_to?
#14
ZJvandeWeg
closed
6 years ago
12
Queue for batching for `ActiveRecord::Relation` batching
#13
ZJvandeWeg
closed
6 years ago
2
Allow passing custom key to BatchLoader#batch
#12
exAspArk
closed
6 years ago
6
Using it with has_many through and polymorphic relationships
#11
chadwilken
closed
6 years ago
3
Make it thread-safe again
#10
exAspArk
closed
7 years ago
2
Use of source_location as hash key prevents abstracting BatchLoader calls
#9
bgentry
closed
6 years ago
3
Default value + Callable syntax
#8
bessey
closed
7 years ago
4
Support default batch value, with auto append
#7
bessey
closed
7 years ago
2
Use metaprogramming
#6
dlanileonardo
closed
6 years ago
16
Special array response syntax?
#5
bessey
closed
7 years ago
12
Don't redefine #method_missing
#4
ZJvandeWeg
closed
7 years ago
6
Fix arity bug in respond_to? method
#3
ZJvandeWeg
closed
7 years ago
7
Performance degradation 0.3.0 -> 1.0.0 -> 1.0.2
#2
richie
closed
7 years ago
10
uninitialized constant BatchLoader::Executor::Set (NameError)
#1
schovi
closed
7 years ago
1
Previous