Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / wagmi-dev/wagmi issues and pull requests
#2898 - bug: Overriding `AddressType` dosen't work with latest wagmi / viem versions
Issue -
State: open - Opened by technophile-04 about 1 year ago
#2898 - bug: Overriding `AddressType` dosen't work with latest wagmi / viem versions
Issue -
State: open - Opened by technophile-04 about 1 year ago
#2898 - bug: Overriding `AddressType` dosen't work with latest wagmi / viem versions
Issue -
State: open - Opened by technophile-04 about 1 year ago
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2894 - docs: error specifying chainId in multicall
Issue -
State: closed - Opened by mintdart about 1 year ago
- 1 comment
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2891 - bug: Ethers.js Adapters error
Issue -
State: closed - Opened by LXVC about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2888 - bug: Can't use react-query devtools
Issue -
State: closed - Opened by amirhhashemi about 1 year ago
- 1 comment
#2887 - bug: Can't submit transaction to Safe Apps SDK (invalid BigNumber value)
Issue -
State: closed - Opened by LilaRest about 1 year ago
- 2 comments
#2887 - bug: Can't submit transaction to Safe Apps SDK (invalid BigNumber value)
Issue -
State: closed - Opened by LilaRest about 1 year ago
- 3 comments
#2887 - bug: Can't submit transaction to Safe Apps SDK (invalid BigNumber value)
Issue -
State: closed - Opened by LilaRest about 1 year ago
- 2 comments
#2887 - bug: Can't submit transaction to Safe Apps SDK (invalid BigNumber value)
Issue -
State: closed - Opened by LilaRest about 1 year ago
- 2 comments
#2887 - bug: Can't submit transaction to Safe Apps SDK (invalid BigNumber value)
Issue -
State: closed - Opened by LilaRest about 1 year ago
- 2 comments
#2887 - bug: Can't submit transaction to Safe Apps SDK (invalid BigNumber value)
Issue -
State: closed - Opened by LilaRest about 1 year ago
- 2 comments
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2886 - bug: Abi was lost when calling write of useContractWrite
Issue -
State: closed - Opened by alienzhangyw about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2884 - Fix `AddressType` mismatch type error
Pull Request -
State: open - Opened by technophile-04 about 1 year ago
- 2 comments
#2884 - Fix `AddressType` mismatch type error
Pull Request -
State: open - Opened by technophile-04 about 1 year ago
- 2 comments
#2884 - Fix `AddressType` mismatch type error
Pull Request -
State: open - Opened by technophile-04 about 1 year ago
- 2 comments
#2884 - Fix `AddressType` mismatch type error
Pull Request -
State: open - Opened by technophile-04 about 1 year ago
- 2 comments
#2884 - Fix `AddressType` mismatch type error
Pull Request -
State: open - Opened by technophile-04 about 1 year ago
- 2 comments
#2884 - Fix `AddressType` mismatch type error
Pull Request -
State: open - Opened by technophile-04 about 1 year ago
- 2 comments
#2884 - Fix `AddressType` mismatch type error
Pull Request -
State: open - Opened by technophile-04 about 1 year ago
- 2 comments
#2883 - docs: fix typo in RPC Providers docs
Pull Request -
State: closed - Opened by dschlabach about 1 year ago
- 2 comments
#2883 - docs: fix typo in RPC Providers docs
Pull Request -
State: closed - Opened by dschlabach about 1 year ago
- 2 comments
#2880 - bug: watchContractEvent missing multiple logs from same transaction
Issue -
State: closed - Opened by illestrater about 1 year ago
- 1 comment
#2880 - bug: watchContractEvent missing multiple logs from same transaction
Issue -
State: closed - Opened by illestrater about 1 year ago
- 1 comment
#2880 - bug: watchContractEvent missing multiple logs from same transaction
Issue -
State: closed - Opened by illestrater about 1 year ago
- 1 comment
#2880 - bug: watchContractEvent missing multiple logs from same transaction
Issue -
State: closed - Opened by illestrater about 1 year ago
- 1 comment
#2878 - bug: `useContractsReads()` cause component re-render even if data hasn't changed
Issue -
State: open - Opened by LilaRest about 1 year ago
- 8 comments
#2878 - bug: `useContractsReads()` cause component re-render even if data hasn't changed
Issue -
State: open - Opened by LilaRest about 1 year ago
- 10 comments
#2878 - bug: `useContractsReads()` cause component re-render even if data hasn't changed
Issue -
State: open - Opened by LilaRest about 1 year ago
- 8 comments
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2877 - chore: version packages
Pull Request -
State: closed - Opened by github-actions[bot] about 1 year ago
- 1 comment
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2875 - bug: <title>为什么useContractRead 返回的数据为0n,实际上是有数据的,而且是18位
Issue -
State: closed - Opened by voledy about 1 year ago
- 1 comment
Labels: M: Needs Reproduction
#2874 - bug: Metamask Connector triggering other injected wallets instead of metamask
Issue -
State: closed - Opened by chiragpay3 about 1 year ago
- 1 comment
#2874 - bug: Metamask Connector triggering other injected wallets instead of metamask
Issue -
State: closed - Opened by chiragpay3 about 1 year ago
- 1 comment
#2874 - bug: Metamask Connector triggering other injected wallets instead of metamask
Issue -
State: closed - Opened by chiragpay3 about 1 year ago
- 1 comment
#2874 - bug: Metamask Connector triggering other injected wallets instead of metamask
Issue -
State: closed - Opened by chiragpay3 about 1 year ago
- 1 comment
#2874 - bug: Metamask Connector triggering other injected wallets instead of metamask
Issue -
State: closed - Opened by chiragpay3 about 1 year ago
- 1 comment
#2872 - bug: args stripped from [[1n]] to [] in usePrepareContractWrite
Issue -
State: closed - Opened by 0xartcro about 1 year ago
- 1 comment