fix(streaks): use user timezone for date strings (#241) - #251
Merged
phertyameen merged 3 commits intoFeb 24, 2026
Conversation
phertyameen
approved these changes
Feb 24, 2026
phertyameen
left a comment
Member
There was a problem hiding this comment.
The utils function solved the date issue. I just need to twick it to fit more into our current providers
phertyameen
self-requested a review
February 24, 2026 01:19
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.
Fix UTC-based date strings causing incorrect streak/quest behavior (#241)
Problem
toISOString()were UTC-only.Solution
getDateString(timeZone, offsetDays)utility inshared/utils.X-User-Timezoneheader (default: UTC).Acceptance Criteria
Testing
Closes Fix UTC-based date strings causing incorrect streak/quest behavior for non-UTC users #241