feat: update the home page to flashtrace 0.12.0#13
Merged
Conversation
The landing page still described flashtrace as of v0.7.0. Re-captured every shown report with a real v0.12.0 run (the summary's items line now counts "from specs" instead of "from markdown") and refreshed the copy: - feature grid: add SemVer revision matching, short-form references and the JSON report; split forwarding into its own card; extend the language list; CI card now names both report formats - wildcard blurb reworded to the 0.12.0 semantics (2.x accepts anything within revision 2) - report colorizer: handle the deep/shallow breakdown on the ok summary line and drop the retired "of the ok items" note Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Group by comment style with the highest-audience representatives (C-style: JS/TS, Java, C#, Go, Rust; hash: Python, Ruby, shell; SQL, Lua, HTML/Vue) instead of an ad-hoc list, leading with the insight that a tag is just a comment. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Short-form references are too specific for the grid, and the JSON report folds into the CI card as "Rich, CI-friendly reports" - a clean 4x2 on desktop again. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What
The home page still described flashtrace as of v0.7.0. This brings it to v0.12.0, based on a read-through of every release's "What's Changed" (0.7.1 through 0.12.0) and the bodies of the user-facing PRs behind them.
Changes
Re-captured reports. Every terminal output shown on the page (hero, how-it-works step 3, all three "See it trace" examples) was re-run with a real flashtrace 0.12.0 against the exact input files shown. Only one thing drifted: the summary's items line now counts
(1 from specs, 1 from code)instead offrom markdown(upstream flashtrace/flashtrace#75 named item origins by role). Everything else was byte-identical.Feature grid ("Built to stay out of your way") - stays a clean 4x2:
2.xnow accepts anything within revision 2.Wildcard example blurb reworded to the 0.12.0 semantics ("accepts anything within revision 2" instead of "any 2.x revision" implying layer-count matching).
Report colorizer: the
oksummary line may now carry a(4 deep-covered, 1 only shallow-covered)breakdown (0.11.2, flashtrace/flashtrace#84) and the standalone "of the ok items…" note is retired - the colorizer follows.Deliberately unchanged: the primary examples keep their pre-0.10 explicit ID style (they remain valid and are the clearer introduction); short-form references stay off the grid as too specific for it; the docs pages update themselves via the deploy workflow.
Verification
pnpm buildpasses against the v0.12.0 docs (14 pages, banner shows v0.12.0);from markdownno longer appears anywhere in the built home page, and all newly linked docs pages (/docs/revisions/,/docs/json-report/) exist in the build.🤖 Generated with Claude Code