[PP-1] Follow-up for #3364506: add deprecation once all simple config forms in core implement

Created on 1 September 2023, over 1 year ago
Updated 16 December 2023, 12 months ago

Problem/Motivation

Follow-up for #3364506-103: Add optional validation constraint support to ConfigFormBase β†’ and [-105].

Restore the

@trigger_error('Implementing form-coupled validation logic is deprecated in drupal:10.2.0 and will trigger a PHP error from drupal:11.0.0. Implement ::copyFormValuesToConfig() instead, which will become an abstract method on ConfigFormBase. See https://www.drupal.org/node/3373502', E_USER_DEPRECATED);

Steps to reproduce

N/A

Proposed resolution

Add the deprecation once all ConfigFormBase subclasses in core have adopted config validation, by overriding \Drupal\Core\Form\ConfigFormBase::copyFormValuesToConfig().

Remaining tasks

  1. βœ…
  2. βœ…
  3. Wait for πŸ“Œ [PP-1] Update all remaining ConfigFormBase subclasses in Drupal core to use config validation Active
  4. … then do this. After #3364506 lands, start running tests with this, and the failures basically represent the TODO list for #3384790!

User interface changes

None.

API changes

ConfigFormBase subclasses will trigger deprecations.

Data model changes

None.

Release notes snippet

None.

πŸ“Œ Task
Status

Postponed

Version

11.0 πŸ”₯

Component
ConfigurationΒ  β†’

Last updated 7 days ago

Created by

πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

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

Comments & Activities

Production build 0.71.5 2024