Problem/Motivation
Remove the "dropdown_type" as it can be set via the css selectors.
Steps to reproduce
Proposed resolution
Remove the "dropdown_type" and let the user use the css selectors instead.
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork choices-3317975
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
grevil commentedDone, please Review!
Comment #4
anybodyTotally agree, because of the possible conflict of these options, which is bad UX.
Anyway, 2 tests fail here, please fix them first @Grevil.
I'm considering the possible conflict as bug.
Comment #5
grevil commentedForgot to remove "dropdown_type" inside the Tests and on settings Form submit, please review once again!
Comment #6
grevil commentedRebased.
Comment #7
anybodyAll passed :) Great!
Comment #9
grevil commentedComment #10
tobiasbIt is better to add a empty update choices_update_8001 again. because a choices_update_8001 will not run on sites which are already on schema version 8001.
And in a perfect drupal-world a update hook choices_update_8002 would remove dropdown_type again.
Comment #11
grevil commented@tobiasb, you are totally right! We decided against it, as the versions released pretty close to each other, and we thought not many people would update it right away. Unfortunately, 13 people use 2.0.4, which introduced the "dropdown_type" config. So we definitely need the update hook, for those few.
Thanks for the concern!
Comment #12
grevil commented@tobiasb, fixed in #3318640: Missing update hook for removing "dropdown_type" config