-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: Remove file I/O from deployment scripts #12015
base: develop
Are you sure you want to change the base?
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
@@ -18,15 +18,13 @@ import { BaseDeployIO } from "scripts/utils/BaseDeployIO.sol"; | |||
// complement the OP Stack Manager. The script architecture is a bit different than a standard forge | |||
// deployment script. | |||
// | |||
// There are three categories of users that are expected to interact with the scripts: | |||
// 1. End users that want to run live contract deployments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep the end users item, but just indicate they are expected to run the scripts via op-deployer, which also uses the go interface
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added here, 23fcc6c feel free to add more details if you have them to this. Otherwise, I can resolve and merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Goodbye file I/O, you will be missed 🫡
This pull request removes file I/O functionality from deployment scripts, simplifying the codebase and focusing on core deployment logic. Key changes include:
loadInputFile
andwriteOutputFile
methods from various input and output contracts.run
function that accepted file paths as arguments in deployment scripts.These changes streamline the deployment process, making it more suitable for direct programmatic use in Solidity and Go environments. The update maintains the existing core deployment logic while removing the complexity associated with file-based configurations.