Based on #3570717: Make configuration schema fully validatable.

Problem/Motivation

As a result of the change of the minimum supported core version to 10.3 in parent issue #3590369: Support for Drupal 12, it should now be possible to implement full validation of all of modules' configuration schema, introduced with change record: Stricter validation for config schema types is available, since version 10.3.0.

See the reports from Config Inspector for the System Branding block on Olivero:

Fix third_party_settings.block_class.classes:

Fix validation of:

  • third_party_settings.block_class.classes string value with a validation rule.

Steps to reproduce

Proposed resolution

Fix the reported schema validation errors by adding validation constraints and the FullyValidatable property.

Examples of similar issues:

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
block_class-config_inspector-report2a.jpg63.09 KBdydave
block_class-config_inspector-report1a.jpg70.32 KBdydave

Issue fork block_class-3605794

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

dydave created an issue. See original summary.

dydave opened merge request !82

  • dydave committed 8cc9dd03 on 3.1.x 
    Issue #3605794 by dydave: Made configuration schema fully validatable.
dydave’s picture

dydave commented
Status: Active » Fixed

90% of the changes in this merge request were generated with AI:

Mostly: Added a Constraint Validator on CSS Classes used for configuration validation and at the block config form level (user facing validation).

The rest of the changes is all tests: Unit, Kernel, Functional.

The changes were merged above at #3, marking as Fixed , for now.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.