🚑️ app: fix missing slippage on repay max amount

[cruzdanilo]

---

Summary by CodeRabbit

Bug Fixes

• Fixed missing slippage adjustment when using the maximum repay amount feature, ensuring proper price protection during transactions.

[changeset-bot]

🦋 Changeset detected

Latest commit: fc1081d

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello @cruzdanilo, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical issue within the application's repayment mechanism where the maximum repayable amount was not accurately reflecting potential slippage. The change ensures that the calculation for maxRepay now incorporates a necessary slippage value, leading to more precise and reliable transaction estimates for users.

Highlights

• Repay Max Amount Calculation: The maxRepay calculation in the Pay component was updated to correctly apply a slippage parameter (10_000n) when determining the maximum amount a user can repay, resolving a previous oversight.

Changelog

• .changeset/brave-falcon-swim.md
  • Added a new changeset file to document the fix for missing slippage on repay max amount.
• src/components/pay-mode/Pay.tsx
  • Corrected the maxRepay calculation by adding a 10_000n slippage parameter to the pad function.

Activity

• No human activity detected in the pull request.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Warning

Rate limit exceeded

@cruzdanilo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 6 minutes and 20 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

Introduces a SLIPPAGE_DIVISOR constant to standardize slippage calculations in the Pay component. Refactors maxRepay and maxAmountIn computations to use this constant, addressing missing slippage on repay max amount. Includes changeset documentation for the patch version bump.

Changes

Cohort / File(s)	Summary
Changeset .changeset/brave-falcon-swim.md	Added changeset entry documenting patch fix for missing slippage on repay max amount in @exactly/mobile package.
Slippage Constant & Refactoring src/components/pay-mode/Pay.tsx	Introduced SLIPPAGE_DIVISOR constant (1_000n) and refactored pad calculations for maxRepay and maxAmountIn to use it consistently, removing previous hardcoded value (1000n).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main fix: adding missing slippage to the repay max amount calculation, which matches the core changes in the PR.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch github

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

Devin Review found 0 potential issues.

View 2 additional findings in Devin Review.

[devin-ai-integration]

Devin Review found 0 new potential issues.

View 3 additional findings in Devin Review.

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.50%. Comparing base (9cd2bdb) to head (fc1081d).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #782   +/-   ##
=======================================
  Coverage   69.50%   69.50%           
=======================================
  Files         207      207           
  Lines        7201     7202    +1     
  Branches     2256     2256           
=======================================
+ Hits         5005     5006    +1     
  Misses       2007     2007           
  Partials      189      189           

Flag	Coverage Δ
e2e	69.48% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fe02c3a218

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[coderabbitai]

Actionable comments posted: 1

[devin-ai-integration]

Devin Review found 0 new potential issues.

View 4 additional findings in Devin Review.

[sentry]

Sentry Issue: EXA-1AT