feat: settings slot anchors for module-contributed pages - #180
Draft
HexaField wants to merge 3 commits into
Draft
Conversation
Lets deployments register their own modules via the bundledModules map before PlatformProvider runs initializeIntegrations. The map was already importable from its deep path; this adds it to the shared barrel so external consumers (platform frontend, custom deployments) can import from @we/app-shell/shared instead of reaching into internals. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- slotRegistry: resolveAnchors now walks routes (resolveRoutes); added resolveTemplate() for shell view templates that bypass nodes() - TemplateLayout: ShellOverlayInner calls resolveTemplate before render so $slot markers in settings/profile templates get resolved - Settings.schema: two new slot anchors — settings-nav (nav column) and settings-pages (route /ext/:page) — let modules inject nav items and page content without platform-specific code in WE Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Extension point for module-contributed account content (email, tier, billing link) alongside the WE-native DID display. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
HexaField
marked this pull request as draft
September 2, 2026 12:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
$slotresolution in template route/settings content, enabling modules to contribute settings nav items and pages through the slot registry.Changes
slotRegistry.ts—resolveTemplate()+resolveRoutes(): walks a template schema'sroutesarray (alongsidechildren/props/slots) so$slotmarkers in route-level content resolve before the renderer sees them.TemplateLayout.tsx—ShellOverlayInnerpasses shell-view schemas throughslotRegistry.resolveTemplate()before rendering.Settings.schema.ts— Three new slot anchors:settings-nav: after the Developer nav item — modules contribute nav entries heresettings-pages:/ext/:pageroute — modules render their own settings pages (gated onrouteStore.segments[1])account-content: inside the Account section — modules contribute account-level chrome (billing, usage, etc.)shared/index.ts— exportsbundledModulesfrom the shared barrel so host apps (platform) can register modules at boot.Stacked on
#177 (
feat/billing-ui) — which already has theglobalflag onSlotContribution. The duplicate commit from this branch was dropped during rebase.Context
The platform module defines billing/usage/account settings pages contributed via slots, but the slot anchors in Settings didn't exist yet. This unblocks those contributions.