Is your feature request related to a problem? Please describe.
When working with GraphQL SSE subscriptions, incoming events are displayed in a single shared subscription list. This becomes frustrating when there are many active subscriptions (10+) that fire frequently — I have to manually search through all events to find the ones belonging to a specific subscription. In contrast, the browser's Network tab already groups SSE events per connection under the "EventStream" tab, making it very easy to inspect events for a particular subscription.
Describe the solution you'd like
I'd like each subscription operation (e.g. subscription from demo site - PokemonAppeared) to have its own EventStream / Messages tab within the extension, similar to how the browser Network tab displays EventStream data per connection. Incoming SSE events should be routed to the corresponding subscription entry based on the operation name or subscription ID.
Ideally, events would be duplicated in both places:
The general subscription feed (as it works today) — for a unified chronological view of all events.
The individual subscription entry (e.g. PokemonAppeared) — with its own EventStream / Messages tab showing only events relevant to that specific subscription.
Describe alternatives you've considered
Adding a filter mechanism to the shared subscription list, where users could filter events by subscription operation name (e.g. typing PokemonAppeared to show only events belonging to that subscription). This approach might actually be an even more universal solution, since it would also benefit users working with WebSocket-based subscriptions, not just SSE.
Additional context
A live demo reproducing this scenario is available at: https://graphql-mock-service-de771830b5b1.herokuapp.com/
In this demo, subscribing to PokemonAppeared generates SSE events. In the browser Network tab, these events are neatly visible under the EventStream tab for that specific connection. However, in the GraphQL Network Inspector extension, all subscription events are mixed together, requiring manual identification of which event belongs to which subscription.
Is your feature request related to a problem? Please describe.
When working with GraphQL SSE subscriptions, incoming events are displayed in a single shared subscription list. This becomes frustrating when there are many active subscriptions (10+) that fire frequently — I have to manually search through all events to find the ones belonging to a specific subscription. In contrast, the browser's Network tab already groups SSE events per connection under the "EventStream" tab, making it very easy to inspect events for a particular subscription.
Describe the solution you'd like
I'd like each subscription operation (e.g. subscription from demo site - PokemonAppeared) to have its own EventStream / Messages tab within the extension, similar to how the browser Network tab displays EventStream data per connection. Incoming SSE events should be routed to the corresponding subscription entry based on the operation name or subscription ID.
Ideally, events would be duplicated in both places:
The general subscription feed (as it works today) — for a unified chronological view of all events.
The individual subscription entry (e.g. PokemonAppeared) — with its own EventStream / Messages tab showing only events relevant to that specific subscription.
Describe alternatives you've considered
Adding a filter mechanism to the shared subscription list, where users could filter events by subscription operation name (e.g. typing PokemonAppeared to show only events belonging to that subscription). This approach might actually be an even more universal solution, since it would also benefit users working with WebSocket-based subscriptions, not just SSE.
Additional context
A live demo reproducing this scenario is available at: https://graphql-mock-service-de771830b5b1.herokuapp.com/
In this demo, subscribing to PokemonAppeared generates SSE events. In the browser Network tab, these events are neatly visible under the EventStream tab for that specific connection. However, in the GraphQL Network Inspector extension, all subscription events are mixed together, requiring manual identification of which event belongs to which subscription.