Robert Mosolgo

Thanks for sharing your thoughts about it! I'll make some time to land this PR soon.

Thanks for opening this discussion and for the link to those docs. I meant to pick something that matched Pundit conventions, but I might have gotten the wrong idea! I'll...

Sorry for the inconvenient name on this one ... in practice, I don't expect to change this in the library, given how long it's been in use, but if you'd...

Sorry for the nasty surprise! It's technically a _feature_ -- we support dynamically hiding some parts of the schema, and as you noticed, when all of an interface's implementors are...

Sorry I haven't left a proper review for this yet. I've been trying to think of how this new suggestion meshes with the use of lookahead which I had in...

Sorry for the slow turn around here. I noticed that `lookup_alias_node` was recursive, but I wanted to pull the branch and try it myself. I've added a test that demonstrates...

Thanks for the update on that. I'm still hung up on the treatment of `arguments:`, where the method accepts an `arguments:` input, but then overwrites it with `query.arguments_for(...)`. The _intended_...

Hmm, sorry for the trouble! I would have expected Rails's autoloader to handle this fine, where it references those classes even though the file hasn't finished loading yet. Unfortunately, `Types::BaseObject`...

It looks like that function _expects_ `observer` to be given as an argument: https://github.com/rmosolgo/graphql-ruby/blob/d1ca69a3daf93286c529e8fccb6e108c4370fb5b/javascript_client/src/subscriptions/createActionCableHandler.ts#L16 Could you please share the full error message and backtrace? > let me know if you...

No, there's not a way to simply ignore them, but I can see the value here. I think there's some similar feature where we're more lax about incoming values, for...