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 the time being, the searching functionality is implemented in the front end instead of the backend. We can change that in the future if we deem that filtering in the frontend is too intensive of a task to be performed on render().
Recommendations are possible if we send the user input before submitting it to the server, which will then return possible partial matches for the query.
As of right now, we only look for case insensitive matches in the object's name or description.
I'm not sure what you mean by autofill, this would be similar to real-time recommendations with what I have in mind.
The searchbar component that's present in the navbar (both desktop and mobile view) simply redirects to the actions page. Between actions and teams, we should probably keep the same behavior so that the user "knows" what to anticipate.
We need to specify how our searchbar is going to work.
Questions
The text was updated successfully, but these errors were encountered: