fix: #3627199 Use the keyed Choice constraint in the settings schema

Rajab Natshahrequested to merge
issue/uikit_admin-3627199:3627199-choice-schema into 4.0.x

Issue: https://www.drupal.org/project/uikit_admin/issues/3627199

  • Drupal 12 refuses Choice: followed by a bare list ("$options must be an associative array or NULL"). The five settings that used it now use Choice: { choices: [...] }, like sign_in_brand already does. Same validation on Drupal 11.
  • CI: opt in to the next-major and max-PHP jobs.
  • Meant for the pending 4.0.1.

AI-Generated: Yes

Checkpoints

  • File an issue about this project
  • Addition/Change/Update/Fix to this project
  • Testing to ensure no regression
  • Automated unit/functional testing coverage
  • Developer Documentation support on feature change/addition
  • User Guide Documentation support on feature change/addition
  • UX/UI designer responsibilities
  • Accessibility and Readability
  • Reviewed by a human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Update Release Notes
  • Release

Merge request reports