Timezone bugfix - and change to using NaiveDate from chrono crate #23
Conversation
This file contains 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
…nsistency graph for new habits.
Open
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.
Hey there Sebastian,
I cherry-picked my master to create this branch but effectively, this fixes the timezone bug that was created whenever you crossed a dateline in the app. I've recoded things to use chrono's NaiveDate which means things are set to whatever the local date is to do the recording.
I also updated all crates to their most recent versions.
(note: this is effectively continuing on from other features I added to habictl - Skips, warns etc. so might have a few conflicts if you don't apply those first. Sorry!)