-
-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(walletconnect): handle all possible response types from algo_sign…
…Txn (#185) There are no restrictions or rules about the `algo_signTxn` RPC method response type. Each wallet can decide on its own how to format the signed transactions it returns. (This should probably be spec'd or defined somewhere!) The WalletConnect provider now handles numerous potential response types, to make sure it always returns an array of encoded signed transactions as `Promise<Uint8Array[]>`. Its signing function response is now typed as ```ts type SignTxnsResponse = Array<Uint8Array | string | null | undefined> ```
- Loading branch information
Showing
2 changed files
with
24 additions
and
4 deletions.
There are no files selected for viewing
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
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