98d950ba44
Introduces kernel/services.js (window.LP.services): an additive, typed,
LAZY view onto the existing cross-cutting singletons — tasks{bus,refresh,
route}, live, auth, data, notify, theme, modal, router. It constructs
nothing (pure getters onto the live globals), so there's no double-init and
the globals stay authoritative. MountContext now injects it as ctx.services.
Slot names/globals were verified against the real code (workflow map): the
design doc's §4 list was wrong in several places — no window.taskManager
(client slot dropped), tasks.route lives on tasksManager.router, auth has no
status(), DataLoader isn't a window prop (lexical fallback), modal/router are
split surfaces (grouped/bound objects).
Migrated the 4 cross-cutting refs in the feature modules onto ctx.services
(admin: router.adminCategoryFromPath + tasks.refresh; backup: tasks.refresh;
app-detail: router.appPath). Page-owned controllers stay feature-globals.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: librelad <librelad@digitalangels.vip>
42 lines
1.8 KiB
JavaScript
42 lines
1.8 KiB
JavaScript
// features/backup/index.js — Backup Center as a self-contained feature module.
|
|
//
|
|
// FIRST page migrated to the feature-module contract (docs/frontend-modularization.md).
|
|
// The kernel drives mount()/unmount() for the /backup route instead of
|
|
// spa.js's handleBackup(). The heavy controller (backup-page.js, ~129KB) is
|
|
// still lazy-loaded on first mount, so cold-load cost is unchanged.
|
|
//
|
|
// Snap-out demo: deleting this folder removes the backup route's module
|
|
// registration; the manifest entry then falls back to the legacy handler
|
|
// (and, once handleBackup is retired, to the kernel's not-found route). The
|
|
// full decomposition of backup-page.js into per-tab modules is Phase 5.
|
|
LP.features.register({
|
|
id: 'backup',
|
|
routes: ['/backup', '/backup*'],
|
|
// Controllers the feature needs; lazy-loaded on first mount (idempotent).
|
|
scripts: [
|
|
'/js/components/backup/backup-page.js',
|
|
'/js/components/backup/backup-app-card.js',
|
|
],
|
|
|
|
async mount(ctx) {
|
|
await ctx.loadScripts(this.scripts);
|
|
const html = await ctx.loadFragment('/html/backup-content.html');
|
|
ctx.setContent(html, 'Backups');
|
|
if (typeof BackupPage === 'undefined') {
|
|
throw new Error('BackupPage controller failed to load');
|
|
}
|
|
window.backupPage = new BackupPage();
|
|
await window.backupPage.init();
|
|
},
|
|
|
|
async unmount(ctx) {
|
|
// Best-effort teardown. BackupPage self-guards stale work via
|
|
// (window.backupPage === this), so nulling the global neutralises any
|
|
// pending task-refresh repaint; we also drop its coordinator registration.
|
|
// A proper dispose() (removing the leaked document listeners) lands with
|
|
// the Phase 5 backup decomposition.
|
|
try { ctx.services.tasks.refresh && ctx.services.tasks.refresh.unregister('backups'); } catch (_) {}
|
|
window.backupPage = null;
|
|
},
|
|
});
|