Skip to content

docs(demo): flag EPDS_CLIENT_THEME as required for client-branding e2e #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aspiers merged 1 commit into from
May 1, 2026
Merged

docs(demo): flag EPDS_CLIENT_THEME as required for client-branding e2e #145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions packages/demo/.env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,12 @@ AUTH_ENDPOINT=https://auth.pds.example/oauth/authorize
# light look, and client-metadata.json ships no branding CSS — the
# auth-service then renders its default Certified styling. Available
# presets: ocean, amber.
#
# Required (uncomment) to run the @client-branding e2e feature locally:
# the suite asserts that auth-service inlines the demo's branding CSS,
# which only happens when client-metadata.json advertises one. Without
# it, every scenario in features/client-branding.feature fails with
Comment thread
aspiers marked this conversation as resolved.
# "expect(html).toContain('body { background: #1a1208')" mismatches.
Comment thread
coderabbitai[bot] marked this conversation as resolved.
# EPDS_CLIENT_THEME=amber

# Session signing secret (generate with: openssl rand -base64 32)
Expand Down
Loading