fix(FirestoreDb): correct getLatestAlarm else branch to use current minute without offset#881
Merged
MarkisDev merged 1 commit intoCCExtractor:mainfrom Apr 19, 2026
Conversation
…inute without offset
MarkisDev
approved these changes
Apr 19, 2026
NihalDR
pushed a commit
to NihalDR/ultimate_alarm_clock
that referenced
this pull request
Apr 20, 2026
…inute without offset (CCExtractor#881)
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
2 participants
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
Fixes #880
As noted in the issue, the
elsebranch ofgetLatestAlarminsidefirestore_provider.dartwas an identical copy of theifbranch (both added+ 1to the current minute). This causedwantNextAlarm = falseto behave exactly likewantNextAlarm = true.Proposed Changes
Removed the
+ 1from theelsebranch. This logic now correctly matches the Isar provider's implementation of the same method.Screenshots
N/A
Checklist