- Issue created by @ctrladel
- 🇪🇸Spain JSnow11
Hello!
we actually implemented the whole client library architecture for web-components support and we do use web-components internally, we contributed those simple elements because we thought not everyone would like to use them since web-components are encapsulated and hard to re-style / adapt
we recently added the "custom-element" inputs for the ui config (we used to have it only as an internal extension for the module), so the backend and config currently already support web components, and you can implement your own library easily
we started to prepare a wc library for contribution but since we decided to go for the simple ts/js/css elements it was left behind
maybe it's time to work on a simple web-component library too, our starting point would be this: https://git.1xinternet.de/1x-contrib-modules/xsearch-elements
it would be a parallel repository, next to this one: https://www.drupal.org/project/search_api_decoupled_client_ui → and in the future we could include it as a selectable option directly in the module
would be nice to have contributors / maintainers for that kind of library, let us know if you are interested!
- 🇺🇸United States ctrladel North Carolina, USA
I had some free time and inspiration since opening the issue and put together https://www.drupal.org/project/search_web_components → . I would say it's a different take to the existing client/ui so not sure how much of a drop in alternative it really is.
Still debating if the module will support the ui submodule or not. With everything web component based it seems like Drupal's existing layout tools may be sufficient.
- 🇩🇪Germany a.dmitriiev
Now it is possible in UI module add custom element tag as a setting, so let's discuss how it will be possible to partly combine the effort and make it possible to use web components from https://www.drupal.org/project/search_web_components → in search_api_decoupled_ui as well, so users can benefit from both modules.