Suggest improved flexible search capabilities
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Is your feature request related to a problem?
I'm always frustrated when search using keyword.
if you search for keywords other than search file name sequence flows, you cannot find the file.
EX. file name to search: 20201113 issue test image
You can find a file by creating a search keyword with search file name sequence flow.
-> search success keyword: "20201113", "issue test", "image", etc
However, if you search for keywords other than search file name sequence flows, you cannot find the file.
-> search fail keyword: "20201113 test", "issue image", "te ", etc
Describe the solution you'd like
I think search is one of the most important features in this app.
It would be better to use your search more flexibly.
I hope I can find the file even if I search for keywords other than search file name order flow.
Instead of spaces, we suggest using the '%' symbol to make it searchable.
When a user searches in an APP, it is suggested that the search string should be changed to the '%' symbol before sending it to the server.
Result after code modification:
If you are positive about this solution, I would like to PR it, so please give me your opinion.
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
Reproduce the successful and failing filename searches described in the issue, including the proposed '%' behavior, before locating the server-side search entry point. Confirm the intended matching semantics with maintainers, then verify that the documented keyword-order examples return the expected file without breaking existing searches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100