refactor: Divi-Boot-Schritte in DiviIntegration::boot() (Bootable) – Upgrader-Hook, Prüf-Route, CLI und Reiter „Divi“ über lit_mcp_admin_tabs; IntegrationRegistry::boot() bootet jede Integration genau einmal; Prüfseiten-Aufräumen im load-Hook statt beim Rendern
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
06148fb8c1
commit
6c59934caa
@@ -0,0 +1,18 @@
|
||||
<?php
|
||||
|
||||
declare(strict_types=1);
|
||||
|
||||
namespace LIT\MCP\Integrations;
|
||||
|
||||
defined('ABSPATH') || exit;
|
||||
|
||||
/**
|
||||
* An integration with boot steps of its own (hooks, REST routes, WP-CLI commands, admin tabs), so the composition
|
||||
* root does not need to know them. IntegrationRegistry::boot() calls boot() whether or not the integration is
|
||||
* available: Plugin boots on plugins_loaded, before the theme – isAvailable() cannot be asked yet.
|
||||
*/
|
||||
interface Bootable
|
||||
{
|
||||
/** Registers the integration's own hooks, routes, CLI commands and admin tabs. Called once by Plugin. */
|
||||
public function boot(): void;
|
||||
}
|
||||
Reference in New Issue
Block a user