You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For our project one of the tags used is only two characters long.
The problem is that the search bar only starts searching for results when it has at least three characters in the search field.
Meaning when I want to search for, let's say "sf" I am not able to do this because the search bar simply doesn't start a search below 3 characters, even when you press enter.
I am aware that searching for results that are shorter than 3 characters might incur a performance penalty, this could be avoided by not live searching below 3 characters but still starting 2 (or even 1) character searches when the user presses enter.
Similarly there could also be a wait period before searches below 3 characters are started. For example the user searches for "sf" and the live-search only starts when the user hasn't typed for 2 seconds, this would still allow a very similar live search but avoid some of the early performance hits.
The text was updated successfully, but these errors were encountered:
Keep the automatic search limit at 3 characters.
But implement an @onEnter function so that a search can be triggered manually. This will still only be triggered if the input value is empty
For our project one of the tags used is only two characters long.
The problem is that the search bar only starts searching for results when it has at least three characters in the search field.
Meaning when I want to search for, let's say "sf" I am not able to do this because the search bar simply doesn't start a search below 3 characters, even when you press enter.
I am aware that searching for results that are shorter than 3 characters might incur a performance penalty, this could be avoided by not live searching below 3 characters but still starting 2 (or even 1) character searches when the user presses enter.
Similarly there could also be a wait period before searches below 3 characters are started. For example the user searches for "sf" and the live-search only starts when the user hasn't typed for 2 seconds, this would still allow a very similar live search but avoid some of the early performance hits.
The text was updated successfully, but these errors were encountered: