vchuserandClaude Opus 5
4201643fc5
The lazy quantifier {4,6}? never expanded beyond its minimum because
the trailing greedy [A-Z0-9]* always absorbed the rest up to the
hyphen, so a longer density code would silently be truncated to 5
chars and could match an unrelated table entry, producing wrong specs
instead of null. The density code is actually fixed-width (A + 4
chars); the revision after it is the variable part. Tighten the
pattern to {4}, rewrite the stale comment (which still claimed a fixed
3-char revision), and add a test that every Samsung density key is
exactly 5 characters so a future mismatched table entry can't silently
become unreachable.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ocr_scanner
Short description of what this project does.
Getting Started
Prerequisites
- Node.js 20+
- npm or pnpm
Installation
npm install
Development
npm run dev
Tech Stack
- ...
Project Structure
src/
...
License
...