From 69de2e3afab5a5ebe5109de1867fac25691b8f7f Mon Sep 17 00:00:00 2001 From: Adam Spiers Date: Fri, 1 May 2026 20:49:21 +0000 Subject: [PATCH] docs(demo): tighten EPDS_CLIENT_THEME e2e note per PR #145 review - Drop the misleading "@client-branding" tag reference (no such tag exists; copilot caught this) and reference the file path instead. - Replace the malformed "expect(html).toContain('...')" snippet with the actual playwright error substring a contributor would see in their failure output (coderabbit flagged the quote/paren mismatch). --- packages/demo/.env.example | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/packages/demo/.env.example b/packages/demo/.env.example index 95636f28..9914459d 100644 --- a/packages/demo/.env.example +++ b/packages/demo/.env.example @@ -49,11 +49,12 @@ AUTH_ENDPOINT=https://auth.pds.example/oauth/authorize # 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 -# "expect(html).toContain('body { background: #1a1208')" mismatches. +# Required (uncomment) to run the client-branding e2e feature locally +# (see features/client-branding.feature): the suite asserts that +# auth-service inlines the demo's branding CSS, which only happens +# when client-metadata.json advertises one. Without it, the scenarios +# in that feature file fail with playwright errors containing +# `Expected substring: "body { background: #1a1208"`. # EPDS_CLIENT_THEME=amber # Session signing secret (generate with: openssl rand -base64 32)