context is a Hash instead of GraphQL::Query::Context, causing runtime errors about graphql-ruby-fragment_cache HOT 5 CLOSED

That's what I was assuming, really good to know about RawValue in case I want to use it for other kinds of caching within GraphQL. I'm going to remove Pundit since it adds more complexity than is worth it.

Thanks for the help!

from graphql-ruby-fragment_cache.

Hi @kurtome, what version of graphql-ruby you have in your app? Is there a chance that you override a context method somewhere?

from graphql-ruby-fragment_cache.

@DmitryTsepelev It turns out my Pundit integration with GraphQL was misconfigured (some how the Field class for pundit was included on my base object). So that fixed the initial problem. Then I ran into #47.

And now, I'm running into a new error with Pundit:

No policy found for:\n\n- Type: Post\n- Runtime value: #<GraphQL::Execution::Interpreter::RawValue:0x00007f9390c66670 @object=[{...},{...}...] ... >`\

I'm considering removing Pundit completely at this point to get around this :)

from graphql-ruby-fragment_cache.

RawValue is way to tell interpreter that we have a value that is already resolved, so no further processing is required. Sounds like you cache a data that depends on the user and his permissions; in this case I'd rather not cache user–dependent data or patch Pundit somehow to let it know how to work with raw values (it holds the same data as a usual resolved object)

from graphql-ruby-fragment_cache.

Check out https://github.com/palkan/action_policy-graphql, it might be a better fit 😉

from graphql-ruby-fragment_cache.