We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(sara) updating task list based on review of migration documentation https://wagmi.sh/react/guides/migrate-from-v1-to-v2
enabled
watch
usePrepareContractWrite
useSimulateContract
useNetwork
useAccount
useAutoConnect.ts
wagmi/chains
wagmi
configureChains
wagmi/providers/*
createConfig
The text was updated successfully, but these errors were encountered:
No branches or pull requests
(sara) updating task list based on review of migration documentation https://wagmi.sh/react/guides/migrate-from-v1-to-v2
enabled
) to query property https://wagmi.sh/react/guides/migrate-from-v1-to-v2#moved-tanstack-query-parameters-to-query-propertywatch
property https://wagmi.sh/react/guides/migrate-from-v1-to-v2#removed-watch-property https://wagmi.sh/react/guides/migrate-from-v1-to-v2#removed-prepare-hooksusePrepareContractWrite
withuseSimulateContract
(no other changes needed i think)useNetwork
, instead useuseAccount
to get the connected chain https://wagmi.sh/react/guides/migrate-from-v1-to-v2#removed-usenetwork-hookuseAutoConnect.ts
might need updates since useConnect return is changed https://wagmi.sh/react/guides/migrate-from-v1-to-v2#updated-useconnect-return-typewagmi/chains
instead ofwagmi
https://wagmi.sh/react/guides/migrate-from-v1-to-v2#updated-wagmi-chains-entrypointconfigureChains
in config files https://wagmi.sh/react/guides/migrate-from-v1-to-v2#removed-configurechainswagmi/providers/*
- replace with viem https://wagmi.sh/react/guides/migrate-from-v1-to-v2#removed-wagmi-providers-entrypointscreateConfig
in config files https://wagmi.sh/react/guides/migrate-from-v1-to-v2#updated-createconfig-parametersThe text was updated successfully, but these errors were encountered: