mirror of
https://github.com/nushell/nushell.git
synced 2025-05-03 09:34:27 +02:00
c747ec75c9
# Description
When implementing a `Command`, one must also import all the types
present in the function signatures for `Command`. This makes it so that
we often import the same set of types in each command implementation
file. E.g., something like this:
```rust
use nu_protocol::ast::Call;
use nu_protocol::engine::{Command, EngineState, Stack};
use nu_protocol::{
record, Category, Example, IntoInterruptiblePipelineData, IntoPipelineData, PipelineData,
ShellError, Signature, Span, Type, Value,
};
```
This PR adds the `nu_engine::command_prelude` module which contains the
necessary and commonly used types to implement a `Command`:
```rust
// command_prelude.rs
pub use crate::CallExt;
pub use nu_protocol::{
ast::{Call, CellPath},
engine::{Command, EngineState, Stack},
record, Category, Example, IntoInterruptiblePipelineData, IntoPipelineData, IntoSpanned,
PipelineData, Record, ShellError, Signature, Span, Spanned, SyntaxShape, Type, Value,
};
```
This should reduce the boilerplate needed to implement a command and
also gives us a place to track the breadth of the `Command` API. I tried
to be conservative with what went into the prelude modules, since it
might be hard/annoying to remove items from the prelude in the future.
Let me know if something should be included or excluded.
21 lines
489 B
Rust
21 lines
489 B
Rust
mod call_ext;
|
|
pub mod column;
|
|
pub mod command_prelude;
|
|
pub mod documentation;
|
|
pub mod env;
|
|
mod eval;
|
|
mod eval_helpers;
|
|
mod glob_from;
|
|
pub mod scope;
|
|
|
|
pub use call_ext::CallExt;
|
|
pub use column::get_columns;
|
|
pub use documentation::get_full_help;
|
|
pub use env::*;
|
|
pub use eval::{
|
|
eval_block, eval_block_with_early_return, eval_call, eval_expression,
|
|
eval_expression_with_input, eval_subexpression, eval_variable, redirect_env,
|
|
};
|
|
pub use eval_helpers::*;
|
|
pub use glob_from::glob_from;
|