Reflect filter selections in the search query input
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
Selecting a value in the filter sidebar applies it to the search, but the query input doesn't show it. Filter state and query text live in two places, so the input never reflects the full set of conditions actually being applied.
Make the two representations one: selecting a filter writes the corresponding condition into the query input, and editing the query updates the filter selections to match.
Notes:
- Needs to work for both query dialects the input supports, which is the main source of complexity — round-tripping requires parsing query text back into filter state, not just generating it.
- Today this is partially addressed by pills rendered below the input, which surface that filters are applied without making them editable as query text.
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
Start at the filter sidebar and query input, then trace how the existing filter state, query text, and rendered filter pills are connected. Check both supported query dialects and identify the parsing and generation entry points. Done means selecting filters updates editable query text and editing either dialect updates the corresponding filter selections without losing conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100