Capture all reasons why particular SDC is incompatible

Created on 10 September 2024, 10 days ago
Updated 11 September 2024, 8 days ago

Overview

Follow-up for 📌 Surface the REASON for an SDC not being made available in XB (i.e. not meeting criteria) Fixed .

Currently we are surfacing reasons why Component entities are not being auto-generated for SDC's that do not meet requirement, but we only store first encountered reason per SDC.
We should check for and store all reasons that make SDC incompatible and store them.

Proposed resolution

Store reasons as value object in State API or consider alternative storage methods and select appropriate solution.

User interface changes

Current UI in /admin/structure/component/status shows a table with a single row per SDC with single reason. This needs to support multiple reasons per SDC.

📌 Task
Status

Active

Component

Config management

Created by

🇬🇧United Kingdom f.mazeikis@gmail.com Brighton

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @f.mazeikis@gmail.com
  • 🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
  • 🇮🇳India Akhil Babu Chengannur

    I ran across this scenario while exploring the component listing in admin/structure/component

    • By default, the experimental component (components/sdc_statuses/experimental) is listed in the component listing and is active.
    • Change the status of the component from experimental to obsolete in experimental.component.yml
    • The component gets disabled in the component listing (Expected)
    • The component gets added in the 'Disabled components' section (admin/structure/component/status) with reason "Component has "obsolete" status" (Expected)
    • Changed the status back to experimental in experimental.component.yml
    • The component will still be disabled in the component listing
    • The component will still be present in the disabled components section with the same reason "Component has "obsolete" status" . Since the component is disabled, it should be listed under the 'Disabled components' section. But the reason is incorrect. I am not sure what reason to use in this case though. Already, there is a 'Manually disabled' reason. But that's also not quiet right for this scenario.
Production build 0.71.5 2024