[JSON View] Save N Recent Filters

[nk-tedo-001]

Description

Add the ability to save and quickly access the most recent JSON filters in the JSON View, similar to how DBeaver handles recent filters.

Why this feature/change is important?

When working with large and complex JSON responses, I frequently reuse the same filter expressions across multiple requests. Having a list of recently used filters would significantly speed up analysis, reduce repetitive typing, and improve overall usability of the JSON View.

[NghiaTranUIT]

@nk-tedo-001 can you give me an example how your JSON query looks like? Do you use JSON Path or JSON Query or normal key-value JSON filter?

[nk-tedo-001]

@NghiaTranUIT I mostly use JSONPath and jq.

[NghiaTranUIT]

Cool, I will add this small feature, so you can save your filter 👍

[nk-tedo-001]

Cool, I will add this small feature, so you can save your filter 👍

Thanks! I just want to clarify that DBeaver saves it automatically when you press Enter.

[nunogoncalves-jt]

Thanks for this!
I may be interpreting this differently than my original request. I would like the query to be present in the request until it's deleted, even after changing requests. That way we can quickly toggle between two requests and check related information without having to re activate/re select the proper query. I'm not sure it's already how you're implementing it, or even if it's easily or even possible, but I'll let the request here.

If both requests have the same query because they just change page or something like that, we would simply apply the same query in each request and it would work the same way as different queries per request.

[NghiaTranUIT]

I would like the query to be present in the request until it's deleted, even after changing requests. That way, we can quickly

@nunogoncalves-jt this logic is already implemented. When you change the requests, the query filter in the JSON doesn't reset, and it is automatically applied (see the video)

CleanShot.2026-02-27.at.23.05.55.mp4

[nunogoncalves-jt]

Yeah, what I meant was that each request got its own query.
req1 = query1
req2 = query2
re1 = query1
req2=query2
and so on.

But I understand that it would go against having the same query for all requests as it is now.

[NghiaTranUIT]

@nunogoncalves-jt it's hard to design UX for your case because: how do we know what request should use what query? The best solution to fix it is to use the Save Filter buttons, so you can switch it quickly without typing it again.

[NghiaTranUIT]

@nunogoncalves-jt @nk-tedo-001 let's try this beta build: https://assets.proxyman.com/beta/Proxyman_6.6.0_Save_JSON_Filter.dmg

• Save your JSON filter
• Click to apply the filter
  

[nk-tedo-001]

@nunogoncalves-jt @nk-tedo-001 let's try this beta build: assets.proxyman.com/beta/Proxyman_6.6.0_Save_JSON_Filter.dmg

* Save your JSON filter

* Click to apply the filter
  ![Save JSON Filter](https://github.com/user-attachments/assets/eeca5271-bc61-4305-9b0d-68e1b1384519)

From what I can see, it works fine! 🎉
There are just two minor points:

1. It needs some UI polish.

2. The Rename popup field should be prefilled with the old name.

[NghiaTranUIT]

Thanks, I will fix it 👍