starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #5431] [feature]: option to clear the response panel #2087

New issue

Closed

opened 2026-03-16 23:07:48 +03:00 by kerem · 7 comments

kerem commented

2026-03-16 23:07:48 +03:00

Owner

Originally created by @12fahed on GitHub (Oct 2, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5431

Is there an existing issue for this?

I have searched the existing issues

Summary

the existing system has many options like copy, save, view, download but there is need of clearing the response where the user can clear as when needed.

picture below shows the missing option

Why should this be worked on?

user might want to clear the response log to avoid confusion while switching the tabs within the website between multiple API requests to maintain readability.

Originally created by @12fahed on GitHub (Oct 2, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5431 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary the existing system has many options like copy, save, view, download but there is need of clearing the response where the user can clear as when needed. picture below shows the missing option <img width="1370" height="200" alt="Image" src="https://github.com/user-attachments/assets/dfe6db12-a1d3-4762-9db1-78e1c1b35e55" /> ### Why should this be worked on? user might want to clear the response log to avoid confusion while switching the tabs within the website between multiple API requests to maintain readability.

kerem

2026-03-16 23:07:48 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 23:08:05 +03:00

Author

Owner

@12fahed commented on GitHub (Oct 3, 2025):

@abraham i would love to work on this feature, can i ?

@12fahed commented on GitHub (Oct 3, 2025): @abraham i would love to work on this feature, can i ?

kerem commented

2026-03-16 23:08:10 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 3, 2025):

Hi @12fahed, I’m curious to understand the reasoning behind your request to clear the response pane. Did you simply want to make it look clean and maintain readability?

I’m concerned about the potential impact on other entries in the response pane, such as Headers or Test results. There seems to be some ambiguity in this feature request. I’d appreciate it if you could provide more details and discuss it before we begin implementing it.

@liyasthomas commented on GitHub (Oct 3, 2025): Hi @12fahed, I’m curious to understand the reasoning behind your request to clear the response pane. Did you simply want to make it look clean and maintain readability? I’m concerned about the potential impact on other entries in the response pane, such as Headers or Test results. There seems to be some ambiguity in this feature request. I’d appreciate it if you could provide more details and discuss it before we begin implementing it.

kerem commented

2026-03-16 23:08:15 +03:00

Author

Owner

@12fahed commented on GitHub (Oct 3, 2025):

Hi @12fahed, I’m curious to understand the reasoning behind your request to clear the response pane. Did you simply want to make it look clean and maintain readability?

I’m concerned about the potential impact on other entries in the response pane, such as Headers or Test results. There seems to be some ambiguity in this feature request. I’d appreciate it if you could provide more details and discuss it before we begin implementing it.

Hi @liyasthomas thanks for engaging. The core reason is to prevent mistakes during iterative testing.

When users send multiple requests rapidly, old responses clutter the panel. It becomes easy to misread a previous response as the latest one, leading to incorrect conclusions.

To clarify the scope: The "Clear" action should only reset the current view, the main Response Body and Headers. It should not affect the saved History or Test Results, which are separate logs.

It's a standard UX feature in tools like Postman/Insomnia (you can refer this video for clarification) for maintaining a clean, focused workspace during active debugging.

Hope this clarifies the intent!

@12fahed commented on GitHub (Oct 3, 2025): > Hi [@12fahed](https://github.com/12fahed), I’m curious to understand the reasoning behind your request to clear the response pane. Did you simply want to make it look clean and maintain readability? > > I’m concerned about the potential impact on other entries in the response pane, such as Headers or Test results. There seems to be some ambiguity in this feature request. I’d appreciate it if you could provide more details and discuss it before we begin implementing it. Hi @liyasthomas thanks for engaging. The core reason is to **prevent mistakes during iterative testing.** When users send multiple requests rapidly, old responses clutter the panel. It becomes easy to misread a previous response as the latest one, leading to incorrect conclusions. To clarify the scope: The "**Clear**" action should only reset the current view, the **main Response Body and Headers**. It **should not** affect the saved History or Test Results, which are separate logs. It's a standard UX feature in tools like Postman/Insomnia ([you can refer this video for clarification](https://user-images.githubusercontent.com/1040583/225614099-3c86cbe7-a0ea-4500-babe-3a1ac3b58eae.gif)) for maintaining a clean, focused workspace during active debugging. Hope this clarifies the intent!

kerem commented

2026-03-16 23:08:20 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 3, 2025):

That’s an interesting perspective. It’s fair enough. You can give it a try.

@liyasthomas commented on GitHub (Oct 3, 2025): That’s an interesting perspective. It’s fair enough. You can give it a try.

kerem commented

2026-03-16 23:08:25 +03:00

Author

Owner

@12fahed commented on GitHub (Oct 3, 2025):

Hello @liyasthomas , I have created a PR for this feature #5435

Could you please review it ?

@12fahed commented on GitHub (Oct 3, 2025): Hello @liyasthomas , I have created a **PR for this feature #5435** Could you please review it ?

kerem commented

2026-03-16 23:08:30 +03:00

Author

Owner

@12fahed commented on GitHub (Oct 26, 2025):

Hello @liyasthomas i had created PR #5435, its been almost 3 weeks now, there isnt any update, could you please review it ?

@12fahed commented on GitHub (Oct 26, 2025): Hello @liyasthomas i had created PR #5435, its been almost 3 weeks now, there isnt any update, could you please review it ?

kerem commented

2026-03-16 23:08:35 +03:00

Author

Owner

@12fahed commented on GitHub (Nov 26, 2025):

closing this issue as the PR #5435 is accepted and scheduled for next major release, thank you @jamesgeorge007 and @nivedin

@12fahed commented on GitHub (Nov 26, 2025): closing this issue as the PR #5435 is accepted and scheduled for next major release, thank you @jamesgeorge007 and @nivedin

kerem referenced this issue

2026-03-17 01:16:51 +03:00

[PR #2243] [MERGED] Open API support for post/put body schemas #3690

kerem referenced this issue

2026-03-17 02:37:56 +03:00

[PR #5322] [MERGED] feat(common): add support for post/put body schemas in openapi import #5156