Enable generating typescript ABIs for multiple Foundry deploy scripts #896
MattPereira
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
Hey @MattPereira Could you check if what Shiv did for the create-eth foundry template could work? Maybe we can take some ideas from there and put it on SE-2 (where foundry is going to be the default) |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current foundry version of SE-2 is only capable of exporting deployment info for a single deploy script because it depends on this line where a specific file name is declared
Additionally, this logic overwrites the entire contents of the
nextjs/contracts/deployedContracts.ts
file so a viable solution would have to involve appending deployed contracts to that file but only if the deployment comes from a different script, otherwise you would want to overwrite the contract name keys because it would be newer version of same contracts ( if that makes sense 😅 )For example, I'm hoping to be able to
exportDeployments()
from all of the numbered deploy scripts for scaffold balancer. The solution of deploying all the pool factories in the00_DeploySetup.s.sol
is viable for now, but will grow increasingly messy as more example pool and hooks contracts are added to the build. Would prefer to be able to encapsulate all the contracts related to eachother in each script while maintaining all the scaffold integrations on the frontend because I'm listening for pool created events emitted by the factory contract in order to offer buttons for the pool explorer pageBeta Was this translation helpful? Give feedback.
All reactions