chore: adopt verification-grid hardware table generator#8
Merged
Conversation
Port the registry-backed build-hardware-table.mjs from brother-ql so the per-repo tables render the rolled-up effective supportStatus from expandVerifications (incl. propagated 'expected' across protocol siblings) instead of the legacy device-level support.status. Regenerate all five tables.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
labelwriter's
build-hardware-table.mjswas still the legacy version (reads raw JSON5, renders device-levelsupport.status, only knowsverified/partial/broken/untested). brother-ql already runs the upgraded generator; this ports it over.What changes
packages/core/data/devices.jsonregistry and renders the rolled-upsupportStatusfromexpandVerifications— the same verification-grid projection the docs site uses.✅ verified · ⚠️ partial · ❌ unsupported · 🔄 expected · ⏳ unverified(legacybroken/untestedkept as fallback).🔄 expected.Effect
Regenerating all five tables (README, docs/hardware.md, 3 package READMEs) after the LW 550 USB verification:
1 verified · 21 untested→2 verified · 12 expected · 8 unverifiedLW 550 now shows ✅ verified; the 12 protocol siblings it shares
lw-raster/lw5-rasterwith surface as 🔄 expected. This also fixes the tables that were left stale when #6 merged without the regen.