Skip to content

Move start and stop clock functionality to the ClockPageViewModelState#26

Merged
NicksPatties merged 2 commits intomasterfrom
clockpage_startAndStop_toState
Aug 16, 2022
Merged

Move start and stop clock functionality to the ClockPageViewModelState#26
NicksPatties merged 2 commits intomasterfrom
clockpage_startAndStop_toState

Conversation

@NicksPatties
Copy link
Copy Markdown
Owner

Changes

  • Moved onStartClock and onStopClock function to the ClockPageViewModelState

Related issue

#24
continuation of #25

Testing

  • Unit tests

return "0$digits"
}

// TODO may need to make onClockStart and onClockStop suspend functions so they can properly
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps something I can do at a later time, but at the same time, I wan't the app to be very snappy and reactive, so saving the event data can happen separately, but if there's something that goes wrong, I should just call another function in the ViewModelState that resets the state of variables if saving goes wrong. Something to think about.

@NicksPatties NicksPatties merged commit 42a9dee into master Aug 16, 2022
@NicksPatties NicksPatties deleted the clockpage_startAndStop_toState branch August 29, 2022 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant