filippomc
commented
2 years ago copied from #360 by @sanjayankur31 current design idea is to merge the functions of the filter component into the text search component:
- only use one search box for all searches
- when the user types in something, show matching tags in drop down list and allow user to select these tags
- if user does not select tag, use text search
- if user selects tag, use tag search
- include modelling/experimental/general in drop down list also (either as tags, or in a different section?)
If we type the tag fast, the interface does not respond as expected. This is mostly certainly due to the instant queries on change. Look at the state update of the field bound to the input (don't need to have a binding there). A strategy to improve this can be to implement some debounce strategy.
Make the selected tags visible in the search bar, remove the delete icon from the single elements (confuses the user as it looks like it deletes the tags from the current repository)