Chat-widget: Fix test theming & update env workflows #8
Conversation
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
🚀 PromptQL Build CompleteBuild Version: Description: PR #8: Chat-widget: Fix test theming & update env workflows |
✅ PromptQL Build AppliedBuild Version: |
robertjdominguez
added a commit
that referenced
this pull request
Aug 10, 2025
## Description - Replaced manual `.env` file creation with proper template-based setup - Added comprehensive theming support to the chat widget test app - Streamlined developer onboarding with clearer environment configuration Previously, developers had to manually create empty `.env` files and figure out what variables were needed: ```sh cd server && touch .env && cd ../pql && touch .env ``` Now we provide proper templates with all required variables pre-defined: ```sh cp server/.env.template server/.env cp pql/.env.template pql/.env ``` The templates include only the variables actually used in each service, with sensible defaults where appropriate. This eliminates guesswork and reduces setup friction. For the test app, the theme switcher now actually works. Previously it only controlled the widget theme while the app itself remained stuck in whatever your system preference was. Now switching themes properly updates the entire test environment with smooth transitions, making development and testing much more pleasant. The theming implementation uses `data-theme` attributes on the document root with proper CSS cascade handling for auto/light/dark modes, ensuring the theme selector controls both the test app background and the embedded widget consistently.
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.
Description
.envfile creation with proper template-based setupPreviously, developers had to manually create empty
.envfiles and figure out what variables were needed:Now we provide proper templates with all required variables pre-defined:
The templates include only the variables actually used in each service, with sensible defaults where appropriate. This eliminates guesswork and reduces setup friction.
For the test app, the theme switcher now actually works. Previously it only controlled the widget theme while the app itself remained stuck in whatever your system preference was. Now switching themes properly updates the entire test environment with smooth transitions, making development and testing much more pleasant.
The theming implementation uses
data-themeattributes on the document root with proper CSS cascade handling for auto/light/dark modes, ensuring the theme selector controls both the test app background and the embedded widget consistently.