Repository navigation
Save raw coupon OCR responses by Telegram file ID - #564
Merged
Merged
Conversation
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.
Coupon OCR responses are discarded after parsing, leaving no source data for investigating incorrect recognition. Save the raw Azure JSON in
coupon_ocr, keyed by Telegram file ID, immediately after OCR and before parsing. Repeat recognition replaces the saved response; single-photo, album, and manual-add flows all save it.Includes the migration with service-role grants and integration coverage for persistence, replacement, and survival after coupon cleanup. Coupon date parsing and the additional coupon regression fixture are unchanged.
Validation: the unchanged OCR suite passes in Release on this branch. The 16 OCR add-flow integration tests passed before isolating this commit.