Nicholas Charriere
@pushix
Has anybody migrated to wagmi v1? The migration guide is super intense, lots of changes https://wagmi.sh/react/migration-guide
6 replies
1 recast
2 reactions
Colin
@colin
I've been a bit frustrated with all the breaking changes across Wagmi since we started using it. Understandable since it was under active development and not a stable version, but alas, required nontrivial amounts of time to migrate & test. Not looking forward to migrating to v1
2 replies
0 recast
1 reaction
Nicholas Charriere
@pushix
I'm a little shocked at how much there is for V1. It's tough for us at Privy because we have to both do the migration ourselves but some of our customers won't have migrated. So we probably need to supported compatibility versions for both. I'm getting python2/3 PTSD.
3 replies
0 recast
0 reaction
jxom
@jxom
Sorry, we are just pushing for better UX & DXs over here! These things need to happen.
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
IMO this isn't better UX/DX. "Wallet" terminology is confusing and ethers had it actually corrected from web3. I don't doubt your good intentions but you aren't making DX better. I'm frustrated and that is my dev experience. https://web3js.readthedocs.io/en/v1.10.0/web3-eth-accounts.html?highlight=wallet#wallet
1 reply
0 recast
1 reaction
Nicholas Charriere
@pushix
I actually agree that `signer` is a really good name. I prefer Public Client to provider... I would pick: public client / signer
1 reply
0 recast
0 reaction