Elevating pallet-slots
to an Independent Crate
#3911
Draft
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.
Description
This PR separates
pallet-slots
into its own crate while keeping the refactor transparent to the code outsidepolkadot-runtime-common
. By re-exporting the pallet inpolkadot-runtime-common
, external references remain unchanged, preserving backward compatibility and minimizing impact on the wider Polkadot codebase.Changes Summary:
pallet-slots
to a standalone crate, including a dedicatedCargo.toml
for dependencies and configurations.polkadot-runtime-common
: To maintain existing code paths,pallet-slots
is re-exported inpolkadot-runtime-common
, making the refactor invisible to external users.Cargo.toml
inpolkadot-runtime-common
and top-level workspace to reflect the new crate path forpallet-slots
.This approach enhances modularity without requiring any changes from the rest of the Polkadot codebase.