maxSnoozeCount Feature Implementation #816
Open
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.
Description
This PR fixes the issue with the maxSnoozeCount setting not being properly saved and retrieved from the database.
Proposed Changes
-Added the maxSnoozeCount column to the SQLite database schema in IsarDb.onCreate
-Updated the Isar database schema by regenerating it using build_runner
-Added a database fix routine (fixMaxSnoozeCountInAlarms) that ensures all alarms have the correct maxSnoozeCount value
-Added code in AlarmRingController to verify and ensure the maxSnoozeCount is correctly loaded from the database
-Fixed the startSnooze method to properly check against the actual maxSnoozeCount from the database
-Ensured the value is correctly passed through all necessary components
Screenshots
WhatsApp.Video.2025-04-12.at.22.34.57.mp4
Checklist