Add structured HTTP history filters beyond free text and scope
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the Workbench history view and its existing text and scope filter implementations, then trace how HTTP exchanges are stored and searched. The issue names no files or tests, so locate the relevant entry points and add coverage for combined filters, reset behavior, and responsiveness. Done means the structured fields compose with existing filters, the UI remains responsive at the stated limit, and the Workbench documentation explains fields and precedence.
Written by the indexing model from the issue text.
Description
Context
The parity matrix marks history filtering as Partial: 0.1.0 has a free-text
filter and a scope view filter. Burp-style triage needs structured filters that
can be combined without turning the query into a regex.
Proposal
Add a filter row or panel for fields such as:
- method and status code/range;
- host and URL/path substring or regex;
- response MIME type and extension;
- request/response body size;
- has notes / has response / in scope;
- time range.
Filters should compose with the existing text filter and scope view. Show a
clear active-filter summary and a reset action. Keep filtering responsive on the
2,000-exchange in-memory limit and design it to work against persistent history.
Acceptance criteria
- Multiple structured filters combine predictably.
- The current text and scope filters keep working.
- Empty results and reset behavior are clear.
- Filtering is covered by tests and uses no blocking work on the UI thread.
- Workbench documentation lists the filter fields and precedence.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 24m
- Merged PRs (30d)
- 52
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from andyintheshell/perseid
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
andyintheshell/perseid#73 ·
Maintainers usually reply within 1 day
-
enhancement help wanted priority: p3
Difficulty 5/5 Over a week Newbie friendliness 25/100
andyintheshell/perseid#72 ·
Maintainers usually reply within 1 day
-
enhancement priority: p3
Difficulty 5/5 Over a week Newbie friendliness 35/100
andyintheshell/perseid#71 ·
Maintainers usually reply within 1 day
-
enhancement priority: p3
Difficulty 5/5 Over a week Newbie friendliness 35/100
andyintheshell/perseid#70 ·
Maintainers usually reply within 1 day
-
accessibility enhancement help wanted priority: p2
Difficulty 5/5 Over a week Newbie friendliness 38/100
andyintheshell/perseid#69 ·
Maintainers usually reply within 1 day
All issues in andyintheshell/perseid
Similar issues
-
checkpoint/verify/rebuild_indexes on a thread holding a WriteTransaction deadlock instead of INT-001Openbug known-issue
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
project-minigraf/minigraf#734 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Nimblesite/lspkit#26 ·
Maintainers usually reply within 1 day