Robert Mosolgo

Hey, sorry for the disruption there. Initializing Mutations outside of query execution isn't a formally supported API, but I'm glad you found something that works. In a pinch, another way...

This is all released in 2.4.0

Hey, thanks for the detailed write-up. I definitely agree that this should be supported one way or another, I'll just have to take a look at how it can be...

Hey, thanks for the detailed writeup. I also don't know of any way of getting the current input path. I'm open to adding it but I think the trick will...

Hey, thanks for opening this issue to discuss this further. In my eyes, there are a few things to consider: - GraphQL-Ruby should move from `Timeout.timeout` to a manually-decremented timeout...

> completely avoidable Yes, you could _also_ do it in the resolver. But using `loads:` also supports Relay-style UUIDs (since it goes through `Schema.object_from_id`) and it also does GraphQL-level authorization...

Some Fiber-related tests are failing due to: https://bugs.ruby-lang.org/issues/21401

👋 Thanks for the detailed report here! Yes, if `private_context_fingerprint_for` is being called here, something is definitely off! One thing that jumped out at me is that, although you have...

:+1: That should do the job for `field_class ...`. Hopefully `messages: ...` will give us the clue we need!

Thanks, there's our answer: ```ruby "Encountered private field: Node.id" ``` Can you confirm that by removing `id` from the query string, and seeing that `private_context_fingerprint_for` is _not_ called? Probably the...