- Issue created by @yannickoo
- @yannickoo opened merge request.
- Status changed to Needs review
over 1 year ago 5:01pm 22 June 2023 - 🇩🇪Germany yannickoo Berlin
I have created a MR to change the input type, please have a look 😇
- Issue was unassigned.
- 🇩🇪Germany yannickoo Berlin
I just realized that
search_api_autocomplete
provides it's own form element that we could use here and that would allow us to support auto-submit.In order to get a search insteaf of a text field you would need to apply the patch from ✨ Use search form element instead of text Needs review .
- Status changed to Needs work
over 1 year ago 6:53am 23 June 2023 - 🇩🇪Germany a.dmitriiev
I think there is no need to have "Auto Submit" configuration setting on Endpoint entity, because this setting exists on Search API Autocomplete entity. If anyway the form element from that module is used, auto-submit setting from it could be used as well. Endpoint entity has method
getAutocomplete
that returns the autocomplete object in response, if it exists. It can be used to get the auto-submit setting from Search API Autocomplete. - Status changed to Needs review
over 1 year ago 10:24am 23 June 2023 - 🇩🇪Germany a.dmitriiev
The looks good and works, maybe then the search api decoupled autocomplete endpoint is also not needed at all, because it is doing the same as search_api_autocomplete anyway, as here the search api autocomplete endpoint is used.
Maybe then the access control for standard search_api_autocomplete should be extended if it was created from endpoint.
-
a.dmitriiev →
committed 09607d80 on 1.x authored by
yannickoo →
Issue #3368760: Use search and search_api_autocomplete form elements for...
-
a.dmitriiev →
committed 09607d80 on 1.x authored by
yannickoo →
- Status changed to Fixed
over 1 year ago 12:55pm 29 June 2023 - 🇩🇪Germany a.dmitriiev
Related issue was created for removing custom search_api_decoupled_autocomplete route as follow up to this. Merging this MR.
Automatically closed - issue fixed for 2 weeks with no activity.