Robert Mosolgo

Yes, that's right -- fields can be cacheable and objects can be cacheable ... and fields that return objects are only cacheable if _both_ the field _and_ the object are...

I think we've addressed the issues raised here ... if I've missed anything, please let me know and I'll reopen this!

Hey! In general, your implementation above seems good to me. It looks like `Query::Variables` could be improved to have a first-class API for setting new values. As a slight improvement,...

Glad you found a workaround for it! Just to make sure I understood, instead of a tuple, you're doing: ```graphql type MobiledocCard { name: String! payload: CardPayload! } # This...

👋 Thanks for the detailed report and sorry about the trouble. I replicated the bug and I've got a fix in the works at #5386

Great point, @spacebat. I opened https://github.com/rmosolgo/graphql-ruby/pull/5409 to switch that around.

I made a few changes over in https://github.com/rmosolgo/graphql-ruby/pull/5077 - I added some debugging info to the failing tests around object shapes. I think something about the implementation of `def comment`...

Awesome. Thanks again for all your work to make this happen!

Oh, yes, I just released it! Thanks again for this improvement :+1:

Hey, thanks for the detailed writeup. Off the top of my head, I don't know a way to make serialization faster. I would have suggested `RawObject`, but as you noticed,...