mirror of
https://github.com/nushell/nushell.git
synced 2025-05-23 08:01:18 +00:00
# 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
63 lines
1.8 KiB
Rust
63 lines
1.8 KiB
Rust
use nu_plugin::{EngineInterface, EvaluatedCall, SimplePluginCommand};
|
|
use nu_protocol::{Category, IntoValue, LabeledError, Signature, SyntaxShape, Value};
|
|
|
|
use crate::ExamplePlugin;
|
|
|
|
pub struct Two;
|
|
|
|
impl SimplePluginCommand for Two {
|
|
type Plugin = ExamplePlugin;
|
|
|
|
fn name(&self) -> &str {
|
|
"example two"
|
|
}
|
|
|
|
fn description(&self) -> &str {
|
|
"Plugin test example 2. Returns list of records"
|
|
}
|
|
|
|
fn signature(&self) -> Signature {
|
|
// The signature defines the usage of the command inside Nu, and also automatically
|
|
// generates its help page.
|
|
Signature::build(self.name())
|
|
.required("a", SyntaxShape::Int, "required integer value")
|
|
.required("b", SyntaxShape::String, "required string value")
|
|
.switch("flag", "a flag for the signature", Some('f'))
|
|
.optional("opt", SyntaxShape::Int, "Optional number")
|
|
.named("named", SyntaxShape::String, "named string", Some('n'))
|
|
.rest("rest", SyntaxShape::String, "rest value string")
|
|
.category(Category::Experimental)
|
|
}
|
|
|
|
fn run(
|
|
&self,
|
|
plugin: &ExamplePlugin,
|
|
_engine: &EngineInterface,
|
|
call: &EvaluatedCall,
|
|
input: &Value,
|
|
) -> Result<Value, LabeledError> {
|
|
plugin.print_values(2, call, input)?;
|
|
|
|
// Use the IntoValue derive macro and trait to easily design output data.
|
|
#[derive(IntoValue)]
|
|
struct Output {
|
|
one: i64,
|
|
two: i64,
|
|
three: i64,
|
|
}
|
|
|
|
let vals = (0..10i64)
|
|
.map(|i| {
|
|
Output {
|
|
one: i,
|
|
two: 2 * i,
|
|
three: 3 * i,
|
|
}
|
|
.into_value(call.head)
|
|
})
|
|
.collect();
|
|
|
|
Ok(Value::list(vals, call.head))
|
|
}
|
|
}
|