fix: [QSP-5] Missing _disableInitializers for some Contracts #265
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
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.
What does this PR introduce?
In this PR we remove Init contracts from LSP7 and LSP8 contract extensions and in exchange use the InitAbstract in the presets.
LSP4DigitalAssetMetadataInit -> LSP4DigitalAssetMetadataInitAbstract
LSP7CappedSupplyInit -> LSP7CappedSupplyInitAbstract
LSP8CappedSupplyInit -> LSP8CappedSupplyInitAbstract
LSP8CompatibleERC721Init -> LSP8CompatibleERC721InitAbstract
LSP7CompatibleERC20Init -> LSP7CompatibleERC20InitAbstract
Also we add _disableInitializers in 2 contracts from LSP7 and LSP8 contract presets:
LSP7CompatibleERC20MintableInit
LSP8CompatibleERC721MintableInit