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.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

cto & general partner @paradigm. ceo /ithaca. working with /rust on /ethereum. building /reth and /foundry. https://gakonst.com

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

Can you just use the JSON output directly? 

Or if you want human-readable, ethers/viem have methods to generate that from json, such as

Can you just use the JSON output directly? 

Or if you want human-readable, ethers/viem have methods to generate that from json, such as https://github.com/mds1/evm-diff/blob/47ce39d51ff478d7b5866df0059ad6164fe89b07/script/json-abi-to-viem-human-readable.ts#L8

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.