-
Notifications
You must be signed in to change notification settings - Fork 115
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
[Nara] Add freeze pallet extrinsic to CRT pallet #4922
Conversation
@mnaamani can you please review? |
b4faf62
to
6061631
Compare
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.
I have reviewed the companion issue. But the implementation presented here is different from what's prescribed. Am I missing something?
Also it's still possible for a creator issue_token
, because there is not frozen-pallet check. Is this desired?
What follows below are minor suggestions
@ignazio-bovo thanks for the review 👍 Regarding |
@ignazio-bovo FYI the proposal part will be submitted in another PR |
3e2eaa4
to
5c7a021
Compare
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.
LGTM
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.
Great contribution, just left some change requests and general comments on use of assert_noop and unit tests.
runtime-modules/content/src/tests/creator_tokens/finalize_creator_token_sale.rs
Outdated
Show resolved
Hide resolved
runtime-modules/content/src/tests/creator_tokens/claim_patronage_credit.rs
Show resolved
Hide resolved
e34cb8f
to
6cf3c1b
Compare
6cf3c1b
to
affb1a1
Compare
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.
Runtime changes looks good.
Just a general comment. It is generally not recommended to force push changes after a PR is opened and reviews are going on. It will make it harder to do followup reviews as reviewer cannot review new changes and would have to look at the PR as whole again.
As a final step when we make runtime changes is to update the types package.
To do this build the node, and run it with joystream-node --dev
then run yarn update-chain-metadata
This produces the chain-metadata.json file at the root.
Then run build script for types package:
yarn workspace @joystream/types build
commit changes:
types/src/augment/*
chain-metadata.json
query-node/chain-metadata/2002.json
I apologize for the force push, I wanted to avoid having too many commits for the same feature going to the "master" branch. I will avoid it in the future. I committed the types packages now, @mnaamani please review again |
Implements the freeze part of #4897
┆Issue is synchronized with this Asana task by Unito