fix: Timezone-Agnostic Daily Streak Calculation (#191)#198
fix: Timezone-Agnostic Daily Streak Calculation (#191)#198nitishchaubeyy wants to merge 14 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
merge conflict |
|
Done @indresh404 |
|
Solve Merge Conflict |
1 similar comment
|
Solve Merge Conflict |
|
Done @indresh404 |
|
CI Checks / Lint Check test should pass |
|
Completed @indresh404 |
|
Solve Merge Conflict |
|
Done @indresh404 |
|
If your PR still shows the old failed Vercel check, please rebase (or merge the latest main branch into your branch) and push again to trigger a fresh deployment/check run. |
# Conflicts: # src/pages/RankHer.jsx
…tishchaubeyy/RankerHub into fix/timezone-agnostic-streaks # Conflicts: # src/pages/RankHer.jsx
|
Hey @indresh404, I synced the branch with the latest main and pushed again to trigger the deployment. I also ran npm run build and npm run lint locally, and everything compiles perfectly without any errors on my end. Since I don't have access to the Vercel logs, could you please check if it's failing due to a missing Environment Variable or a caching issue on Vercel's end? Thanks! |
Description
Resolves #191 by anchoring the Daily Activity Streak evaluation logic exclusively to standardized UTC dates, preventing local system timezones from corrupting streak continuations or permitting double-dipping.
Key Changes:
new Date()milliseconds to explicitYYYY-MM-DDISO strings representing the strict UTC boundary.Date.UTC()calculations to accurately check if the time difference is exactly 1 day (diffDays === 1).streakPointsandtotalPointsusing proper database mutation standards during the login handshake.writeBatchinfrastructure insidesyncGitHubData(Issue [Feature][Level 3] Atomic Batch Writes for Profile Sync to Prevent Data Fragmentation #193) to ensure full file compatibility.Fixes #191