-
Notifications
You must be signed in to change notification settings - Fork 619
Marketplace implementation addresses #5822
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
size-limit report 📦
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5822 +/- ##
==========================================
+ Coverage 53.34% 53.55% +0.20%
==========================================
Files 1101 1102 +1
Lines 59124 59163 +39
Branches 4825 4837 +12
==========================================
+ Hits 31541 31685 +144
+ Misses 26864 26760 -104
+ Partials 719 718 -1
*This pull request uses carry forward flags. Click here to find out more.
|
|
Merge activity
|
TOOL-2814
## Problem solved
Short description of the bug fixed or feature added
<!-- start pr-codex -->
---
## PR-Codex overview
This PR introduces support for `ZkSync` chains by adding implementations for contracts and adjusting methods to handle `ZkSync` specific logic, including fetching default constructor parameters and deploying contracts.
### Detailed summary
- Added `ZKSYNC_IMPLEMENTATIONS` and `ZKSYNC_WETH` records for various `ZkSync` chains.
- Updated `CustomContractForm` to handle `MarketplaceV3` differently for `ZkSync` chains.
- Introduced a test for retrieving default constructor parameters for `ZkSync`.
- Modified `getAllDefaultConstructorParamsForImplementation` to return `nativeTokenWrapper` for `ZkSync`.
- Updated contract deployment logic in `bootstrap.ts` to use `ZkSync` implementations.
- Added a test case for saving implementations for `ZkSync` chains.
- Enhanced contract fetching logic in `getOrDeployInfraContract` for `WETH9` on `ZkSync`.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
a3ff229 to
3718020
Compare
TOOL-2813
Problem solved
Short description of the bug fixed or feature added
PR-Codex overview
This PR introduces support for
ZkSyncchains by defining implementations and WETH addresses, updating contract deployment logic, and adding tests to ensure correct behavior for these chains.Detailed summary
ZKSYNC_IMPLEMENTATIONSandZKSYNC_WETHforZkSyncchain configurations.CustomContractFormto handleMarketplaceV3forZkSyncchains.getAllDefaultConstructorParamsForImplementationto returnWETHforZkSync.ZkSync.getOrDeployInfraForPublishedContractto utilizeZkSyncimplementations.getOrDeployInfraContractto returnWETHforZkSyncchains.