fs
c364e2b46d
Add a module kernel (ModuleManifest, ModuleRegistry) that allows modules to contribute routes, UI slots, search providers, layout context, session lifecycle, and permissions. Modules are activated via config/modules.php or APP_ENABLED_MODULES env variable. Conflicts (duplicate routes, permissions, slot keys) cause a fail-fast with a clear error message. Extract the address book from hardcoded Core integration points into the first module (modules/addressbook/). The module provides: - Aside icon-bar tab + People panel via UI slot system - Global search resource via AddressBookSearchProvider - Layout context data via AddressBookLayoutProvider - Session lifecycle via AddressBookSessionProvider Core cleanup removes address-book hardcodings from SearchSqlResourceProvider, SearchUiMetaProvider, SearchItemMapperProvider, appBuildLayoutNavContext(), and the aside templates. Permissions (ADDRESS_BOOK_VIEW) and business logic (AddressBookService) remain in Core as they gate general user visibility. Includes 38 new tests (894 total), PHPStan level 5 clean, and architecture tests verifying zero hardcoded address-book references in search/templates. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
27 lines
728 B
PHP
27 lines
728 B
PHP
<?php
|
|
|
|
namespace MintyPHP\App\Module\Contracts;
|
|
|
|
use MintyPHP\App\AppContainer;
|
|
|
|
/**
|
|
* Populates module-specific session data after login and cleans up on logout.
|
|
*
|
|
* Called from the login flow after successful authentication. When a module is
|
|
* deactivated, its provider is not called — session keys are simply not set.
|
|
*/
|
|
interface SessionProvider
|
|
{
|
|
/**
|
|
* Populate session keys with module-specific data after successful login.
|
|
*
|
|
* @param array<string, mixed> $user The authenticated user record
|
|
*/
|
|
public function populate(array $user, AppContainer $container): void;
|
|
|
|
/**
|
|
* Remove session keys owned by this module (called on logout).
|
|
*/
|
|
public function clear(): void;
|
|
}
|