⚠️ Beta Notice
This is a beta release and you may encounter unexpected issues. We appreciate your help testing!
What's Changed
🚀 Highlights
This beta update focuses heavily on stability and code quality. A major overhaul of the testing infrastructure (splitting legacy vs. modern tests) helped identify and fix some complex logic bugs in chore workflows. Additionally, a major refactor of over 80 constants to strictly align with the new storage-only architecture.
🐛 Critical Bug Fixes
- Service Logic: Fixed the
reset_all_choresservice, which was incorrectly removing timestamps instead of resetting them, causing old claims to appear active and a few other strange behaviors after migration. - Auto-Approve: Fixed a bug where
AUTO_APPROVEpending actions were not awarding points correctly. - Scheduling Logic: Resolved an issue where
AT_MIDNIGHT_ONCEandAT_DUE_DATE_ONCEmodes were incorrectly rescheduling due dates immediately upon approval. - Shared Chores: Fixed an issue where
SHARED_FIRSTchores were being treated asINDEPENDENTduring "set" and "skip" due date service calls. - Notification Localization: Resolved missing or incorrect translation keys, ensuring a fully localized experience for all notification types.
✨ UX & Feature Enhancements
- Smoother Flows: The "Edit Chore" flow now automatically skips the per-kid date popup if only one kid is assigned to the chore.
- Clear Due Dates: Added a "Clear Due Date" checkbox to both main and per-kid forms, making it easier to remove deadlines.
- Template Fixes: Fixed an issue where template dates were not properly passing down to the per-kid date helper form.
🔧 Under the Hood
- Refactoring: Renamed and reorganized ~80 constants to strictly separate Configuration (
CONF_*), Flow (CFOF_*), and Data (DATA_*) usage per new standards. - Testing Overhaul: Complete reorganization of the test suite. We now have 905 passing tests, with new comprehensive scenarios covering complex chore lifecycles, notification workflows, and translations.
Full Changelog: 0.3.1...0.5.0b2