Add Send to Decoder from message editors and history
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- desktop, developer-experience
Research direction
Start by reading the Decoder implementation and the HTTP history and message detail entry points, then trace how they represent selected and full message bytes. Check how Repeater, Intruder, and WebSocket detail expose messages, and add tests for binary selections, full request and response contents, and existing chains. Done means the action is available in the required views, preserves bytes, warns before reusing a chain, and has documentation.
Written by the indexing model from the issue text.
Description
Context
Decoder supports stacked Text/Hex panels and selection-aware transforms, but
there is no way to move captured data into it. The parity matrix lists Send to
Decoder as a remaining M3 gap.
Proposal
- Add a context-menu action to send a request, response, or current selection to
Decoder. - Offer it from HTTP history, the message detail panes, Repeater, Intruder, and
WebSocket detail where a selection exists. - Open a new Decoder chain or append a panel, with a clear choice when a chain is
already open. - Preserve exact selected bytes; do not route binary data through lossy text
conversion. If the user sends a displayed Pretty body, label the source and
decoded/derived nature.
Acceptance criteria
- At least HTTP history and the main message detail offer Send to Decoder.
- The action preserves the selected bytes and handles binary content.
- A full request/response includes the expected head and body.
- Existing Decoder chains are not overwritten without warning.
- Tests and documentation are added.
- 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 70/100
bitcoindevkit/electrum_streaming_client#57 ·
Maintainers usually reply within 2 days