fix expected outcome on pool remove

[temptemp3]

Summary by CodeRabbit

• New Features
  • Improved the PoolRemove component for enhanced liquidity removal operations.
  • Streamlined asynchronous handling for better performance and readability.
  • Enhanced error handling to ensure accurate state updates based on withdrawal success.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to the PoolRemove component located in src/components/PoolRemove/index.tsx. The primary change is the restructuring of the useEffect hook to utilize an async function with await, replacing the previous promise-based .then() chaining. This adjustment improves readability and error handling. The logic now checks for an active account early, retrieves the account's balance within the same asynchronous function, and employs BigInt and BigNumber for precise calculations. Enhanced error handling ensures that state updates occur only after successful withdrawal operations.

Changes

File Path	Change Summary
src/components/PoolRemove/index.tsx	Restructured useEffect to use async/await, improved error handling, early exit for inactive accounts, and refined calculations with BigInt and BigNumber.

Possibly related PRs

• Fix/remove lp #22: This PR modifies the PoolRemove component, including changes to the expected outcome calculation, which is directly related to the changes made in the main PR regarding the useEffect hook and the calculation of withdrawal amounts.
• fix expected outcome on pool remove #32: This PR focuses on restructuring the useEffect hook in the PoolRemove component, similar to the main PR's changes, enhancing error handling and the calculation of expected outcomes.

Suggested labels

donotmerge

Poem

🐰 In the garden where numbers play,
A rabbit hops, brightening the day.
With async hops and await so neat,
The PoolRemove dance is now a treat!
Error checks and balances in sight,
Making liquidity removal just right! 🌼

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c3b78bc and d114611.

📒 Files selected for processing (1)

• src/components/PoolRemove/index.tsx (1 hunks)

🔇 Additional comments (1)

src/components/PoolRemove/index.tsx (1)

384-414: Overall, the refactored useEffect enhances readability

The use of an asynchronous function within the useEffect hook is appropriate here. The restructuring improves the control flow and error handling, making the code more readable and maintainable.