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
The wevm team recommends using tree-shakable clients with useClient and useConnectorClient, but there doesn't seem to be a way to take advantage of these alongside wagmi's built-in hooks. Allowing us to pass in a client with each hook means we could use chain-specific clients (useClient({ chainId: ... })) and also extend them as needed (e.g. to override underlying actions).
With this approach, I would be able to work around this issue by extending the connector client with public actions tied to a client that uses the RPC rather than the injected provider's RPC.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The wevm team recommends using tree-shakable clients with
useClient
anduseConnectorClient
, but there doesn't seem to be a way to take advantage of these alongside wagmi's built-in hooks. Allowing us to pass in a client with each hook means we could use chain-specific clients (useClient({ chainId: ... })
) and also extend them as needed (e.g. to override underlying actions).With this approach, I would be able to work around this issue by extending the connector client with public actions tied to a client that uses the RPC rather than the injected provider's RPC.
Beta Was this translation helpful? Give feedback.
All reactions