fix: correct error handling in connect method #41
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.
Breaking Changes
N/A
Changes
Associated Issues
closes #40
Description
reject
call in the subscription callback is handled byuseConnect
'scatch
block, bypassingWalletConnectModalSign.connect
's error handlingapproval
promise chain to remain pending afterModal closed
errorfinally
, it closes the modal, and the subscription from the subsequent attempt throws aModal closed
errorTo fix this, I consolidated the approval promise and modal closure handling within the connect method using
Promise.race
, ensuring that either a successful connection or modal closure properly resolves/rejects the promise chain.After
2024-12-03.11.38.30.mov