Contract.connect() returns a BaseContract

[TomiOhl]

Ethers Version

6.6.2

Search Terms

connect, contract, migration, BaseContract

Describe the Problem

Since a Contract's connect method returns a BaseContract, it apparently doesn't have the methods from the abi - at least according to typescript (vs code?).
The error message is: Property 'setFee' does not exist on type 'BaseContract'.ts(2339) (where setFee is the name of the function I'm calling).
Note that the code still runs fine.

Code Snippet

// this gives error
await contract.connect(randomWallet).setFee(ethers.ZeroAddress, 12);

// this is fine
await (contract.connect(randomWallet) as Contract).setFee(ethers.ZeroAddress, 12)

Contract ABI

["function setFee(address token, uint256 newFee)"]

Errors

Property 'setFee' does not exist on type 'BaseContract'.ts(2339)

Environment

Ethereum (mainnet/ropsten/rinkeby/goerli), node.js (v12 or newer), Hardhat

Environment (Other)

No response

[TomiOhl]

Even openzeppelin is using a workaround right now (though for attach()): https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/master/packages/plugin-hardhat/src/utils/ethers.ts#L6-L8

[ricmoo]

Also, that Contract should probably pass the typing along in the pass-through function.

[cimeriann]

Hi @TomiOhl , has this issue been resolved yet? in my case, I'm trying to do a transfer(using connect)

[TomiOhl]

@Olaaa30 haven't updated to a newer version of ethers yet, currently I'm using the workaround I included in the issue (casting as Contract)

[ricmoo]

I am working on a more robust solution that will incorporate the EVMts library, which derives the typing information from the ABI.

The only issue is the typing, so it is safe to cast the return type to the known type. :)

[cimeriann]

@TomiOhl okay, thanks...guess I'll stick to that too for now