-
Notifications
You must be signed in to change notification settings - Fork 3
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
added fields AnnouncementSigner and CommunityRules to CommunityMetadata #336
Conversation
caveat: the rpc reads CommunityMetadata.name and will break if this can't be decoded. therefore we need state migration (manual or automated) |
while parity tends to do single-step migrations, I believe this case here is much simpler to understand and comes with less boilerplate if we allow migration from v0->v2 and v1->v2 in a single move. v0->v1 was a noop with bound checks only |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, only some minor comments. I like that we are no longer afraid of storage migrations. XD
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All questions satisfied! :) Looks good to me
closes #334
closes #335
breaking change!
includes a storage migration to v2 for the communities pallet