Check greater than or equal for autocomplete scoped search options
What does this MR do and why?
In the backend, we consider search terms with count >= 2 as non-abusive but in the frontend for autocomplete, this was set to count > 2 which is causing confusion.
This MR changes the frontend to check for count >= 2 in order to show the scoped search options when the search is not abusive for consistency.
| level | length | before | after |
|---|---|---|---|
| global | 2 |
|
|
| 3 |
|
|
|
| group | 2 |
|
|
| 3 |
|
|
|
| project | 2 |
|
|
| 3 |
|
|
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
- Run autocomplete for 2 and 3 characters and see that with this change, we show
Search for <> in...for search terms of length>= 2instead of> 2