Per-barcode print, consistent symbology detection everywhere; v0.6.5 - #15
Merged
eigger merged 1 commit intoJul 17, 2026
Merged
Conversation
The single "print request" button on an item's barcode section always targeted whichever barcode happened to be flagged primary (or an arbitrary one if none were, since manually-added barcodes never got isPrimary set and there was no way to change it) — on a multi-barcode item there was no way to know or control which label actually printed. Each barcode row now has its own print button, and the webhook payload is built from that specific barcode instead of guessing at "primary". Symbology detection was also inconsistent across every barcode-adding entry point: the item detail page's unified add flow hardcoded "OTHER" for anything that wasn't a scanned QR, while /scan, manual item registration, and CSV import all ran a digit-shape heuristic (guessSymbology) that the detail page never called. Moved guessSymbology into packages/shared as the one implementation both apps use, added a matching scan-format mapper for when the real format is already known from a camera scan, and wired both into the detail page's manual-add route and the item registration form so a scanned or typed barcode gets the same, correct symbology (and Matter tagging, restricted to asset items) no matter which screen it was added from. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
eigger
deleted the
feature/barcode-print-per-row-consistent-symbology-v0.6.5
branch
July 17, 2026 08:26
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.
The single "print request" button on an item's barcode section always targeted whichever barcode happened to be flagged primary (or an arbitrary one if none were, since manually-added barcodes never got isPrimary set and there was no way to change it) — on a multi-barcode item there was no way to know or control which label actually printed. Each barcode row now has its own print button, and the webhook payload is built from that specific barcode instead of guessing at "primary".
Symbology detection was also inconsistent across every barcode-adding entry point: the item detail page's unified add flow hardcoded "OTHER" for anything that wasn't a scanned QR, while /scan, manual item registration, and CSV import all ran a digit-shape heuristic (guessSymbology) that the detail page never called. Moved guessSymbology into packages/shared as the one implementation both apps use, added a matching scan-format mapper for when the real format is already known from a camera scan, and wired both into the detail page's manual-add route and the item registration form so a scanned or typed barcode gets the same, correct symbology (and Matter tagging, restricted to asset items) no matter which screen it was added from.