chore(sequencer)!: update storage keys locations and values (ENG-898) #1616
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.
Summary
The storage keys for all components were moved from the top of
state_ext
modules into newstorage::keys
modules. The key values were updated to a consistent style.Background
We wanted the keys to be easy to find and to follow a consistent pattern in terms of their values and locations.
Changes
<COMPONENT>/storage/keys
./
._
as word separators.state_ext
modules for formatting keys were unified into a new structAddressPrefixer
incrate::storage
.Asset
functionality was moved fromcrate::storage_keys
tocrate::storage
.Testing
state_ext
modules are tested to ensure they are actually prefixes of the given keys.Breaking Changelist
Related Issues
Closes #1611.