After upgrading to GraphiQL v5, we appear to have lost the ability to view query history, which was previously available in the side menu under “Show Collection.”
Problem Statement
When investigating issues, we often work with many GraphQL queries simultaneously. The absence of query history has made this workflow significantly harder.
Specifically:
Loss of Query History
- Earlier, query history allowed quick switching between previously executed queries.
- Now, with many query tabs open (often 50+), it’s very easy to lose track of prior queries.
- Scrolling through tabs to find an earlier query is impractical and inefficient.
Tab Reuse Based on Operation Name
If a query with a certain operation name is already open in one of the tabs, opening a new query link with the same operation name:
Automatically reuses an existing tab. Replaces the query variables and state to match the newly opened link.
This behavior makes comparisons difficult.
Impact on Debugging Workflow
- When a new issue is reported:
- I often need to keep the original query open for reference.
- Then open a modified or entirely new query in a separate tab.
- Since new queries may overwrite existing tabs and new tabs are added at the end, finding earlier queries becomes extremely difficult without history support.
Why This Matters
Issue investigation commonly requires switching back and forth between multiple queries.
Query history provided a reliable, searchable way to navigate previous work.
The current tab behavior increases cognitive overhead and slows down debugging.
Requested Solutions (in order of preference)
Restore the Query History feature
- Bring back the previous “query history / collection” view in the side menu.
- This would immediately solve the problem of navigating between previously run queries.
OR
Change Tab Behavior
- Always open query links in a new tab, regardless of matching operation names.
- Do not reuse or override existing tabs automatically.
Either of the above would significantly improve productivity and restore a workable investigation flow.
After upgrading to GraphiQL v5, we appear to have lost the ability to view query history, which was previously available in the side menu under “Show Collection.”
Problem Statement
When investigating issues, we often work with many GraphQL queries simultaneously. The absence of query history has made this workflow significantly harder.
Specifically:
Loss of Query History
Tab Reuse Based on Operation Name
If a query with a certain operation name is already open in one of the tabs, opening a new query link with the same operation name:
Automatically reuses an existing tab. Replaces the query variables and state to match the newly opened link.
This behavior makes comparisons difficult.
Impact on Debugging Workflow
- I often need to keep the original query open for reference.
- Then open a modified or entirely new query in a separate tab.
Why This Matters
Issue investigation commonly requires switching back and forth between multiple queries.
Query history provided a reliable, searchable way to navigate previous work.
The current tab behavior increases cognitive overhead and slows down debugging.
Requested Solutions (in order of preference)
Restore the Query History feature
OR
Change Tab Behavior
Either of the above would significantly improve productivity and restore a workable investigation flow.