[PP-2] Introduce ConfigEntityForm to standardize use of validation constraints for config entities

Created on 3 September 2021, about 3 years ago
Updated 21 February 2024, 9 months ago

Problem/Motivation

The CKEditor 5 module in Drupal core will be the first in Drupal core (or anywhere?) to use validation constraints defined in config schema for 100% of its validation needs. No form-based validation is used: the form-based validation just uses validation constraints.

Just like we already do for content entities.

It'd be great if we would standardize this, to avoid reinventing the wheel.

Proposed resolution

Extract from ckeditor5 module.

Remaining tasks

TBD

User interface changes

None.

API changes

New: \Drupal\Core\Entity\ConfigEntityForm (or \Drupal\Core\Config\Entity\ConfigEntityForm?).

Data model changes

None.

Release notes snippet

TBD

✨ Feature request
Status

Active

Version

11.0 πŸ”₯

Component
Configuration entityΒ  β†’

Last updated 34 minutes ago

Created by

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

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024