Caching connection types is broken against graphql-ruby 1.9
thebadmonkeydev opened this issue · 0 comments
thebadmonkeydev commented
There was a change to the way relay connections are wrapped post resolution (or at least by the time we resolve the cache proc). Now when there is a cache hit against a relay connection field, we need to ensure that the result coming back from our resolver is a proper subclass of GraphQL::Relay::BaseConnection
.
When the GraphQL::Relay::EdgesInstrumenter
runs, it is working with an object that it is not expecting and a NoMethodError: no method 'edge_nodes' for <class of cached object>
.