Content
@
0 reply
0 recast
0 reaction
Varun Srinivasan
@v
Someone asked in the conference what Foundry improvements would be helpful. A big one that we're struggling with today when deploying FC contracts is producing TS ABIs from the Foundry artefacts.
2 replies
0 recast
4 reactions
gakonst
@gakonst
What's a TS ABI? Any examples in mind?
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
High level problem is that sometimes verification fails (due to quirks of Etherscan or w/e) and we want a valid ABI object to copy paste, but there are lots of little gotchas that don't work today. I think @horsefacts.eth has some ideas he wants to contribute here, once we're done with the OP mainnet migration
2 replies
0 recast
0 reaction
Varun Srinivasan
@v
TS ABI = valid typescript ABI object
2 replies
0 recast
0 reaction
Pierrick
@pierrick
So what’s generated in the out folder of Foundry projects is not a valid TypeScript ABI? What could be nice is that in complement of the out folder, it generates a folder with only the ABIs of the project and without including the ones from imported libraries. This folder could then be committed.
0 reply
0 recast
0 reaction
