Closed (fixed)
Project:
Experience Builder
Version:
1.x-dev
Component:
Config management
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
27 May 2025 at 08:05 UTC
Updated:
14 Aug 2025 at 12:29 UTC
Jump to comment: Most recent
Comments
Comment #4
libbna commentedI have updated the ComponentValidationTest.php and .schema file as per the suggestions. For next steps I have to confirm that we will be creating "ValidStructuredDataPropExpression.php" and "ValidStructuredDataPropExpressionValidator.php" inside the
/src/Plugin/Validation/Constraint, right?Comment #5
thoward216 commentedComment #6
wim leers#3526707: Tighten validation of `experience_builder.generated_field_explicit_input_ux: prop_field_definitions.[%key].default_value` is in! 🎉
Comment #7
wim leersOops, during the rebase on top of 1.x I apparently somehow erased the authorship by @libbna! 😅 Crediting them already to ensure they are recognized for what they contributed :)
Comment #8
wim leers@thoward216 is out today, I'd like to land something nice & simple for once before I go on PTO 😇
Comment #9
wim leersFYI, picking this up because it became more important since #3530521: Decouple image shape matching from the `image` MediaType: support matching multiple bundles of a single MediaSources (`image`), and now soon also #3530533: Support image shape matching against multiple bundles of multiple MediaSources (`image` + `oembed` + `acquia_dam_asset` + …) — we need to be able to be as confident as possible that
PropExpressions stored in XB's config are valid.Comment #10
wim leersComment #12
wim leers