forked from extern/nushell
95b78eee25
# Description
The meaning of the word usage is specific to describing how a command
function is *used* and not a synonym for general description. Usage can
be used to describe the SYNOPSIS or EXAMPLES sections of a man page
where the permitted argument combinations are shown or example *uses*
are given.
Let's not confuse people and call it what it is a description.
Our `help` command already creates its own *Usage* section based on the
available arguments and doesn't refer to the description with usage.
# User-Facing Changes
`help commands` and `scope commands` will now use `description` or
`extra_description`
`usage`-> `description`
`extra_usage` -> `extra_description`
Breaking change in the plugin protocol:
In the signature record communicated with the engine.
`usage`-> `description`
`extra_usage` -> `extra_description`
The same rename also takes place for the methods on
`SimplePluginCommand` and `PluginCommand`
# Tests + Formatting
- Updated plugin protocol specific changes
# After Submitting
- [ ] update plugin protocol doc
48 lines
1.4 KiB
Rust
48 lines
1.4 KiB
Rust
use nu_engine::{command_prelude::*, get_full_help};
|
|
|
|
#[derive(Clone)]
|
|
pub struct PathCommand;
|
|
|
|
impl Command for PathCommand {
|
|
fn name(&self) -> &str {
|
|
"path"
|
|
}
|
|
|
|
fn signature(&self) -> Signature {
|
|
Signature::build("path")
|
|
.input_output_types(vec![(Type::Nothing, Type::String)])
|
|
.category(Category::Path)
|
|
}
|
|
|
|
fn description(&self) -> &str {
|
|
"Explore and manipulate paths."
|
|
}
|
|
|
|
fn extra_description(&self) -> &str {
|
|
r#"You must use one of the following subcommands. Using this command as-is will only produce this help message.
|
|
|
|
There are three ways to represent a path:
|
|
|
|
* As a path literal, e.g., '/home/viking/spam.txt'
|
|
* As a structured path: a table with 'parent', 'stem', and 'extension' (and
|
|
* 'prefix' on Windows) columns. This format is produced by the 'path parse'
|
|
subcommand.
|
|
* As a list of path parts, e.g., '[ / home viking spam.txt ]'. Splitting into
|
|
parts is done by the `path split` command.
|
|
|
|
All subcommands accept all three variants as an input. Furthermore, the 'path
|
|
join' subcommand can be used to join the structured path or path parts back into
|
|
the path literal."#
|
|
}
|
|
|
|
fn run(
|
|
&self,
|
|
engine_state: &EngineState,
|
|
stack: &mut Stack,
|
|
call: &Call,
|
|
_input: PipelineData,
|
|
) -> Result<PipelineData, ShellError> {
|
|
Ok(Value::string(get_full_help(self, engine_state, stack), call.head).into_pipeline_data())
|
|
}
|
|
}
|