Fix AddressType
when using wagmi and viem
#2421
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
While migrating to wagmi V1 in scaffold-eth/scaffold-eth-2#352 the
AddressType
is not correctly picked (We have configuredAddressType
asstring
) but it still complains type mismatch since its expecting0x{string}
.Checkout this comment -> scaffold-eth/scaffold-eth-2#352 (comment) for more context
Additional Information
Solution : My assumption is that this is caused due to version mismatch of
abiType
inviem
which uses0.8.2
andwgmi
which uses0.8.1
( seems like related to #1712 ), So updated the version of packages usingabitype
in wagmi to0.8.2
inline withviem
.Created a direct PR because felt similar to #1712, but please feel free to close this PR in favour of better option, Tysm 🙌
Your ENS/address: shivbhonde.eth