Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[ethers] Expose ABI in generated code

See original GitHub issue

I’m using deployMockContract from @ethereum-waffle/mock-contract and it requires an ABI for it to be called. Typechain currently doesn’t expose this but the abi constant is in the generated factory file.

Can there be a configuration option to expose the ABI?

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:12 (7 by maintainers)

Top GitHub Comments

1reaction

krzkaczorcommented, Mar 20, 2021

How about adding the data as abi and bytecode static readonly properties of the factory class? IMO it feels better than exporting very generic names like abi or bytecode from each factory file.

Yes I think the only way to make this useful is to expose it as part of the factory class (not module).

I am fine with this change. The only problem that I see is that hardhat users confuse these factories often with factories from hardhat (and we diverge these interfaces even more) but I am planning to address it in a separate ticket (https://github.com/ethereum-ts/TypeChain/issues/359).

1reaction

quezakcommented, Mar 17, 2021

I agree that this would be useful in some cases. I actually used to import the json files too, before the factory classes were added to the ethers target here. @krzkaczor what do you think?

How about adding the data as abi and bytecode static readonly properties of the factory class? IMO it feels better than exporting very generic names like abi or bytecode from each factory file.