Open stubailo opened 7 years ago
Sounds useful.
Exposing this in the UI is hard because it relies on making, gulp, design decisions. I do have some notions for what this could look like, but I am not a designer.
@AGS- worked on getting the history pane, but it doesn't save the results yet. Maybe we should?
I think to start with, adding a prop to configure this would be sufficient.
I don't think graphiql is useful for subscriptions without this feature even - for example, this bug:
this remains an often requested feature now that we have documented support for observables and (async iterables as well - multipart IncrementalDelivery, etc). The IncrementalDelivery
appends/sets results for @stream or @defer like it's supposed to, and subscriptions should do something like this ticket describes, and be able to be executed alongside a mutation if possible (this is a common workflow when testing graphql subscriptions!).
GraphiQL supports both promise and observable fetchers, which let us really easily add support for GraphQL subscriptions. However, this approach just shows the most recent subscription result.
If there was an option somewhere to show a log of all observable results instead of just the most recent one, that would be super useful! I'm not sure if it should be:
Or something else.