Skip to content
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

[BREAKING] chore!: multisig pallet name should not be CamelCase #557

Merged
merged 1 commit into from
Apr 8, 2022

Conversation

gregdhill
Copy link
Member

Signed-off-by: Gregory Hill gregorydhill@outlook.com

Signed-off-by: Gregory Hill <gregorydhill@outlook.com>
@gregdhill gregdhill force-pushed the chore/rename-multisig branch from 71ed1a7 to 2d1c265 Compare March 30, 2022 10:53
@sander2
Copy link
Member

sander2 commented Mar 31, 2022

Storage value keys are derived from the pallet name (+ field name), so did you check that there are no storage items we need to migrate?

@gregdhill
Copy link
Member Author

gregdhill commented Apr 8, 2022

Storage value keys are derived from the pallet name (+ field name), so did you check that there are no storage items we need to migrate?

There are two storage items (Multisigs and Calls) both are cleared here on execution. So providing that there are no ongoing calls we should be okay to change the pallet name without a migration.

Edit: Both storage maps are currently empty on Kintsugi.

@sander2 sander2 changed the title chore: multisig pallet name should not be CamelCase [BREAKING] chore!: multisig pallet name should not be CamelCase Apr 8, 2022
@sander2 sander2 merged commit 46677dc into interlay:master Apr 8, 2022
@gregdhill gregdhill deleted the chore/rename-multisig branch April 8, 2022 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants