Declare a showcase frame for the hqtui.com apps gallery - #178
Merged
Conversation
hqtui.com/apps captures screenshots of applications built on the library. The capture script takes an application directory and imports `scripts/showcase.ts` from it, because only the application knows what a good state looks like. The state is driven through the real reducer, from a real connected status and the real demo script, rather than assembled by hand. A screenshot of a state the reducer cannot actually produce is a picture of something that does not exist. `demoEvent` stamps `new Date()`, which is right for a live demo and wrong for a committed screenshot twice over: the image would differ on every regeneration, and ten events sharing one second does not look like a feed. Only the clock is pinned; the content is still the real script. `demo: false` on purpose. That flag drives the badge saying whether the numbers came from a live daemon, and a showcase that quietly flags itself as demo data advertises the wrong thing. Build-time fixture only; nothing here ships in the CLI. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017Df2FNu5DhinMV2soRz3cy
ThreatCrush Security Scan12 finding(s) HIGH/CRITICAL: 1 | MEDIUM: 6 | LOW: 5
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
hqtui.com/apps captures screenshots of applications built on the library. The capture script takes an application directory and imports
scripts/showcase.tsfrom it, because only the application knows what a good state looks like.This adds ours: the live dashboard, connected.
It goes through the real reducer
The state is driven from a real connected status and the real demo script through
reducer, not assembled by hand. A screenshot of a state the reducer cannot actually produce is a picture of something that does not exist — the one thing a showcase must never be.Two details worth the review
The clock is pinned.
demoEventstampsnew Date(), which is right for a live demo and wrong for a committed screenshot twice over: the image would differ on every regeneration, and ten events sharing one second does not read as a feed. Only the timestamp is overridden — the content is still the real script.demo: falseon purpose. That flag drives the badge saying whether the numbers came from a live daemon. A showcase that quietly flags itself as demo data is advertising the wrong thing, and the dashboard is honest about this distinction by design — worth not undermining in the screenshot.Scope
Build-time fixture only. Nothing here ships in the CLI, and no application code changed.
tsc --noEmiton the new file is clean, and the pre-commit hooks (CLI build, landing page build) passed.🤖 Generated with Claude Code
https://claude.ai/code/session_017Df2FNu5DhinMV2soRz3cy