Fix: Correct 'Use Max' Behavior to Set Input Field and Recalculate Output #142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@gabrieltemtsen is attempting to deploy a commit to the Mento Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
bayological
reviewed
Oct 7, 2024
Sure, I have |
bayological
approved these changes
Oct 10, 2024
|
Hi @bayological just checking if you're gonna merge the update since it's already approved? 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…typing in output field
Description
A few sentences describing the overall effects and goals of the pull request's commits.
What is the current behavior, and what is the updated/expected behavior with this PR?
The PR fixes the issue where the "Use Max" button incorrectly sets the output field value after a user types in the output field. The updated behavior ensures the input field is set to the maximum balance and recalculates the output based on the conversion rate when the useMax is triggered.
Other changes
Describe any minor or "drive-by" changes here.
Tested
An explanation of how the changes were tested or an explanation as to why they don't need to be.
Tested manually by entering values in both input and output fields, clicking "Use Max," and confirming the input and output fields behave as expected.
Related issues
Checklist before requesting a review