Skip to content

fix: error state when amount exceed wallet balance#649

Merged
jjramirezn merged 1 commit intopeanut-walletfrom
fix/send-bal-exceed
Jan 27, 2025
Merged

fix: error state when amount exceed wallet balance#649
jjramirezn merged 1 commit intopeanut-walletfrom
fix/send-bal-exceed

Conversation

@kushagrasarathe
Copy link
Copy Markdown
Contributor

@kushagrasarathe kushagrasarathe commented Jan 27, 2025

  • updated the error state if send amount + gas exceeds wallet balance
  • now preventing going to confirm send view if balance is not there for gas

fixes TASK-8303

Summary by CodeRabbit

  • Bug Fixes
    • Improved error handling for transactions with insufficient wallet balance
    • Enhanced user feedback when transaction fees exceed available funds
    • Clarified error message to guide users on resolving balance-related transaction issues

@vercel
Copy link
Copy Markdown

vercel bot commented Jan 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
peanut-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 27, 2025 9:03am

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 27, 2025

Walkthrough

The pull request focuses on improving error handling for transaction fee calculations and user balance checks. Changes are implemented in two files: src/components/Create/Link/Input.view.tsx and src/utils/sdkErrorHandler.utils.tsx. The modifications enhance the user experience by providing more precise error messages when a user's wallet balance is insufficient to cover transaction fees, guiding them to adjust their transaction amount accordingly.

Changes

File Change Summary
src/components/Create/Link/... Added logic to calculate total transaction amount including token value and gas fees
src/utils/sdkErrorHandler.utils.tsx Introduced new error handling case for insufficient balance, with a more specific user-friendly error message

Possibly related PRs

Suggested reviewers

  • Hugo0
  • panosfilianos

Poem

🐰 A Rabbit's Transaction Tale 🚀

Fees and balance, a delicate dance,
Checking funds with a mathematical glance,
Error messages clear as can be,
Guiding users with finesse and glee,
Transaction magic, smooth and light! 💸


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@notion-workspace
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
src/utils/sdkErrorHandler.utils.tsx (1)

100-101: LGTM! Consider standardizing error message format.

The new error handling case correctly addresses the insufficient balance scenario. The message is clear and actionable.

Consider standardizing the error message format with other messages in the file:

  • Some messages end with a period
  • Some messages don't have punctuation
  • Some start with "Please"
-            return 'You do not have enough balance to cover the transaction fees, try again with a lower amount'
+            return 'You do not have enough balance to cover the transaction fees. Please try again with a lower amount.'
src/components/Create/Link/Input.view.tsx (2)

181-188: Add null safety checks for undefined values.

The comparison might fail if transactionCostUSD is undefined.

Consider adding explicit null safety checks:

-        if (totalAmount > walletBalance) {
+        if (!transactionCostUSD) {
+            console.warn('Transaction cost estimation failed')
+            return
+        }
+        if (totalAmount.gt(walletBalance)) {

185-185: Extract duplicate error message to a constant.

The same error message is duplicated at lines 185 and 215.

Consider extracting it to a constant:

+const INSUFFICIENT_BALANCE_ERROR = 'You do not have enough balance to cover the transaction fees, try again with a lower amount'

 // Then use it in both places:
-                                errorMessage:
-                                    'You do not have enough balance to cover the transaction fees, try again with a lower amount',
+                                errorMessage: INSUFFICIENT_BALANCE_ERROR,

Also applies to: 215-215

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 66fee2d and 7ed657f.

📒 Files selected for processing (2)
  • src/components/Create/Link/Input.view.tsx (2 hunks)
  • src/utils/sdkErrorHandler.utils.tsx (1 hunks)
🔇 Additional comments (1)
src/components/Create/Link/Input.view.tsx (1)

178-189: LGTM! The balance check implementation aligns with PR objectives.

The implementation correctly:

  1. Calculates total amount including gas fees
  2. Prevents proceeding if balance is insufficient
  3. Provides clear user feedback

Comment on lines +179 to +180
const totalAmount = parseFloat(tokenValue ?? '0') + (transactionCostUSD ?? 0)
const walletBalance = parseFloat(maxValue ?? '0')
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Use safer number handling for financial calculations.

The current implementation uses floating-point arithmetic which can lead to precision issues in financial calculations.

Consider using a decimal arithmetic library like decimal.js or bignumber.js:

-        const totalAmount = parseFloat(tokenValue ?? '0') + (transactionCostUSD ?? 0)
-        const walletBalance = parseFloat(maxValue ?? '0')
+        const totalAmount = new BigNumber(tokenValue ?? '0').plus(transactionCostUSD ?? '0')
+        const walletBalance = new BigNumber(maxValue ?? '0')

Committable suggestion skipped: line range outside the PR's diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants