2019-08-15 05:02:02 +00:00
|
|
|
use crate::commands::PerItemCommand;
|
Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
|
|
|
use crate::context::CommandRegistry;
|
2019-05-16 02:42:44 +00:00
|
|
|
use crate::prelude::*;
|
Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
|
|
|
use nu_errors::ShellError;
|
|
|
|
use nu_protocol::{CallInfo, ReturnSuccess, Scope, Signature, SyntaxShape, UntaggedValue, Value};
|
2019-07-23 22:22:11 +00:00
|
|
|
|
|
|
|
pub struct Where;
|
|
|
|
|
2019-08-14 17:02:39 +00:00
|
|
|
impl PerItemCommand for Where {
|
2019-07-23 22:22:11 +00:00
|
|
|
fn name(&self) -> &str {
|
|
|
|
"where"
|
|
|
|
}
|
2019-05-28 06:45:18 +00:00
|
|
|
|
Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
|
|
|
fn signature(&self) -> Signature {
|
2019-10-28 05:15:35 +00:00
|
|
|
Signature::build("where").required(
|
|
|
|
"condition",
|
|
|
|
SyntaxShape::Block,
|
|
|
|
"the condition that must match",
|
|
|
|
)
|
2019-08-29 22:52:32 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
fn usage(&self) -> &str {
|
|
|
|
"Filter table to match the condition."
|
2019-05-22 07:12:03 +00:00
|
|
|
}
|
2019-07-23 22:22:11 +00:00
|
|
|
|
2019-08-02 19:15:07 +00:00
|
|
|
fn run(
|
|
|
|
&self,
|
2019-08-15 05:02:02 +00:00
|
|
|
call_info: &CallInfo,
|
Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
|
|
|
_registry: &CommandRegistry,
|
2019-08-29 03:53:45 +00:00
|
|
|
_raw_args: &RawCommandArgs,
|
2019-11-21 14:33:14 +00:00
|
|
|
input: Value,
|
2019-08-24 19:36:19 +00:00
|
|
|
) -> Result<OutputStream, ShellError> {
|
2019-08-14 17:02:39 +00:00
|
|
|
let input_clone = input.clone();
|
2019-08-15 05:02:02 +00:00
|
|
|
let condition = call_info.args.expect_nth(0)?;
|
2019-08-24 19:36:19 +00:00
|
|
|
let stream = match condition {
|
2019-11-21 14:33:14 +00:00
|
|
|
Value {
|
|
|
|
value: UntaggedValue::Block(block),
|
2019-08-30 17:29:04 +00:00
|
|
|
..
|
2019-08-14 17:02:39 +00:00
|
|
|
} => {
|
Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 02:30:48 +00:00
|
|
|
let result = block.invoke(&Scope::new(input_clone.clone()));
|
2019-08-14 17:02:39 +00:00
|
|
|
match result {
|
|
|
|
Ok(v) => {
|
|
|
|
if v.is_true() {
|
2019-08-24 19:36:19 +00:00
|
|
|
VecDeque::from(vec![Ok(ReturnSuccess::Value(input_clone))])
|
2019-08-14 17:02:39 +00:00
|
|
|
} else {
|
2019-08-24 19:36:19 +00:00
|
|
|
VecDeque::new()
|
2019-08-14 17:02:39 +00:00
|
|
|
}
|
|
|
|
}
|
2019-09-11 14:36:50 +00:00
|
|
|
Err(e) => return Err(e),
|
2019-08-14 17:02:39 +00:00
|
|
|
}
|
|
|
|
}
|
2019-11-21 14:33:14 +00:00
|
|
|
Value { tag, .. } => {
|
2019-08-24 19:36:19 +00:00
|
|
|
return Err(ShellError::labeled_error(
|
|
|
|
"Expected a condition",
|
|
|
|
"where needs a condition",
|
2019-10-13 04:12:43 +00:00
|
|
|
tag,
|
2019-08-24 19:36:19 +00:00
|
|
|
))
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
Ok(stream.to_output_stream())
|
2019-08-02 19:15:07 +00:00
|
|
|
}
|
|
|
|
}
|