Library addresses interface in factories, are not human readable
See original GitHub issueWhen I am generating typechain classes for ethers-v5
, for a contract using a library with external calls, the library name in the interface is not human readable.
In the tests of the implementation of this feature in #178 , library contract name was human readable (Which makes me believe this is a bug)
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Documentation - Ethers.js
An ABI often comes from the Solidity or Vyper compiler, but you can use the Human-Readable ABI in code, which the following examples...
Read more >Chapter 3. Beans, BeanFactory and the ApplicationContext
A BeanFactory is represented by the interface org.springframework.beans.factory.BeanFactory, for which there are multiple implementations.
Read more >Factory Method - Refactoring.Guru
Factory Method is a creational design pattern that provides an interface for creating objects in a superclass, but allows subclasses to alter the...
Read more >2020 Library Systems Report | American Libraries Magazine
ProQuest's acquisition of Innovative Interfaces, which closed in January, represents a seismic shift in the library technology industry.
Read more >ipaddress — IPv4/IPv6 manipulation library — Python 3.11.1 ...
Convenience factory functions¶. The ipaddress module provides factory functions to conveniently create IP addresses, networks and interfaces: ipaddress.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like this will be a simple extentsion for the exisitng logic – the
linkReferences
object is there, just under a different path. @Lumyo would you like to prepare a PR for this? You’d need to look for thelinkReferences
object in a few places before using it in theextractLinkReferences
call herewaffle artifact:
hardhat artifact:
Thanks! Released as: https://github.com/ethereum-ts/TypeChain/releases/tag/typechain%405.1.2