You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The default (given subscriptions might be more common than live queries)
A UI option that appears if your fetcher returns an observable
A prop passed to the component
Or something else.
The text was updated successfully, but these errors were encountered:
stubailo
changed the title
Have option to show observable results in a log
Feature: Option to show observable results in a log
Apr 16, 2017
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.
I don't think graphiql is useful for subscriptions without this feature even - for example, this bug: #652
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.
The text was updated successfully, but these errors were encountered: