AddonView
Corex\Config\Addons\AddonView · class · Config layer
One add-on’s render model: the add-on plus its computed state (installed, active, flag on) and, when a toggle would break a dependency, the reason it is blocked (null when the add-on is freely togglable). A pure value object the screen renders. Spec 060 / M6: it also resolves to one truthful {@see AddonStatus} so the Add-ons screen shows a single honest state and offers enable/disable only for installed add-ons. The dependencyMissing/wooMissing/proRequired inputs are additive (default false) so existing constructions keep working.
Public API
Section titled “Public API”__construct(Addon $addon, bool $installed, bool $active, bool $flagOn, ?string $blockedReason, bool $dependencyMissing, bool $wooMissing, bool $proRequired)
Section titled “__construct(Addon $addon, bool $installed, bool $active, bool $flagOn, ?string $blockedReason, bool $dependencyMissing, bool $wooMissing, bool $proRequired)”isBlocked(): bool
Section titled “isBlocked(): bool”status(): AddonStatus
Section titled “status(): AddonStatus”The single truthful display state, in the canonical order: pro_required → not_installed → inactive → dependency_missing → feature_off → woocommerce_missing → active.