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

feat: add pallet-identity #556

Merged
merged 1 commit into from Apr 13, 2022
Merged

Conversation

gregdhill
Copy link
Member

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

@sander2
Copy link
Member

sander2 commented Mar 31, 2022

LGTM, but should this be marked breaking? Tbh I am not sure. It would break clients for sure because of unrecognized events, but we need metadata update after spec-version change anyway.. Should we rethink what we mark as breaking?

Signed-off-by: Gregory Hill <gregorydhill@outlook.com>
@gregdhill
Copy link
Member Author

Tbh I'm not sure, though I think we do that to adjust the numbering of pallets in our runtime so entries can be grouped more easily. See for example the Acala runtime where groups start at multiples of 10.

@nud3l
Copy link
Member

nud3l commented Apr 13, 2022

I'd be happy to merge this pending the comments above - I guess the grouping should possibly happen in a different PR though?

@sander2 sander2 merged commit 6266a64 into interlay:master Apr 13, 2022
@gregdhill gregdhill deleted the feat/pallet-identity branch April 13, 2022 14:10
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.

None yet

3 participants