`ComponentTreeMeetRequirements` constraint validator must be updated now that Blocks-as-Components are supported

Created on 6 November 2024, about 1 month ago

Overview

πŸ“Œ Introduce an XB `PageTemplate` config entity Active added the ComponentTreeMeetRequirements validation constraint. It was designed to also support imposing the absence/presence of Blocks-as-Components, prior to πŸ“Œ Add support for Blocks as Components Active landing.

And #3475584 has since landed, but due to MR size it was decided to land it an in incomplete state.

This is critical for data integrity, and should be rectified ASAP. It will also help πŸ“Œ Introduce a `Pattern` config entity Active .

Proposed resolution

  1. Uncomment
                // @todo Remove this in Blocks-as-XB-Components: https://www.drupal.org/project/experience_builder/issues/3475584
                if (str_starts_with($missing_value, 'block.') || str_starts_with($missing_value, 'Drupal\\')) {
                  continue;
                }
    

    in \Drupal\experience_builder\Plugin\Validation\Constraint\ComponentTreeMeetsRequirementsConstraintValidator::validate().

  2. Make tests pass
  3. Expand test coverage β€” the @todos pointing to issue 3475584 describe what should be tested.

User interface changes

None.

πŸ“Œ Task
Status

Active

Version

0.0

Component

Config management

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