Issues
- 5
Incompatibility with graphql-ruby 2.0.18+
#87 opened by swrobel - 6
Incompatibility with graphql-ruby 2.3.x
#90 opened by gstokkink - 6
undefined method to_ary on ActiveRecord objects
#31 opened by caleb - 1
- 0
`BatchLoader::GraphQL.for` doesn't delegate missing methods as `BatchLoader.for` does
#86 opened by stanhu - 1
batchloader || result
#40 opened by terencechow - 5
- 0
BatchLoader::GraphQL with union type
#83 opened by Curter29 - 0
Erro on principal node is object
#81 opened by heliocaruccio - 1
How to debug the code inside batch loader block
#78 opened by xchen1189 - 0
Loading across collections
#77 opened by ivanyv - 6
- 14
batch-loader not working for non-nullable graphql fields, returns "Cannot return null for non-nullable field"
#68 opened by bbugh - 2
How I can filter associations values?
#70 opened by kalfaro - 3
Warnings after updating to Ruby 2.7
#69 opened by sjovanelly - 6
N+1 query problem with GraphQL (client side)
#54 opened by mauro-ni - 2
- 2
Searchkick(elasticsearch) Object Associations
#63 opened by xgrei - 4
- 7
Support for new GraphQL Interpreter
#41 opened by JanStevens - 4
- 2
N+1 queries when batch loading has many association
#59 opened by tjvc - 1
- 2
Possibility of deadlock
#55 opened by JanStevens - 4
- 7
Update docs for latest graphql
#48 opened by davidw - 7
Consider new name or alias for 'call'
#50 opened by davidw - 4
- 5
- 5
Split `cache` keyword from method replacement
#43 opened by smcgivern - 4
usage with sort?
#37 opened by terencechow - 2
- 3
"Prime" items
#35 opened by maletor - 3
This created a regression where resolvers that do not *return* a `BatchLoader::GraphQL` fail to call `BatchLoader::GraphQL` calls that the resolver uses.
#36 opened by maletor - 5
- 3
Many to many relationship
#38 opened by Derenge - 14
- 1
- 4
Will generate multiple queries
#25 opened by maletor - 8
- 4
- 1
Using with GraphQL Pro authorization
#21 opened by benkimball - 3
Trouble with has_many through
#20 opened by rlb3 - 3
Error with has_many relationship.
#19 opened by rlb3 - 3
Question: how to handle through association
#18 opened by cabello - 2
- 2
- 2
- 0
Best practice for has_many relationship
#15 opened by chadwilken - 3