Skip to content

feat(facade): add optional view config resolver#73

Open
wolfy-j wants to merge 2 commits into
masterfrom
feat/view-config-resolver
Open

feat(facade): add optional view config resolver#73
wolfy-j wants to merge 2 commits into
masterfrom
feat/view-config-resolver

Conversation

@wolfy-j

@wolfy-j wolfy-j commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Adds the optional wippy.facade:resolver contract used by applications that want runtime facade config/theming overrides. Backward compatibility: unbound resolver paths degrade to the existing static ns.requirement defaults, so existing apps do not need to bind anything.\n\nPublished package source: wippy/facade@0.6.20.\n\nVerification:\n- make test in src/facade/test: 2/2 passed

wolfy-j added 2 commits July 3, 2026 11:42
Add an optional wippy.facade:resolver contract.definition that lets an
application override facade requirement values (css_variables, custom_css,
app_title, ...) at request time. When no implementation is bound the config
and CSS-vars handlers fall back to the static ns.requirement defaults, so
behavior is unchanged for existing deployments.

theming_helpers gains resolve_overrides() (structural :implementations()
gate, ambient-actor open, pcall-hardened to {} on any failure) and
requirement() (override string wins over the static default). Both handlers
resolve overrides once per request and route every requirement read through
the override-aware getter.
The endpoints degrade to static on any resolver failure, so unbound and errored
are indistinguishable and need no distinguishing; open() fails cleanly when
nothing is bound. Removes the implementations() round-trip and the unused logger.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant