refactor(parser): extract text normalizer #103
No reviewers
Labels
No labels
area:backend
area:frontend
area:infra
area:ocr
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
phase:M1
phase:M2
phase:M3
phase:M4
phase:M5
phase:M6
phase:M7
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TJC/bill-splitter!103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/90-extract-text-normalizer"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
ITextNormalizer+BasicNormalizerunderParsing/Normalization, doing generic line normalization only: trim + whitespace collapse (A2 of the ADR-0006 pipeline extraction, epic #77).ReceiptParseEnginenormalizes each line through the normalizer instead of the inlineTrim();CleanName's#code/@unitstripping stays put (item-name concern for #92), no misread fixing (#96).ReceiptParser.Parsefacade,OcrWorkercall site, pure Domain andlongminor units all unchanged.Test plan
dotnet build backend/BillSplitter.slndotnet test backend/tests/BillSplitter.Tests/BillSplitter.Tests.csproj- 85/85 green, 33-fixture corpus byte-identical.Closes #90