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: Upgrade to polkadot v0.9.37 #61

Merged
merged 1 commit into from
Feb 16, 2023
Merged

feat: Upgrade to polkadot v0.9.37 #61

merged 1 commit into from
Feb 16, 2023

Conversation

tolak
Copy link
Collaborator

@tolak tolak commented Feb 15, 2023

@tolak tolak requested a review from freddyli7 February 15, 2023 12:36
Copy link
Contributor

@freddyli7 freddyli7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! just one question

@@ -243,6 +243,7 @@ pub mod pallet {
{
/// Pause bridge, this would lead to bridge transfer failure before it being unpaused.
#[pallet::weight(195_000_000)]
#[pallet::call_index(0)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see now we have this call_index annotation in v0.9.37, is it a mandatory annotation for each extrinsic now from this version? I remember that when we worked on the access grant feature, we used to define a number for each extrinsic, then we decided to use a more readable and maintainable name, is this annotation related to that number?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is used to identify the extrinsic. We were planning to use the index but we thought the index may change. I have short discuss with parity team when they implement this function, suggested to add name too but they don't think runtime should care about the name, see here

@tolak tolak merged commit cbe3f83 into main Feb 16, 2023
@tolak tolak deleted the polkadot-0.9.37 branch February 16, 2023 05:44
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