-
Notifications
You must be signed in to change notification settings - Fork 7
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
Reef Knot v2: rework autoconnect and remove legacy #119
Conversation
|
Separate logic, handle `chainChanged` event
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.
LGTM
Changes
reef-knot (main package)
@reef-knot/web3-react
web3-react
library, including Web3ReactProvider and ProviderWeb3 context providers. Now, a dApp must useReefKnot
context provider directly.lido-sdk
packages, including ProviderSDK context provider, required foruseSDK
hook. If a dApp useslido-sdk
and callsuseSDK
, then the ProviderSDK setup must be moved to this dApp now (you can see an example of such migration in demo-react app in this PR).useWeb3
,useDisconnect
,useConnectorInfo
,useConnectorError
reworked to work with wagmi and left for backwards compatibility, because some dApps still rely on these hooks.@reef-knot/core-react
autoConnectOnly
wallet adapters (for Ledger Live, Safe and mobile dApp Browsers)@reef-knot/ledger-connector
@reef-knot/connect-wallet-modal
autoConnectOnly
wallets and minor fixes.Wallet Adapters
autoConnectOnly
, which means that they will not be shown in the Wallet Connection Modal. As part of the autoconnect process, there is an attempt to detect each ofautoConnectOnly
wallets and connect if the detection is successful.Demo App (apps/demo-react)
ProviderWeb3
call, because it is removed from@reef-knot/web3-react
. UseReefKnot
context provider directly and setupProviderSDK
separately.Tasks
Resolves SI-1040, SI-1110, SI-1120