XB Component config entity's `status` may only be `true` if it meets all of XB's requirements

This isn't quite what I meant. I meant something much simpler!

Starting to use validation constraints for SDC *.component.yml files would be going too far — that's what the SDC JSON schema is already doing, these are simply the additional requirements that XB has.

Maybe we could convert that all to validation constraints, but that seems overkill 😅

akhil babu → made their first commit to this issue’s fork.

Added a validation constarint to check if 'status' is TRUE.
Now updating the tests

@kristen pol in #4: that iff wasn't a typo: https://en.wikipedia.org/wiki/If_and_only_if

@akhil babu Thanks for getting started on this! But you only added a constraint that simply refuses to accept false as a value. That's not what's described in the issue summary:

# @todo Write validation constraint that verifies that IF this value is `true`, that \Drupal\experience_builder\Plugin\ComponentPluginManager::componentMeetsRequirements() also is met.

You're well on your way to that though — you need to update the validator you wrote to call that method 😊

Thanks for the guidance @wim leers. I have updated the validator code. Drupal\Tests\experience_builder\Kernel\ComponentTest::testObsoleteStatusHandling still fails. I am not sure if this test should be removed or updated. Moving to needs review for feedback.

📌 Prepare for multiple component types: ComponentTreeStructure should contain Component config entity IDs, not SDC IDs Fixed landed, which requires a small change here.

I'll first tackle the tricky config validation bits.

The test that @akhil babu mentioned in #11 (ComponentTest::testObsoleteStatusHandling()) is now the last failing one, and it is pretty damn tricky indeed 😬

Will continue that one tomorrow.

Didn't get to it a week ago; won't have time for it in the coming days; higher priorities to deal with.