-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add missing events to nomination pool extrinsics #7377
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
Conversation
Ank4n
left a comment
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.
Some nits but okay with this PR.
| /// A pool member's claim permission has been updated. | ||
| MemberClaimPermissionUpdated { member: T::AccountId, permission: ClaimPermission }, | ||
| /// A pool's metadata was updated. | ||
| MetadataUpdated { pool_id: PoolId, caller: T::AccountId }, |
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.
Is adding caller useful here? Nothing against it, just trying to understand the rationale. Same for other events.
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.
In the case of set_metadata, both the pool's root and its bouncer can make that call - this is to disambiguate which did it, in case the two roles are performed by different accounts.
The same goes for the other calls: nominate/chill can be called by the pool's root/nominator.
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
Found via open-web3-stack/polkadot-ecosystem-tests#165.
Closes #7370 .
Description
Some extrinsics from
pallet_nomination_poolswere not emitting events:set_configsset_claim_permissionset_metadatachillnominateIntegration
N/A
Review Notes
N/A