Explicitly test that all components are compatible with XB under the right circumstances

Created on 25 July 2025, 21 days ago

Problem/Motivation

We now have an explicit test that at least some Mercury components are compatible with XB.

We should expand that test to ensure that all components are, under the right circumstances (that is, if they have fields available that they can match to), compatible with XB -- that is, they are valid and exposed as Component config entities.

Without this, we can never be sure that Mercury actually works in XB properly.

📌 Task

Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.

Merge Requests

!13Explicitly test that all components are compatible with XB under the right circumstances
Merged
🇺🇸United States phenaproxima
updated 3 days ago

Comments & Activities

Issue created by @phenaproxima
Merge request !13Add failing test → (Merged) created by phenaproxima
First commit to issue fork.
Comment 3 days ago →
🇺🇸United States phenaproxima Massachusetts
Pipeline finished with Skipped
3 days ago
#571449

Comment 3 days ago →

System Message

phenaproxima → committed 581e5038 on 1.x

Issue #3538105 by phenaproxima, galactus86: Explicitly test that all...

Comment 3 days ago →
🇺🇸United States phenaproxima Massachusetts
Awesome collaboration in here, and now we won't be able to add a broken component to Mercury without PHPUnit yelling at us. :)

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024

Explicitly test that all components are compatible with XB under the right circumstances

Problem/Motivation

Merge Requests

!13Explicitly test that all components are compatible with XB under the right circumstancesMerged

Comments & Activities

!13Explicitly test that all components are compatible with XB under the right circumstances
Merged