-
Notifications
You must be signed in to change notification settings - Fork 347
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
fix(cli): Update warp apply to apply changes in single command #4672
base: main
Are you sure you want to change the base?
Conversation
…D extends in a single call
🦋 Changeset detectedLatest commit: e4be6d8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
mostly lgtm although it would intuitively make more sense to me if we did
contracts = contracts.extend()
contracts.update()
const mergedRouters = mergeAllRouters( | ||
multiProvider, | ||
existingConfigs, | ||
newDeployedContracts, | ||
warpCoreConfigByChain, | ||
); |
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.
can we just join the newDeployedContracts with the existing deployed and pass that to the update step?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4672 +/- ##
=======================================
Coverage 73.85% 73.85%
=======================================
Files 100 100
Lines 1423 1423
Branches 181 181
=======================================
Hits 1051 1051
Misses 351 351
Partials 21 21
|
Description
This PR fixes a limitation in
warp apply
such that it can only extend or update an existing warp route. This means that for configs with both changes requirewarp apply
to be called multiple times. An example is when Renzo deploys to new chain, and it needs to update the existing ISMs.Related issues
Backward compatibility
Yes
Testing
Manual/Unit Tests