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
{{ message }}
This repository has been archived by the owner on Dec 5, 2020. It is now read-only.
Let's drop autocomplete and just use "search-as-you-type", for 2 reasons:
it takes a lot of time to implement the completion suggestion in elasticsearch. See here
it is very difficult and bug prompt from the front-end's pov. How do you show both autocomplete and search results in a cool manner, without having the user add all sorts of css? There is the problem that the searc results component has to be a child of the input component etc.
We solve this issue by simply having search-as-you-type functionality instead of autocomplete and no actual search results. In the end it will look like a simple widget that the user adds on a page and while he types, results appear right beneath the search field.
In this ticket: drop all the uncalled code related to autocomplete, implemented so far, and remove todos for the now-obsolete puzzles: #157#158#159#160
The text was updated successfully, but these errors were encountered:
Let's drop autocomplete and just use "search-as-you-type", for 2 reasons:
We solve this issue by simply having search-as-you-type functionality instead of autocomplete and no actual search results. In the end it will look like a simple widget that the user adds on a page and while he types, results appear right beneath the search field.
In this ticket: drop all the uncalled code related to autocomplete, implemented so far, and remove todos for the now-obsolete puzzles: #157 #158 #159 #160
The text was updated successfully, but these errors were encountered: