Fix GoalTracker progress overflow issue

[Akankshya-35-45]

Summary

Fixes the GoalTracker progress bar overflow issue when the current value exceeds the target value.

Closes #243

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / code cleanup

Changes Made

• Added a width cap using Math.min()
• Prevented the progress bar from exceeding 100% width
• Ensured the progress bar stays within the rounded container

How to Test

Steps for the reviewer to verify this works:

1. Run the project locally using npm run dev
2. Create a goal with target = 5
3. Set current value greater than target (e.g. 8)
4. Verify that the progress bar does not overflow the container
5. Confirm the progress bar width is capped at 100%

Screenshots (if UI change)

N/A

Checklist

• Linked issue in summary
• npm run lint passes locally
• No TypeScript errors (npm run type-check)
• Self-reviewed the diff
• Added/updated tests if applicable

[vercel]

@Akankshya-35-45 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Clamps the goal progress bar width to avoid overflowing past 100%.

Changes:

• Limit the computed progress percentage used for the bar width to a maximum of 100%.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Akankshya-35-45]

Thanks for the suggestion! Updated the logic to clamp the progress value between 0 and 100 using Math.max(0, Math.min(pct, 100)) to handle negative values as well.

[Priyanshu-byte-coder]

Thanks for the fix! The progress bar overflow bug has already been fixed in PR #286 which was just merged. That PR also resolves this issue alongside the confetti feature. This PR is now conflicting with main.

The core fix (Math.min cap) is correct — it was just merged via a different PR. Closing this as resolved.