Improve design of "Places" filter
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Looks good! The only thing that I would add is a search box on top of the places filter too. These can be a lot (see our company instance) and it might also get confusing.
It would be also great to set up search aliases, for example if someone searches "Chat", they're also presented with the "talk" and "conversation" filters.
Originally posted by @marcoambrosini in https://github.com/nextcloud/server/pull/43189#pullrequestreview-1869495174
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 reviewing pull request 43189 and the current Places filter entry point; the issue names no files or tests. Define the search behavior and alias handling, then verify that the filter supports searching places and returns the requested related terms.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100