Repository navigation
refactor(shared): clarify alarm values and coordinator ownership - #81
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
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.
Why
Alarm equality includes construction-time fields, theme decoding is duplicated, and ViewModel constructors obscure the shared coordinator owner. Scheduling an unsaved alarm also silently selects the newest saved row.
What changed
Scope
Blast Radius
The generated Swift copy signature and internal ViewModel constructor change. Theme IDs remain LIGHT=0, DARK=1, SYSTEM=2 with invalid values using SYSTEM; every production scheduling caller supplies a saved identity.
Verification