starred/hoppscotch

Fork 0

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

[GH-ISSUE #4148] [bug]: JSON response body disappears intermittently when filtering response using JSONpath. #1489

New issue

Closed

opened 2026-03-16 20:33:11 +03:00 by kerem · 6 comments

kerem commented

2026-03-16 20:33:11 +03:00

Owner

Originally created by @MutasemAlfattal on GitHub (Jun 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4148

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When typing a Jpath query, the JSON response disappears.
This happens almost always but intermittently while im writing a query.
I need to click on Raw and click back on Json to see the response again, doing this will require me re writing the query.

https://github.com/hoppscotch/hoppscotch/assets/162300287/e4c3126c-1d58-4574-9767-6695bc0b527f

Steps to reproduce

1.Click on filter button
2.Start typing a Jpath Query

Environment

Production

Version

Cloud

Originally created by @MutasemAlfattal on GitHub (Jun 27, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4148 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When typing a Jpath query, the JSON response disappears. This happens almost always but intermittently while im writing a query. I need to click on Raw and click back on Json to see the response again, doing this will require me re writing the query. https://github.com/hoppscotch/hoppscotch/assets/162300287/e4c3126c-1d58-4574-9767-6695bc0b527f ### Steps to reproduce 1.Click on filter button 2.Start typing a Jpath Query ### Environment Production ### Version Cloud

kerem

2026-03-16 20:33:11 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 20:33:27 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jun 27, 2024):

@nivedin can you look into this?

@liyasthomas commented on GitHub (Jun 27, 2024): @nivedin can you look into this?

kerem commented

2026-03-16 20:33:32 +03:00

Author

Owner

@nivedin commented on GitHub (Jun 28, 2024):

@MutasemAlfattal thank you for reporting the issue, it should be fixed with #4151

@nivedin commented on GitHub (Jun 28, 2024): @MutasemAlfattal thank you for reporting the issue, it should be fixed with #4151

kerem commented

2026-03-16 20:33:38 +03:00

Author

Owner

@MutasemAlfattal commented on GitHub (Jun 28, 2024):

@nivedin Of course, and thank you for resolving the matter

@MutasemAlfattal commented on GitHub (Jun 28, 2024): @nivedin Of course, and thank you for resolving the matter

kerem commented

2026-03-16 20:33:43 +03:00

Author

Owner

@MutasemAlfattal commented on GitHub (Jul 9, 2024):

@nivedin This issue has reoccurred!

@MutasemAlfattal commented on GitHub (Jul 9, 2024): @nivedin This issue has reoccurred!

kerem commented

2026-03-16 20:33:48 +03:00

Author

Owner

@nivedin commented on GitHub (Jul 9, 2024):

@MutasemAlfattal the fix has not been merged to production yet.. will be live soon

@nivedin commented on GitHub (Jul 9, 2024): @MutasemAlfattal the fix has not been merged to production yet.. will be live soon

kerem commented

2026-03-16 20:33:53 +03:00

Author

Owner

@nivedin commented on GitHub (Jul 23, 2024):

@MutasemAlfattal the fix is live, you can take a look if it still persists feel free to re-open the issue

@nivedin commented on GitHub (Jul 23, 2024): @MutasemAlfattal the fix is live, you can take a look if it still persists feel free to re-open the issue