Fixing withdraw modal updates and adding info #886
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.
Removed refetching for balance result data as it would often conflict with the max withdrawable data which would make things complicated. I chose to remove it rather than try to make it work as a constantly flowing stream of data makes keeping the form up to date while not messing with the user's input very complex. Moreover, I find it annoying when my balances are constantly changing, especially when trying to withdraw everything. I know there are some workaround we could try, but unless there are clear drawbacks to this approach, I feel it would be better to keep it simple. Additionally, I added a callout if the user is limited in how much they can withdraw due to utilization. To determine if the user is limited, I took a similar approach to the isConstrainedByUtilization by checking the withdrawablePercentage.