Group-by control is not typeable, values cannot be removed, and some keys require editing the URL by hand
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
The group-by control does not behave like the rest of the search experience:
- You cannot type to filter the list of available keys. The list must be scrolled.
- Selected values cannot be removed from the control once added.
- Some keys are not offered in the picker at all. Grouping by
osrequires
constructing the query string in the URL manually.
Individually these are small. Together they make the control unusable for anyone
with a non-trivial attribute set, which is exactly the population that needs
grouping most. Teams end up keeping a folder of hand-written URLs.
Scrolling to find a key does not scale past a few dozen attributes. Hand-editing
URLs is not discoverable, is not teachable across a large engineering org, and
breaks whenever the query grammar changes. The inconsistency with the main search
bar, which does support typeahead, makes the control feel broken rather than
limited.
Solution Brainstorm
- Typeahead filtering over available keys, matching the search bar's behaviour.
- Removable chips for selected group-by values.
- Every key that is valid in the URL should be offered in the picker,
osincluded.
Product Area
Explore
Requested by Saad Khan.
--
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 by locating the Explore group-by control and comparing it with the main search bar's typeahead behavior. Done means users can filter available keys, remove selected values, and choose every key valid in the URL, including os.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100