SupportSettings
Corex\Guides\Support\SupportSettings · class · Add-ons layer
Where a support message goes, and whether the form is offered at all (spec 087, FR-002 / FR-003). Two layers, and the order matters. config/guides.php holds the shipped default, which is the one line a developer edits. The corex_guides_support_email option, written by the Settings screen, layers over it — so a site owner changes the address without a deploy, and a site that has never opened Settings still has a working address. The layering is not implemented here: the Config engine already does it (.env → options → defaults, first source wins). This class only supplies the defaults the engine has no other way to learn, because {@see \Corex\Foundation\CoreServiceProvider::defaults()} globs corex-core/config/ and nothing else — an add-on’s config file is not auto-discovered.
Public API
Section titled “Public API”__construct(ConfigInterface $config)
Section titled “__construct(ConfigInterface $config)”recipient(): string
Section titled “recipient(): string”The address a support message is sent to. Empty when the site has deliberately blanked it.
enabled(): bool
Section titled “enabled(): bool”Whether the site wants the support form offered at all.
configured(): bool
Section titled “configured(): bool”Whether a message sent right now would have somewhere to go.