Specs fail when testing cached fields about graphql-ruby-fragment_cache HOT 3 CLOSED

Hey @jeromedalbert, could you please try to use then? Something like resolved.then { |value| ... }

from graphql-ruby-fragment_cache.

No luck with that, it returns a GraphQL::Execution::Lazy too

from graphql-ruby-fragment_cache.

I think the root cause of the problem is that my resolve helper code does not define any query in GraphQL::Query.new. That is why I am getting errors about a nil operation_type, since no operation (query or mutation or subscription) is defined.

Just for the heck of it I passed a placeholder query GraphQL::Query.new(MyAppSchema, 'query { posts { title } }', context: context) and did resolved.value, but that gives me the following:

NoMethodError: undefined method `map' for nil:NilClass
from /Users/jerome/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/graphql-fragment_cache-1.13.1/lib/graphql/fragment_cache/cache_key_builder.rb:177:in `bl
ock in path_cache_key'

because the CacheKeyBuilder path is nil. It makes sense since I am trying to shoehorn a query that is not being executed the normal way.

graphql-ruby-fragment_cache needs a path to compute its cache key, but my resolve helper code never provides one. As is, the helper code is incompatible with the gem. It might be possible to make it work by making the helper "backfill" a query from the field name, and there would still be this nil path issue to figure out. But I think it is overkill and the simplest solution is probably to disable cache processing with #90.

from graphql-ruby-fragment_cache.