New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃殌 Feature: Search autocomplete #16451
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale, waiting for comments |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale, waiting for comments |
It sounds great to me! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale, gathering interest |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Thanks for opening the issue @drodil 馃檶馃徎 ! |
Hello @drodil thanks for opening this issue. Just for my own understanding. This feature request is to add auto complete support on the search engines side? The reason why I ask is because we have this AutoComplete component available but if I understand it correctly this is so that this auto complete component can be used with suggested terms? |
So idea is to utilize the AutoComplete component for search and provide the suggested terms from the search engine as part of the SearchAPI response. Elastic/OpenSearch supports this out-of-the-box but for other search backends it should probably render nothing or figure a way to do this. |
This makes sense to me. One thing that I'm not 100% sure about is if this has to be returned on the same response from the query endpoint, or if we want to introduce another endpoint responsible for only getting search suggestors. Have you been thinking about that anything when writing up the feature request? Some (but not limited to) work that I see needs to happen as part of this is:
Is this aligned with your thinking? Have I missed anything thats on top of your mind? We might want to discuss 2 and 3 before starting with 1, so that we are aligned on the approach and then we could split 1 into different engine specific issues to separate the work as long as the approach is settled on. From our side, this is not something that is on our near term roadmap, but if its something you want to come up with a proposal for I'm happy to support with feedback. |
Sounds good. Maybe it requires a new endpoint for suggestions, I haven't really thought it through. Splitting this into multiple issues makes a lot of sense as they can be worked on independently. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still not stale 馃槃 |
馃敄 Feature description
The search could suggest searching words using autocomplete. For example, ElasticSearch supports autocomplete to be returned in the response: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-suggesters.html
馃帳 Context
For better user experience, the search could propose the search words for the user
鉁岋笍 Possible Implementation
Use MUI autocomplete for search input
馃憖 Have you spent some time to check if this feature request has been raised before?
馃彚 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: