test(calculate): verify streak formulas for multiple weeks gaps timeline (Variation 2)

[souravjhahind]

🧩 Background

Streak computation calculations are susceptible to off-by-one errors when managing calendar offsets and date boundaries.

🎯 Objective

Add a specific test simulating weeks with 0 commits separating two active contribution stretches.

📁 Files to touch

• lib/calculate.test.ts

🛠️ Implementation steps

• Configure custom contribution data matching this pattern.
• Execute the streak calculator and assert accurate currents and longest values.

✅ Definition of done

• 1 new test case simulating this specific timeline.
• All streak mathematical assertions are accurate.

[Sanika2404]

Hi @souravjhahind,

I would like to work on this issue under GSSoC 2026.

I understand that the objective is to add a test case for streak calculations where two active contribution periods are separated by multiple weeks with zero commits. This scenario is important for validating that the streak algorithm correctly handles extended inactivity periods and accurately computes both current and longest streak values without date-boundary or off-by-one errors.

My approach will be:

• Review the existing streak calculation tests in lib/calculate.test.ts.
• Create a custom contribution dataset containing two active streak segments separated by several weeks of no contributions.
• Execute the streak calculator against this timeline.
• Verify that both current streak and longest streak values match the expected results.
• Ensure the test follows existing project conventions and passes successfully with the full test suite.

I will submit a clean and thoroughly tested PR once the implementation is complete.

Could you please assign this issue to me?

Thank you!

[github-actions]

👋 Hey @Sanika2404! Looks like you want to work on this issue — awesome! 🎉

We don't assign issues through comments like this. Here's how our system works:

🤖 How to Claim an Issue

Comment /claim on this issue and our bot will automatically assign it to you (if you're eligible).

/claim

⚠️ Note: Only the issue author (@souravjhahind) can /claim this issue. If you'd like to contribute, consider opening a new issue for a bug or feature you've found, then claim that one!

📋 A Few Things to Know

• You can hold a maximum of 3 open issues at a time.
• If there's no activity for 3 days, the assignment will automatically expire so others can pick it up.
• Make sure to read our CONTRIBUTING.md before you start — it covers code style, commit conventions, and the PR checklist.

💬 Join Our Discord

Get faster help, collaborate with other contributors, and stay updated with project news:

Happy contributing! 🚀

[VarshithaChettipalli]

/claim

Hi @souravjhahind

I would like to work on this issue under GSSoC 2026.

I have experience with React and frontend development and would love to contribute. Kindly assign this issue to me.

Thank you!

[github-actions]

🎉 Assigned! Welcome to the project, @VarshithaChettipalli.

⏳ Reminder: You have 2 days to submit a Pull Request. After 2 days of inactivity, you will be automatically unassigned to give others a chance (as per our GSSoC anti-hoarding policy).

💡 Please read CONTRIBUTING.md if you haven't already.

Happy coding! 🚀