Fix: pass config parameter to useConnectorClient in useSimulateContract and useEstimateGas #4447
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.
Added the config parameter to
useConnectorClient
parameters when used inuseSimulateContract
anduseEstimateGas
.useConnectorClient
would always calluseConfig
as config wasn't provided in the parameters, this broke providing a config to either hook and would meanuseConfig
was triggered in both hooks. This caused an error whenWagmiProvider
wasn't available in the context, asuseConnectorClient
would calluseContext(WagmiContext)
even if a config parameter was provided to the parent hooks.