-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update/wallet connect #493
Conversation
Completes #494 |
@@ -40,7 +40,7 @@ const { getEthersLedgerAddresses } = useLedger() | |||
const { getEthersTrezorAddresses } = useTrezor() | |||
const { user } = useUser() | |||
const { detectActiveNetwork, switchEthersNetwork } = useWallets() | |||
const { connectWalletConnectV2 } = useWalletConnect() | |||
const { connectWalletConnectV2, walletConnectSelectedAccount } = useWalletConnect() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally curious, would it ever make sense to do something like:
const walletConnect = useWalletConnect()
...
watch(walletConnect.selectedAccount, () => {
...
}
composableName.someVariableOrMethodName
might be nice for organization (and less redundancy).
Not suggesting this for the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool pattern.
Made a few meaningful updates to our WalletConnect integration:
Made these changes in
mvp
. They can be ported over toapp
when we're ready to enable the WalletConnect integration there.