Memoize DiscountProgressBar tier scans and derived values

[RUKAYAT-CODER]

Overview
In src/components/courses/DiscountProgressBar.tsx the two useMemo blocks (lines 51-60) key off normalizedSpend, but the tier markers/list (lines 107-128) re-scan with the raw currentSpend on every render, and maxThreshold/progressPercent (lines 46-48) are recomputed unmemoized each render. Memoize the tier scans and derived values consistently.

[Evaristus023]

@Evaristus023 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I’ve thoroughly reviewed the issue description and have a clear understanding of the expected outcome. I’d love the opportunity to work on this issue. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Evaristus023 to this issue.

[temieehade-coder]

@temieehade-coder has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer, I can fix this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @temieehade-coder to this issue.

[Obaara293]

@Obaara293 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer, I've carefully reviewed the issue description and I'm certain I can work on it and sort it out perfectly. Kindly assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Obaara293 to this issue.

[IfyJustin91]

@IfyJustin91 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainers,

I'd like to work on this issue. I understand the goal is to optimize DiscountProgressBar by consistently memoizing tier scans and derived values to eliminate unnecessary recalculations during re-renders. I can refactor the component to use useMemo effectively, preserve existing behavior, and add or update tests to ensure the optimization is correct and easy to review.

I'd appreciate being assigned to this issue. Thank you!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @IfyJustin91 to this issue.

[Rayhab2000]

@Rayhab2000 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please assign this issue to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Rayhab2000 to this issue.

[MrOmale]

@MrOmale has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I will love to work on this issue please.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MrOmale to this issue.

[Dickson2015]

@Dickson2015 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

The issue description is crystal clear, Maintainer I would love to be given the opportunity to work on this issue thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dickson2015 to this issue.

[divinemike019]

@divinemike019 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I’d like to work on this issue because performance optimizations have a direct impact on user experience. I’ll refactor the DiscountProgressBar to consistently memoize tier scans and derived values, eliminating unnecessary recomputations while preserving existing behavior. The implementation will be clean, efficient, and aligned with the project's coding standards, ensuring improved render performance without introducing regressions.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @divinemike019 to this issue.

[CodeMayor]

@CodeMayor has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to work on this issue because it improves rendering efficiency without changing component behavior. I'll refactor the repeated tier scans and derived calculations into consistent memoized values, ensure dependency arrays are correct, and keep the implementation aligned with the existing React patterns while avoiding unnecessary recomputation.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CodeMayor to this issue.

[chuks68]

@chuks68 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would like to work on this issue because i am confident i can resolve the issue, having worked on and resolved similar issues. my eta is 4 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @chuks68 to this issue.

[drips-wave]

Congratulations, @chuks68! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @chuks68: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊