Closed (won't fix)
Project:
Configuration Split
Version:
2.0.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 Sep 2026 at 05:57 UTC
Updated:
22 Sep 2026 at 10:43 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #3
mortona2k commentedComment #4
bircherThanks for opening this feature request.
But we already added chosen and select2_all to composers suggest section.
I don't think adding 330 lines of code and mostly js is the best course of action when there are modules purpose made that make input lists more approachable.
Comment #6
mortona2k commentedI don't think the UX is as good with Chosen or Select2 All. For example, you can't filter and then click on a few items. You have to re-type the filter each time.
I can understand if you don't want this much custom ui code being added though.
Comment #7
bircherYea, maybe there is better way to do it than chosen or select2 all, there are other modules that address this kind of concern too.
I would be happy to add a better one to composer's suggest section or even feature it on the project page. But I don't think it should be the concern of config split. I know UI/UX is important and we do checkboxes already as an improvement over a multi select list. But I think further improvements are out of scope.
Other libraries can be added through form alters if you want to maintain it in a contrib module. If you do so I would adapt \Drupal\config_split\Form\ConfigSplitEntityForm::useSelectList so that your module is compatible with chosen or select2 all.