feature: abctl: explanation of / (filter) function
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 40
- Avg merge
- 12h 17m
- Merged PRs (30d)
- 156
Description
Feature Description
More TUI verbiage around what the / key, filter, which lets the user filter to a subset of events based on substring matches to the METHOD, does.
This isn't obvious. The TUI merely presents the string "filter..." and the user doesn't know what is happening. Some users expected a query language, to filter on something like DURATION > 5s.
Proposed Solution
Step 1 is to replace the filter ... prompt with something like METHOD name filter...
We can also discuss offering something like JQuery language to allow users to filter for e.g. DURATION > 5s.
Want to contribute?
- I would like to work on this issue.
Additional Context
No response
Contributor 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.
Research direction
In the abctl TUI, locate the code that displays the / filter prompt and inspect how the prompt text is assembled. Update the wording so it explains that filtering matches substrings in METHOD values, then verify the prompt and existing filter behavior in the TUI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100