- Issue created by @arousseau
- Merge request !12252Issue 3526779: Customizable views area handlers ids. โ (Open) created by arousseau
- ๐ซ๐ทFrance arousseau
I added a rough proof of concept which works ok.
I had to add the
Method Drupal\views\Plugin\views\area\AreaPluginBase::submitOptionsForm() has no return type specified.
phpstan error to the list of ignored errors incore/.phpstan-baseline.php
since\Drupal\views\Plugin\views\area\Entity
already implements it and would break. - ๐ณ๐ฑNetherlands Lendude Amsterdam
I would be against doing this in Drupal core, it adds more options to the Views UI which is already too full of options, and this feel very much like an edge case. If you need this in a project you can just add a custom area plugin that does this and use that, right? Just my feeling.
Back to needs work for the tests.
- ๐ซ๐ทFrance prudloff Lille
My rationale for adding this to core would be that almost every other machine name in Drupal can be customized from the UI.
- ๐ฎ๐ณIndia abhijith s
abhijith s โ made their first commit to this issueโs fork.
- ๐บ๐ธUnited States mortona2k Seattle
Having random machine names in views is quite annoying for developers. I think this should be fixed in core.
I think it should be included just under the setting for administrative labels. That is in a collapsed element, so to me this increases functionality without adding clutter.
I want this for fields as well, where you can have duplicate fields that just have _1 _2 at the end, with no way to differentiate semantically.
- ๐ซ๐ทFrance arousseau
I moved the new input to a details element, under admin label as suggested by @mortona2k