mirror of
https://github.com/nushell/nushell.git
synced 2025-05-10 01:42:57 +00:00
01d30a416b
# Description
This is something that was discussed in the core team meeting last
Wednesday. @ayax79 is building `nu-plugin-polars` with all of the
dataframe commands into a plugin, and there are a lot of them, so it
would help to make the API more similar. At the same time, I think the
`Command` API is just better anyway. I don't think the difference is
justified, and the types for core commands have the benefit of requiring
less `.into()` because they often don't own their data
- Broke `signature()` up into `name()`, `usage()`, `extra_usage()`,
`search_terms()`, `examples()`
- `signature()` returns `nu_protocol::Signature`
- `examples()` returns `Vec<nu_protocol::Example>`
- `PluginSignature` and `PluginExample` no longer need to be used by
plugin developers
# User-Facing Changes
Breaking API for plugins yet again 😄
34 lines
902 B
Rust
34 lines
902 B
Rust
use nu_plugin::{Plugin, PluginCommand};
|
|
|
|
mod commands;
|
|
mod example;
|
|
|
|
pub use commands::*;
|
|
pub use example::ExamplePlugin;
|
|
|
|
impl Plugin for ExamplePlugin {
|
|
fn commands(&self) -> Vec<Box<dyn PluginCommand<Plugin = Self>>> {
|
|
// This is a list of all of the commands you would like Nu to register when your plugin is
|
|
// loaded.
|
|
//
|
|
// If it doesn't appear on this list, it won't be added.
|
|
vec![
|
|
Box::new(Main),
|
|
// Basic demos
|
|
Box::new(One),
|
|
Box::new(Two),
|
|
Box::new(Three),
|
|
// Engine interface demos
|
|
Box::new(Config),
|
|
Box::new(Env),
|
|
Box::new(DisableGc),
|
|
// Stream demos
|
|
Box::new(CollectExternal),
|
|
Box::new(ForEach),
|
|
Box::new(Generate),
|
|
Box::new(Seq),
|
|
Box::new(Sum),
|
|
]
|
|
}
|
|
}
|