Skip to content

Conversation

nezz0746
Copy link
Contributor

No description provided.

Copy link
Contributor

coderabbitai bot commented Oct 28, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes in the TokenAmountInput component introduce a new key event handling feature that prevents the default action for the 'e', '+', and '-' keys, thereby disallowing scientific notation and certain mathematical symbols in the input. Additionally, minor adjustments were made to the rendering logic of the token amount label to ensure consistent output when the tokenValue is falsy. The overall functionality of the component remains unchanged, focusing on enhancing input validation and the display of token amounts.

Changes

File Path Change Summary
src/components/Global/TokenAmountInput/index.tsx Added key event handling to prevent scientific notation input and adjusted rendering logic for token amount display.

Possibly related PRs

  • Fix input amount #380: The changes in the InitialView component involve handling token amounts and formatting based on selected decimals, which relates to the input validation and display logic in the TokenAmountInput component.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0852ae6 and d7eb63d.

📒 Files selected for processing (1)
  • src/components/Global/TokenAmountInput/index.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/Global/TokenAmountInput/index.tsx

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 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.

Copy link

vercel bot commented Oct 28, 2024

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 Oct 28, 2024 2:10pm

Copy link
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

🧹 Outside diff range and nitpick comments (1)
src/components/Global/TokenAmountInput/index.tsx (1)

81-83: LGTM! Consider adding a comment explaining the e-key prevention.

The implementation correctly prevents scientific notation input, which improves the user experience for token amount entry.

Add a comment to explain why we're preventing 'e':

+                        // Prevent scientific notation ('e' key) in numeric input
                         if (e.key.toLowerCase() === 'e') {
                             e.preventDefault()
                         }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b9e1aa2 and 8d4ead5.

📒 Files selected for processing (1)
  • src/components/Global/TokenAmountInput/index.tsx (2 hunks)
🔇 Additional comments (1)
src/components/Global/TokenAmountInput/index.tsx (1)

Line range hint 22-24: Verify input validation constraints.

The component handles decimal input but lacks explicit validation for:

  • Maximum value constraints
  • Decimal place limitations
  • Precision handling for large numbers

This could lead to potential issues with token amount calculations or display.

Let's check if there are any validation utilities or constants defined elsewhere:

Consider adding:

  1. Maximum value validation
  2. Decimal place constraints
  3. Proper numeric validation using regex or validation utilities

Comment on lines 92 to 95
? '0'
: inputDenomination === 'USD'
? utils.formatTokenAmount(Number(tokenValue) / (selectedTokenData?.price ?? 0))
: '$' + utils.formatTokenAmount(Number(tokenValue) * (selectedTokenData?.price ?? 0))}
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider simplifying the nested ternary expression.

While the falsy value handling is correct, the nested ternary makes the code harder to read and maintain.

Consider refactoring to improve readability:

-                        {!tokenValue
-                            ? '0' 
-                            : inputDenomination === 'USD'
-                              ? utils.formatTokenAmount(Number(tokenValue) / (selectedTokenData?.price ?? 0))
-                              : '$' + utils.formatTokenAmount(Number(tokenValue) * (selectedTokenData?.price ?? 0))}
+                        {(() => {
+                            if (!tokenValue) return '0';
+                            const amount = inputDenomination === 'USD'
+                                ? Number(tokenValue) / (selectedTokenData?.price ?? 0)
+                                : Number(tokenValue) * (selectedTokenData?.price ?? 0);
+                            return inputDenomination === 'USD'
+                                ? utils.formatTokenAmount(amount)
+                                : '$' + utils.formatTokenAmount(amount);
+                        })()}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
? '0'
: inputDenomination === 'USD'
? utils.formatTokenAmount(Number(tokenValue) / (selectedTokenData?.price ?? 0))
: '$' + utils.formatTokenAmount(Number(tokenValue) * (selectedTokenData?.price ?? 0))}
{(() => {
if (!tokenValue) return '0';
const amount = inputDenomination === 'USD'
? Number(tokenValue) / (selectedTokenData?.price ?? 0)
: Number(tokenValue) * (selectedTokenData?.price ?? 0);
return inputDenomination === 'USD'
? utils.formatTokenAmount(amount)
: '$' + utils.formatTokenAmount(amount);
})()}

@nezz0746 nezz0746 changed the base branch from main to develop October 28, 2024 09:55
@nezz0746 nezz0746 changed the title fix: prevent e in token input [TASK-6558] prevent e in token input Oct 28, 2024
Copy link

Copy link
Contributor

@jjramirezn jjramirezn left a comment

Choose a reason for hiding this comment

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

suggestion(blocking): it's a good opportunity to prevent '+' and '-' also (they are valid in decimal mode too)

e.preventDefault()
if (onSubmit) onSubmit()
}
if (['e', '+', '-'].includes(e.key.toLowerCase())) {
Copy link
Contributor

Choose a reason for hiding this comment

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

praise: nice!

@jjramirezn jjramirezn merged commit 4c626b4 into develop Oct 28, 2024
2 checks passed
@coderabbitai coderabbitai bot mentioned this pull request May 15, 2025
@Hugo0 Hugo0 deleted the feat/preven-e-in-token-input branch July 3, 2025 18:22
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