Open
Conversation
bjorkert
approved these changes
Feb 28, 2026
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.
This change allows overriding the time zone used for the graph.
Backstory: When traveling for work and monitoring my son's numbers remotely, I get confused when the graph uses my time zone instead of his. I prefer to set it to his time zone, so it aligns with his sleep time, meal time, etc.
I added a setting under Graph Settings to override the graph time zone:
For example, if I'm in London and my son is in San Francisco:
before
after
Note: When the time zone override is changed,
markDirty()forces the time axis update. The pills on the graph points don't get updated immediately and require an app reload — this is consistent with how the graph behaves currently on the actual time zone changes, so I kept it that way.