-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature/in 121 #37
Feature/in 121 #37
Conversation
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.
Alright this probably looks like a wall of changes but most of it is arround the switch to T::ProcessVersion
. This is actually really close on the implmentation side, so well done! Couple of additional points:
- Please rebase or merge in main. There's currently some churn from the
cargo fmt
- Tests need writing still, but I think you know that. Just a reminder
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.
Tests are looking good. Many points from the first review still remain but we're headed in the right direction. Few comments to look at
…pdate_version function.
…in regards to the requersted changes.
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.
You've done really well to pick this up and make something meaningful. Well done!
I don't have much to comment regarding the logic and types/structs. I noticed there are a lot of comments, some seem anecdotal whereas some seem more formal, also the formal comments are not always consistently applied i.e. method and variable documentation.
Is there a standard for code comment documentation in rust/substrate?
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.
Really close couple of minor changes. Also need to consider the following:
- bump pallet version
- bump runtime version (including the chain runtime version to match in the runtime lib.rs)
- bump node version
}; | ||
} | ||
|
||
pub fn set_disabled(id: &T::ProcessIdentifier, version: &T::ProcessVersion) -> Result<bool, Error<T>> { |
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.
Sorry I didn't comment all of these but it's the same thing with unit instead of bool if you want to
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.
🤦 sorry been rushing a little i guess and did not see that this repeats
@@ -4,7 +4,7 @@ edition = '2018' | |||
license = 'Apache-2.0' | |||
repository = 'https://github.com/digicatapult/vitalam-node/' | |||
name = 'vitalam-node-runtime' | |||
version = '2.2.0' | |||
version = '2.2.1' |
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.
This version needs refencing in https://github.com/digicatapult/vitalam-node/blob/5ae336055621e016b1a1925605a67f01ae7018c0/runtime/src/lib.rs#L96
Sorry to be the README troll, but this pallet has reached a point where it should have a section in the README? Like the sections for other pallets detailing their storage + extrinsics |
@jonmattgray - was actually thinking about this earlier in the morning, will add a README file |
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.
What
Version
.create process
method anddisable_process
Test coverage
TODO