fix(SwapModal): Max slippage value remains as set even the custom field is erased #16397
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
…ld is erased - if the slippage value is invalid, display a "N/A" text in the footer instead of a partial value Fixes #16395
caybro
requested review from
alexjba,
dlipicar,
Khushboo-dev-cpp and
anastasiyaig
Jenkins Builds
|
alaibe
approved these changes
Sep 25, 2024
dlipicar
approved these changes
Sep 25, 2024
caybro
deleted the
16395-max-slippage-value-remains-as-set-even-the-custom-field-is-erased
branch
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.
What does the PR do
Fixes #16395
Affected areas
SwapModal
Architecture compliance
My PR is consistent with this document: Architecture guidelines
Screenshot of functionality (including design for comparison)