Rename --blueprint-input to --in
The context is indeed sufficient as pointed by @nemo83; no need to make the cli needlessly verbose.
This commit is contained in:
@@ -26,9 +26,10 @@ pub struct Args {
|
||||
/// `plutus.json`), or use the `cbor.serialise` function from the Aiken standard library.
|
||||
parameter: Option<String>,
|
||||
|
||||
/// Path to a blueprint file to be used as input.
|
||||
#[clap(short = 'b', long, value_parser)]
|
||||
blueprint_input: Option<PathBuf>,
|
||||
/// Optional path to the blueprint file to be used as input. Default to 'plutus.json' when
|
||||
/// omitted.
|
||||
#[clap(short, long = "in", value_parser)]
|
||||
input: Option<PathBuf>,
|
||||
|
||||
/// Output file. Optional, print on stdout when omitted.
|
||||
#[clap(short, long)]
|
||||
@@ -46,7 +47,7 @@ pub struct Args {
|
||||
pub fn exec(
|
||||
Args {
|
||||
parameter,
|
||||
blueprint_input,
|
||||
input,
|
||||
out,
|
||||
module,
|
||||
validator,
|
||||
@@ -108,7 +109,7 @@ pub fn exec(
|
||||
})
|
||||
}
|
||||
|
||||
None => p.construct_parameter_incrementally(title, &blueprint_input, ask_schema)?,
|
||||
None => p.construct_parameter_incrementally(title, &input, ask_schema)?,
|
||||
};
|
||||
|
||||
eprintln!(
|
||||
|
||||
Reference in New Issue
Block a user