CommandPalette needs a supported way to disable client filtering
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.1k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 57
Description
Summary
UCommandPalette always applies local filtering based on searchTerm, even when results are already pre-filtered by a remote search backend.
Why this matters
For server-driven search UIs, the component should be able to render the provided items as-is. Right now the only reliable workaround is a fragile combination of permissive fuse settings and/or group.ignoreFilter, plus a regression test to make sure upstream behavior does not change.
Requested behavior
A first-class prop to bypass client filtering entirely, for example:
ignoreFilteron the whole component, or- a documented remote-search mode
Current workaround
We are using v-model:searchTerm with remote Typesense results and forcing UCommandPalette to keep all returned items visible.
Thanks.
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 UCommandPalette implementation and trace how searchTerm applies local filtering, then review its existing component tests. Add a supported component-level way to bypass filtering for remotely filtered items and cover the behavior with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100