-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Fix earnings calculator for flat reward amounts #2535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe code refactors the earnings calculation logic within the earnings calculator block by introducing a centralized Changes
Poem
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
apps/web/ui/partners/lander/blocks/earnings-calculator-block.tsx (1)
32-32: Clarify unit semantics forrewardAmount.
reward.amountappears to be expressed in cents for “flat” rewards and in percentage points for non-flat rewards. Storing both in a single variable namedrewardAmountrisks unit confusion and future regressions.
Consider deriving two explicit variables instead:-const rewardAmount = reward.amount ?? 0; +const rewardAmountInCents = reward.type === "flat" ? reward.amount ?? 0 : 0; +const rewardPercentage = reward.type !== "flat" ? (reward.amount ?? 0) : 0;and update the calculation paths accordingly.
This makes the code self-documenting and prevents accidental cross-unit usage.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
apps/web/ui/partners/lander/blocks/earnings-calculator-block.tsx(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build
🔇 Additional comments (1)
apps/web/ui/partners/lander/blocks/earnings-calculator-block.tsx (1)
85-89: ```shell
#!/bin/bashDisplay the top of the file for context and locate rewardAmount usage
sed -n '1,200p' apps/web/ui/partners/lander/blocks/earnings-calculator-block.tsx
rg -n 'rewardAmount' -n 'const reward' apps/web/ui/partners/lander/blocks/earnings-calculator-block.tsx</details> </blockquote></details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
|
🤖 Bug0 QA Agent Here are the results of the automated tests for PR #2535:
To re-run the tests, please comment |
Summary by CodeRabbit