You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm just starting to integrate vue3-eth. We support multiple chains with a configuration for each keyed by chainId. I imagine this is how most developers will approach the problem as ethereum gives you chainId rather than e.g. "ropsten" to start with. Would you consider accepting an array of supported chainIds as an improvement? e.g. useChain(['0x1', '0x3']). If argument supplied and current network not in the array, trigger wrongNetwork.
The text was updated successfully, but these errors were encountered:
That seems reasonable, we do a single deploy per environment (e.g. ropsten for staging, localhost for dev, etc), but i don't see any reason not to support an array.
Just FYI, this plugin is pretty immature. It won't be abandoned because I have a couple of small apps based on it, but things like Walletconnect support won't happen for at least a couple months.
I'm just starting to integrate vue3-eth. We support multiple chains with a configuration for each keyed by chainId. I imagine this is how most developers will approach the problem as ethereum gives you chainId rather than e.g. "ropsten" to start with. Would you consider accepting an array of supported chainIds as an improvement? e.g.
useChain(['0x1', '0x3'])
. If argument supplied and current network not in the array, trigger wrongNetwork.The text was updated successfully, but these errors were encountered: