Jonathan Brennan

@tom-quiltt @faizan-siddiqui additional information about your setup or, even better, a running example would help with troubleshooting.

This is currently possible by passing in your own [fetcher](https://github.com/graphql/graphiql/tree/main/packages/graphiql#using-as-package). That said, passing in a `METHOD` option to the default fetcher seems like it could be a reasonable upgrade. @acao,...

Hello @francipvb 👋! As @acao mentioned, I've been working on a prototype of the new GraphiQL design. The primary goal of the prototype is to test and validate the new...

I've just started digging into the work that @thomasheyenbrock has been doing to move components into `@graphiql/react`, as Step 1 above, and the breaking change concerns from @n1ru4l have become...

I'm not a huge fan of the children pattern going forward, as the new design allows for _more_ customization and I think exposing these options as typed props is a...

@dylanowen I'm working on a small PR (#2778 ) to update some styling that's unrelated to this PR, but getting a failing test that _is_ part of this PR. ```...

ahh...there it is. Thanks for the explanation, makes sense now. I've got the fix in with #2778.

I think you've a good point...the Doc Explorer isn't in the DOM by default anymore (it must have been when you added your test), so I added a fireEvent to...

I've got a branch locally that has ladle installed in `@graphiql/react` that's helping me to do some visual component testing and file shuffling/organization. I've also got existing testing code [in...

Also, I was tripped up for at least a couple of hours because I was unaware that I needed to add exported modules from `@graphiql/react` to the [mock that `@graphiql`...