Skip to content

Correct the built-in UI size in the README; tidy stale doc comments#98

Merged
FumingPower3925 merged 1 commit into
mainfrom
fix/docs-size
Jun 16, 2026
Merged

Correct the built-in UI size in the README; tidy stale doc comments#98
FumingPower3925 merged 1 commit into
mainfrom
fix/docs-size

Conversation

@FumingPower3925

Copy link
Copy Markdown
Owner

Docs only — no code change, logged under [Unreleased] (no version bump).

The final pre-announcement sweep caught the README still calling the built-in docs page ~1.6 KB (its size at v0.1.0). It's grown to ~10 KB since (security headers, the dismissable notice, method badges, expandable operations) — I measured the served /docs/ page at 10105 bytes against v0.6.7. It was also off from rawui.go's own comment.

  • README.md (×2: features bullet + UI table) ~1.6 KB~10 KB
  • rawui.go comment ~6 KB~10 KB (the served page is the source of truth)
  • cmd/demo/main.go + doc.go: reworded two comments that referenced the old "Tier" vocabulary the package overview dropped; rewrapped one over-long doc.go line
  • CHANGELOG.md: noted under [Unreleased]

CHANGELOG.md line 607 (the historical v0.1.0 entry) keeps its original ~1.6 KB — that was accurate then.

Build / vet / gofmt clean; the default-UI CSP parity test still passes (only a comment changed, the served page bytes are unchanged).

The README still described the built-in docs page as ~1.6 KB — its size
back at v0.1.0. It has grown to ~10 KB since (security headers, the
dismissable notice, method badges, expandable operations), so the figure
was off by several times and disagreed with rawui.go. Corrected both
README spots and aligned the source comment. Also reworded a couple of
doc comments that still referenced the old "Tier" terminology the
package overview no longer uses. Logged under Unreleased — docs only, no
code change.
@FumingPower3925 FumingPower3925 merged commit 7ed116c into main Jun 16, 2026
38 checks passed
@FumingPower3925 FumingPower3925 deleted the fix/docs-size branch June 16, 2026 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant