Remove legacy support to take advantage of config validation features

Created on 20 October 2023, 8 months ago
Updated 12 April 2024, 2 months ago

Problem/Motivation

The ConfigFormBase config validation extensions are only available as of Drupal 10.2.0.

Considering:

  • Drupal 9 being EOL feature-wise since 2023-06-21 and completely as of 2023-12-23
  • Drupal 10.1 being EOL feature-wise on 2023-12-23 (and completely on 2024-06-19)
  • Drupal 10.2 dev being available since DrupalCon Lille
  • Image Delta Formatter having an existing 8.x-1.2 stable release already
  • Image Delta Formatter dev version being only used by a handful of people

The best time to upgrade to these features and remove D9 and D10.1 support in the next stable release appears to be Xmas 2023.

The best time for the same upgrade in dev is ASAP.

Steps to reproduce

n.a.

Proposed resolution

Remaining tasks

TBD.

User interface changes

None.

API changes

None.

Data model changes

Config format changes.

πŸ“Œ Task
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡«πŸ‡·France fgm Paris, France

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

Comments & Activities

  • Issue created by @fgm
  • πŸ‡·πŸ‡ΈSerbia bojanz

    Sounds good to me.

  • πŸ‡«πŸ‡·France fgm Paris, France

    @bojanz: the filter settings config validation and D11 support are in, but I do not see how to write validation tests. I checked the config works by manually breaking the schema, applying the formatter in a view mode, inspecting it in config_inspector to see that it crashes notifying of the error ; then reverting to the current schema, redoing the same, and seeing that config_inspector reports all-ok. But no idea how to reasonably do that in a test. Any suggestion ?

Production build 0.69.0 2024