Add ColonyExtensionMeta #982
Merged
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
kronosapiens
force-pushed
the
maint/meta-extensions
branch
from
37be3bb to
76be92b
Compare
|
Noting that we would like to add some (let's say 32) storage slot placeholders in case we need to add new storage to this base class down the road. |
kronosapiens
force-pushed
the
maint/meta-extensions
branch
from
76be92b to
826ef79
Compare
kronosapiens
force-pushed
the
maint/meta-extensions
branch
2 times, most recently
from
ae9766d to
25ed4a6
Compare
kronosapiens
force-pushed
the
maint/meta-extensions
branch
from
25ed4a6 to
2f61a81
Compare
area
approved these changes
Oct 14, 2021
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.
Closes #977
Add the
ColonyExtensionMetabase class for extensions, which provides meta transaction functionality as per #962.Exiting extensions continue to inherit from
ColonyExtensionfor storage alignment reasons (and implement meta transaction functionality in a one-off basis), but new extensions should all use this new base class.