Problem/Motivation

ConfigSchemaChecker mentions that tests can use the $strictConfigSchema property.

It should also mention $configSchemaCheckerExclusions for specific exclusions.

Neither of these properties are in this class, but this is where developers will look first when their test breaks because of a config schema problem.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3624235

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

joachim created an issue. See original summary.

ayoub.elmansouri made their first commit to this issue’s fork.

ayoub.elmansouri opened merge request !17213

ayoub.elmansouri’s picture

ayoub.elmansouri commented
Status: Active » Needs review

I have updated the documentation in 'ConfigSchemaChecker' to also mention the '$configSchemaCheckerExclusions' property alongside '$strictConfigSchema'.

This will make it much easier for developers to find how to exclude specific configurations when their tests fail due to schema validation.

Opened a Merge Request for review. Moving status to Needs review.

ayoub.elmansouri’s picture

ayoub.elmansouri commented

@delereno Thanks for reviewing. The additions look good as confirmed. Marking threads as resolved.

jacobupal’s picture

jacobupal commented
Issue tags: +Rotterdam2026

(walking this one back...)

jacobupal’s picture

jacobupal commented
Issue tags: -Novice, -Rotterdam2026

Seems like the novice aspect of this task is complete, current state is "Needs review" which would be better for a more-than-novice person. Removing the Novice tag now to help move things forwards (here in Issue Triage at DrupalCon Rotterdam 2026).