-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
Description
I ran into a few issues while testing the receipt flow things like duplicate entries being saved, the edit/update logic not behaving as expected, and some parsing quirks. After digging through the code, I traced most of it back to the imageHandler and
updateReceipt
logic.
I'd like to fix these to make the core CRUD operations more reliable.
Identified Issues
Critical
- Infinite Loop: Uploading a receipt causes the bot to continuously process its own response messages, creating an infinite loop.
Logic & Data Integrity
- Duplicate Saves: Confirming an upload saves the receipt twice - once immediately on upload and again on confirmation.
- Updates create duplicates: Editing a receipt (especially the date) creates a new entry instead of updating the existing record. This appears to be caused by incorrect parameter order in
getReceiptByUniqueID. - NaN Prices: Entering invalid characters in the price field saves as
NaNinstead of validating or reverting.
UI & Parsing
- Broken Actions: The "Edit" and "Delete" buttons often fail to trigger, likely due to
uiHandlernot being initialized when the buttons render. - Date Parsing: Natural language dates with ordinals (e.g., "18th Aug") fail to parse and default to the current date.
Recording.2026-01-21.060922.mp4
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels