Matt Bessey

Oh sweet, I had a look at that but misinterpreted it as only a type generator. I am or by the sounds of it was using this package to do...

FYI I got around to writing up my use case, just in case you were interested in more details https://bessey.io/blog/2018/08/05/apollo-graphql-prefetching/

I _think_ in this case my issue is that `await browser.wait(Until.elementIsNotVisible(...))` does not work how I expected it to. My hope was I could validate that an element that was...

Also running into this. Its not a huge thing but a slightly more precise temporary solutions is: ```ruby user = swallow_warden_throws { env["warden"].user } def swallow_warden_throws catch(:warden) do result =...

> More broadly, as I've noted a few times, there's several moving parts here that lead to a high risk for disastrous integration-level bugs: Dataloaders, array handling, and scope re-authorization...

Hey, apologies for asking in the wrong place, would you rather move this discussion elsewhere? My email is [email protected]

Adding a +1 as I've also just run into this while working on our higher order type renaming framework. Like @IvanChibisov we are leveraging `loads:` and changesets in a `RelayClassicMutation`,...

I've done a little bit of pry debugging and I have established that this is the problem: https://github.com/rmosolgo/graphql-ruby/blob/5b938754cdbcf0eefa3b0b70bc794e1b3336046b/lib/graphql/schema/member/has_arguments.rb#L62 Since `get_argument` is not passed a `context` it falls back to a...

👍 Well I've already handled this one case the type extension way. It's not too bad. It did take me a while to wrap my head around the fact that...

I ran into https://github.com/rmosolgo/graphql-ruby/issues/4564 while working on a solution to this issue. In case it inspires an upstream API to get built heres ours: We built a mixin for all...