Skip to content
Snippets Groups Projects
Commit fad92253 authored by Seemant Aggarwal's avatar Seemant Aggarwal
Browse files

cargo +nightly fmt && add prdoc

parent 568e21e9
Branches
No related merge requests found
Pipeline #517449 waiting for manual action with stages
in 9 minutes and 34 seconds
title: 'Adding command export_chain_spec for polkadot-omni node'
doc:
- audience: Runtime Dev
description: |
Idea is introduce a function export-chain-spec that does the chain-spec exporting. build-spec will work as before, but have a deprecation message on usage.
For now, this new command will focus on the ability to take the chain-specs embedded in the node and "exports" them to a json file
We will not include the addition of boot node functionality, that the build-spec command has right now into the new command, if along the process, we decide otherwise, we can include it
Part of this PR will also be to display the message the build-spec will soon be on deprecation pat
crates:
- name: polkadot-omni-node-lib
bump: major
- name: sc-cli
bump: patch
......@@ -24,8 +24,7 @@ use std::{
path::PathBuf,
};
use crate::error::{Result};
use crate::SharedParams;
use crate::{error::Result, SharedParams};
/// Export a chain-spec to a JSON file in plain or in raw storage format.
///
......@@ -43,18 +42,17 @@ use crate::SharedParams;
#[derive(Debug, Clone, Parser)]
pub struct ExportChainSpecCmd {
/// The chain spec identifier to export.
#[allow(missing_docs)]
#[clap(flatten)]
pub shared_params: SharedParams,
#[allow(missing_docs)]
#[clap(flatten)]
pub shared_params: SharedParams,
/// `chain-spec` JSON file path. If omitted, prints to stdout.
/// `chain-spec` JSON file path. If omitted, prints to stdout.
#[arg(long)]
pub output: Option<PathBuf>,
/// Export in raw genesis storage format.
#[arg(long)]
pub raw: bool,
}
impl ExportChainSpecCmd {
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment