refactor(settings): split security into 4 focused tiles
Extracts user-lifecycle, audit and telemetry from the security subpage into their own tiles, and renames the slimmed-down security subpage to account-access for a clearer scope. Each subpage now has at most three detail cards instead of the eight previously crowded into security. Hub gains four tiles, sub-action redirects (expire-remember-tokens, run-user-lifecycle) move to their new sections, architecture tests track the new section list and i18n adds the new labels in de + en. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -59,7 +59,7 @@ class AuthzUiTemplateContractTest extends TestCase
|
||||
// Settings was split into a landing hub + per-section subpages.
|
||||
// The form-carrying subpages must use the server-side $canUpdateSettings
|
||||
// capability instead of the legacy can() helper.
|
||||
foreach (['general', 'security', 'email', 'api', 'sso', 'branding'] as $section) {
|
||||
foreach (['general', 'account-access', 'user-lifecycle', 'audit', 'telemetry', 'email', 'api', 'sso', 'branding'] as $section) {
|
||||
$templateContent = $this->readProjectFile("pages/admin/settings/{$section}(default).phtml");
|
||||
$this->assertStringNotContainsString("can('settings.update')", $templateContent, $section);
|
||||
$this->assertStringContainsString('$canUpdateSettings', $templateContent, $section);
|
||||
|
||||
Reference in New Issue
Block a user