#DEV-22 build: core contracts (deploy, init, and configuration) #4
Conversation
This file contains 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
ryanycw
changed the title
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.
Summary
The purpose of this pull request is to reorganize the repository to maintain a consistent diamond contract style.
Details
With the current diamond standard fashion, the core diamond contract NonFungiblePositionVault is responsible for mapping functions. Submodules mapping and upgrade logic can be found in LibFunctionRouter, while all storage structure is located in LibAppStorage. Additionally, the function logic is in submodules/, and any shared functions between submodules are moved to libraries/, such as LibPostionManager.sol in src/libraries/.
Todo