[ethers] Factory for connecting to existing contract instances #162
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.
This is a follow-up for PR #160 (CC issue #137)
Problem: existing methods allowed only to deploy a new contract instance, or attach to an existing address, but only connecting through a complete
Signer
/Wallet
. In actual use cases, you often don't need (or even don't want) the contract instance to have a signer connected, just a provider, to use contract'sview
orpure
functions.Proposed solution:
static connect(address: string, signerOrProvider: Signer | Provider)
-- this just invokes theContract
constructor with the same params and the hardcoded ABI (since we can't add runtime functions to our contract type declarations)