fix(bridge-ui): custom and none fee selection overwritten by error fetching recommended fee #16737
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.
When there's an error calculating the recommended fee, the label
Error calculating processing fee, you will need to claim manually!
replaces the value of custom and none fees when these are selected instead of the Recommended fee.Regardless of the fee type selected, the error message will show up next to the 'Processing Fee' text:
With my fix, when selecting a custom fee or none fee, the selected fee amount shows accuratly: