This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Allow renaming storage item prefixes #9016
Merged
Merged
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
507c312
Implement parsing for #[pallet::storage_name] on storage items
KiChjang a1e75b2
Rename storage prefix when a #[pallet::storage_name] is supplied
KiChjang c87e4d0
Fix test_storage_info
KiChjang 9ea8251
Rename storage_name to storage_prefix
KiChjang 9d6a9e8
Check for duplicates when renaming storage prefixes
KiChjang 34fbf92
Allow only string literals for storage_prefix renames
KiChjang 5277f7d
Merge remote-tracking branch 'origin/master' into kckyeung/storage-pr…
KiChjang fc49baf
Use proper spans for attribute errors
KiChjang b8895a2
Check for valid identifiers when parsing storage prefix renames
KiChjang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
18 changes: 18 additions & 0 deletions
18
frame/support/test/tests/pallet_ui/storage_invalid_rename_value.rs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
#[frame_support::pallet] | ||
mod pallet { | ||
use frame_support::pallet_prelude::Hooks; | ||
use frame_system::pallet_prelude::BlockNumberFor; | ||
|
||
#[pallet::config] | ||
pub trait Config: frame_system::Config {} | ||
|
||
#[pallet::pallet] | ||
pub struct Pallet<T>(core::marker::PhantomData<T>); | ||
|
||
#[pallet::storage] | ||
#[pallet::storage_prefix = "pub"] | ||
type Foo<T> = StorageValue<_, u8>; | ||
} | ||
|
||
fn main() { | ||
} |
5 changes: 5 additions & 0 deletions
5
frame/support/test/tests/pallet_ui/storage_invalid_rename_value.stderr
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
error: `pub` is not a valid identifier | ||
--> $DIR/storage_invalid_rename_value.rs:13:29 | ||
| | ||
13 | #[pallet::storage_prefix = "pub"] | ||
| ^^^^^ |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
just a sidenote, now that we don't use renamed_prefix as ident, we don't need to force it to be a valid ident anymore AFAICT
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.
Do we want that though? This would mean that it's possible to create storage prefixes that does not follow Rust identifier naming conventions. I guess that kind of makes sense, but something tells me that it's a bad idea, like there might be a footgun lying there somewhere if we're too permissive...
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.
ok, we can leverage the constraint when wanted.