refactor: create L1, L2, common folders #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 14280619317Details
💛 - Coveralls |
|
Does rename "L1/L1EthRegistry" to "L1/EthRegistry" cause name collision with "L2/EthRegistry"? If not, then it should just be "L1/EthRegistry". |
|
L1/L1EjectionController can just be called as L1/EjectionController |
Arachnid
approved these changes
Apr 1, 2025
…ucture-namechain-directory
|
@makoto I think filenames should match the contract names to avoid any confusion, so will keep them as they are. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.