aboutsummaryrefslogtreecommitdiff
path: root/tests/network-diagnostics
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-11 23:36:51 -0500
committerCraig Jennings <c@cjennings.net>2026-07-11 23:36:51 -0500
commitbd84f9008e6ebf32c7f2a0befb2b20feb8c1fa48 (patch)
tree0fa45927130af69dfb9dda78ce4a9956dcba2298 /tests/network-diagnostics
parent23edcfbd97d9d821b01f789b59dd81a567ec93c0 (diff)
downloadarchsetup-bd84f9008e6ebf32c7f2a0befb2b20feb8c1fa48.tar.gz
archsetup-bd84f9008e6ebf32c7f2a0befb2b20feb8c1fa48.zip
refactor(gallery): extract design tokens to one source for 3 targets
The colors, glows, gradient ramp, and pulse rate were hardcoded literals scattered across ~40 sites in the gallery. Retuning the amber meant a find-and-replace through the whole file. I pulled them into tokens.json as the single source. gen_tokens.py reads that source and emits three targets: web CSS custom properties (into the gallery :root, between markers), waybar GTK @define-color declarations, and an elisp alist for the future svg.el renderer. The three genuinely differ (CSS --vars with rgb-triple glows, GTK @define-color with underscore names, elisp hex alist), which is why one generator beats three hand-maintained copies. The amber hue is defined once, and its glow triples are derived from the hex, so retuning it means editing one line and rerunning the generator. The gallery render is unchanged. I verified it pixel-identical against the prior commit with reduced-motion forced and the live clock masked (diff of 0). Tests cover hex conversion, the three emitters, marker replacement, and idempotency: 27 tests, 100% line coverage, wired into make test-unit.
Diffstat (limited to 'tests/network-diagnostics')
0 files changed, 0 insertions, 0 deletions