Skip to content

fix : use effectiveTodayStr instead of localTodayStr for resolvedTodayDate in streak calculation - #18

Closed
tmdeveloper007 wants to merge 1 commit into
mainfrom
fix/8683-todayIndex-effectiveTodayDate
Closed

tmdeveloper007 wants to merge 1 commit into
mainfrom
fix/8683-todayIndex-effectiveTodayDate

Conversation

@tmdeveloper007

Copy link
Copy Markdown
Owner

Summary of What Has Been Done

Fixed an unconditional overwrite of resolvedTodayDate in calculateStreak in lib/calculate.ts. The variable was initialized to localTodayStr but should be initialized to effectiveTodayStr to correctly reflect vacation-adjusted dates.

Changes Made

  • lib/calculate.ts: Changed let resolvedTodayDate = localTodayStr; to let resolvedTodayDate = effectiveTodayStr; in calculateStreak

Impact it Made

  • Streak dates correctly reflect vacation-adjusted effective dates
  • Improves accuracy of streak tracking when vacation mode is active
  • Fixes streak calculation for users with vacation dates configured

Closes

Closes #8683

Note

Please assign this PR to the tmdeveloper007 account.

@github-actions github-actions Bot added the needs-details This PR is missing required description details. label Aug 4, 2026
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

👋 Hey @tmdeveloper007, it looks like you didn't use our PR template!

The section ## Description is missing from your PR description.

Please update your PR description to include all required sections so we can review this properly:

  • ## Description — What does this PR do? Which issue does it fix?
  • ## Pillar — Which contribution pillar does this fall under?
  • ## Checklist — Have you ticked off the quality checklist?

You can find the full template in CONTRIBUTING.md. Just edit your PR description and the needs-details label will be removed automatically. 🙌

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

👋 Hey @tmdeveloper007!

Unfortunately, this PR has been automatically closed because the referenced issue #8683 does not exist (or was deleted).

To resolve this, please do the following:

  1. Link a valid open issue by editing your PR description to include a closing keyword (e.g., Fixes #<issue-number>).
  2. Reopen this PR once the link is added.

Please link a valid open issue before this PR can be reviewed. 🙏

@github-actions github-actions Bot closed this Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-details This PR is missing required description details.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant