Should reconnect provide a chainId to the connector's connect function?

[deodad]

If an application is automatically reconnected to a wallet should wagmi try to get the wallet onto either the the last chain the user was connected to for this dapp or if that's not available configs.chains[0]?

Something like what the walletConnect.ts connector tries to do:

        let targetChainId = chainId
        if (!targetChainId) {
          const state = (await config.storage?.getItem('state')) ?? {}
          const isChainSupported = config.chains.some(
            (x) => x.id === state.chainId,
          )
          if (isChainSupported) targetChainId = state.chainId
          else targetChainId = config.chains[0]?.id
        }
        if (!targetChainId) throw new Error('No chains found on connector.')

---

Context

We have a custom connector for wallets exposed to Mini Apps by the hosting Farcaster client (Mini Apps are rendered in iframes so we can't inject code directly to expose the provider).

In our initial implementation of the connector we would check if the chainId passed in as a parameter to the connect function on our connector matched the current chain and if not we'd request the wallet the switch chains. What we found is developers would often send transaction to wrong chain since when a user opened their app the connected wallet could be on any chain.

[tmm]

should wagmi try to get the wallet onto either the the last chain the user was connected to for this dapp or if that's not available configs.chains[0]

makes sense to me. we should make it clear that reconnect#chainId is "best effort" since not all connectors support "silent" chain switching (injected) or switching in general (safe).