-
Notifications
You must be signed in to change notification settings - Fork 680
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
Explain usage of <T: Config>
in FRAME storage + Update parachain pallet template
#4941
Conversation
Also we can't have the banner printed all the time, because it leads to printing malformed chain specs.
+ small fixes
+ addressing some nits
<T: Config>
in FRAME storage + Update parachain pallet template
@kianenigma Command |
@@ -755,7 +755,13 @@ pub mod pallet { | |||
// We ignore this error as it just means the amount we're trying to deposit is | |||
// dust and the beneficiary account doesn't exist. | |||
.or_else( | |||
|e| if e == TokenError::CannotCreate.into() { Ok(()) } else { Err(e) }, | |||
|e| { | |||
if e == TokenError::CannotCreate.into() { |
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.
New formatter 🙈 ?
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.
ah shit :D
…aritytech/polkadot-sdk into kiz-update-tempalates-and-t-in-storage
bot fmt |
"$PIPELINE_SCRIPTS_DIR/commands/fmt/fmt.sh" was queued. Comment |
@kianenigma Command
|
@@ -1,4 +1,7 @@ | |||
//! A shell pallet built with [`frame`]. | |||
//! | |||
//! To get started with this pallet, try implementing the guide in | |||
//! <https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/guides/your_first_pallet/index.html> |
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.
//! <https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/guides/your_first_pallet/index.html> | |
//! <https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/guides/your_first_pallet/index.html>. |
@@ -25,10 +25,13 @@ frame-benchmarking = { optional = true, workspace = true } | |||
frame-support = { workspace = true } | |||
frame-system = { workspace = true } | |||
|
|||
# primitive deps | |||
sp-runtime = { workspace = true } | |||
sp-std = { workspace = true } |
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.
Was sp-std
be proposed to soft deprecate?
#2101
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.
hmm I see, a mistake indeed. Would you like to open a PR that reverts this + added a deprecation warning to sp-std, preventing this from happening?
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 think I can make a following PR to remove the usage of sp-std
here.
I don't know how to warn deprecation for a crate...
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.
#5001
Following PR is here
Following PR for #4941 that removes usage of `sp-std` on templates `sp-std` crate was proposed to deprecate on #2101 @kianenigma --------- Co-authored-by: Kian Paimani <[email protected]>
…llet template (paritytech#4941) Explains one of the annoying parts of FRAME storage that we have seen multiple times in PBA everyone gets stuck on. I have not updated the other two templates for now, and only reflected it in the parachain template. That can happen in a follow-up. - [x] Update possible answers in SE about the same topic. --------- Co-authored-by: Serban Iorga <[email protected]> Co-authored-by: command-bot <>
Following PR for paritytech#4941 that removes usage of `sp-std` on templates `sp-std` crate was proposed to deprecate on paritytech#2101 @kianenigma --------- Co-authored-by: Kian Paimani <[email protected]>
* master: (120 commits) network/tx: Ban peers with tx that fail to decode (#5002) Try State Hook for Bounties (#4563) [statement-distribution] Add metrics for distributed statements in V2 (#4554) added sync command (#4818) Bridges V2 refactoring backport and `pallet_bridge_messages` simplifications (#4935) xcm-executor: Improve logging (#4996) Remove usage of `sp-std` on templates (#5001) fixed cmd bot commenting not working (#5000) Explain usage of `<T: Config>` in FRAME storage + Update parachain pallet template (#4941) Expose metadata-hash feature from polkadot crate (#4886) Add `MAX_INSTRUCTIONS_TO_DECODE` to XCMv2 (#4978) add notices to the implementer's guide docs that changed for elastic scaling (#4983) `polkadot-parachain` simplifications and deduplications (#4916) Update Templates README docs (#4980) allow clear_origin in safe xcm builder (#4777) litep2p/peerstore: Fix bump last updated time (#4971) Make `tracing::log` work in the runtime (#4863) sp-core: Improve docs generated by `generate_feature_enabled_macro` (#4968) [Backport] Version bumps and prdocs reordering from 1.14.0 (#4955) Assets: can_decrease/increase for destroying asset is not successful (#3286) ...
…llet template (paritytech#4941) Explains one of the annoying parts of FRAME storage that we have seen multiple times in PBA everyone gets stuck on. I have not updated the other two templates for now, and only reflected it in the parachain template. That can happen in a follow-up. - [x] Update possible answers in SE about the same topic. --------- Co-authored-by: Serban Iorga <[email protected]> Co-authored-by: command-bot <>
Following PR for paritytech#4941 that removes usage of `sp-std` on templates `sp-std` crate was proposed to deprecate on paritytech#2101 @kianenigma --------- Co-authored-by: Kian Paimani <[email protected]>
Explains one of the annoying parts of FRAME storage that we have seen multiple times in PBA everyone gets stuck on.
I have not updated the other two templates for now, and only reflected it in the parachain template. That can happen in a follow-up.