-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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(script
): mv ScriptSequence
to new crate
#9098
Conversation
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.
overall makes sense but would like us to avoid introducing duplicating types without a clear blocker for just resusing forge-script-sequence stuff
also would like us to check how many deps we'll add to foundry-cheatcodes if it would depend on new crate
script
): mv ScriptSequence
related type to new cratescript
): mv ScriptSequence
to new crate
Importing |
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.
nice, looking good, just a couple nits
* refac(`script`): extract script sequence and related types to new crate * replace MultiChainSequence in script crate * replace TransactionWithMetadata and AdditionalContract * replace ScriptSequence * replace all underlying ScriptSequence and related types * doc nits * add `ScriptTransactionBuilder` * remove `TxWithMetadata` * mv verify fns and use `ScriptSequence` directly * clippy
Motivation
Closes #9105
ScriptSequence
is the type that is written to broadcast files such asrun-latest.json
. It handles serialization.save()
and deserialization.load()
of the broadcast results.Now that we want to implement cheatcodes that make it easy to load broadcast results into a script (See: #4732). It is imperative to move these types to prevent cyclical deps.
Solution
forge-script-sequence
.forge-script
.@klkvr ptal