Use #config_target and validation constraints for settings

Created on 28 June 2024, 8 months ago
Updated 23 July 2024, 7 months ago

Problem/Motivation

Added in Drupal 10.2
Change record: #config_target in ConfigFormBase: using validation constraints for editing simple config

Proposed resolution

  • Account Settings form uses ConfigFormBase, allowing form elements to use #config_target.
  • Move all values getting and saving to #config_target style.
  • Adding an interlocking validation constraint for genpass_mode which is tied to verify_mail.
  • Update tests to confirm constraints are working.
  • Add test to check on

Remaining tasks

  • ✅ File an issue
  • ✅ Addition/Change/Update/Fix
  • ✅ Testing to ensure no regression
  • ✅ Automated unit testing coverage
  • ✅ Code review by maintainers
  • ➖ Code review by someone else? Nope.
  • ✅ Release notes snippet
  • ✅ Release: 2.1.0

User interface changes

  • Error messages made more specific.

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

📌 Task
Status

Fixed

Version

2.1

Component

Code

Created by

🇦🇺Australia elc

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024