Disabling the send button until is ready for transfer #527
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.
Fixes #526
Description
Our wallet consists of several ways to authenticate the user and therefore different ways to carry out a transaction. The method that WalletConnect uses is the only one that requires two steps to perform a transaction: the creation of the sendConfig object and the actual execution of the transfer.
However, it happens that if the user tries to execute the transfer before the configuration object is ready, the error described in #526 occurs.
To avoid that, we disable the submit button until we're sure the config object is ready to be used.
Test scenarios
Checklist: