Fix graphql resolver complexity
Since 1.9 graphql always sets complexity for resolvers, which caused that our default resolver complexity proc wasn't used. Unless complexity is set explicitly then graphql now uses complexity `1`. To avoid this behavior, we use `complexity` method to set complexity to `0`, then when instantiating a field we use our default complexity proc if complexity is `0`.
Showing
Please register or sign in to comment