2022-11-01 11:40:11 +00:00
|
|
|
use crate::input_handler::{operate, CellPathOnlyArgs};
|
2022-07-04 10:51:07 +00:00
|
|
|
use nu_engine::CallExt;
|
|
|
|
use nu_protocol::ast::Call;
|
|
|
|
use nu_protocol::ast::CellPath;
|
|
|
|
use nu_protocol::engine::{Command, EngineState, Stack};
|
|
|
|
use nu_protocol::Category;
|
2022-11-09 21:55:05 +00:00
|
|
|
use nu_protocol::{Example, PipelineData, ShellError, Signature, Span, SyntaxShape, Type, Value};
|
2022-07-04 10:51:07 +00:00
|
|
|
|
|
|
|
#[derive(Clone)]
|
|
|
|
pub struct BytesLen;
|
|
|
|
|
|
|
|
impl Command for BytesLen {
|
|
|
|
fn name(&self) -> &str {
|
|
|
|
"bytes length"
|
|
|
|
}
|
|
|
|
|
|
|
|
fn signature(&self) -> Signature {
|
|
|
|
Signature::build("bytes length")
|
2022-11-09 21:55:05 +00:00
|
|
|
.input_output_types(vec![(Type::Binary, Type::Int)])
|
|
|
|
.vectorizes_over_list(true)
|
2022-07-04 10:51:07 +00:00
|
|
|
.rest(
|
|
|
|
"rest",
|
|
|
|
SyntaxShape::CellPath,
|
2022-11-10 05:49:11 +00:00
|
|
|
"for a data structure input, find the length of data at the given cell paths",
|
2022-07-04 10:51:07 +00:00
|
|
|
)
|
|
|
|
.category(Category::Bytes)
|
|
|
|
}
|
|
|
|
|
|
|
|
fn usage(&self) -> &str {
|
|
|
|
"Output the length of any bytes in the pipeline"
|
|
|
|
}
|
|
|
|
|
|
|
|
fn search_terms(&self) -> Vec<&str> {
|
2022-08-24 09:16:47 +00:00
|
|
|
vec!["size", "count"]
|
2022-07-04 10:51:07 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
fn run(
|
|
|
|
&self,
|
|
|
|
engine_state: &EngineState,
|
|
|
|
stack: &mut Stack,
|
|
|
|
call: &Call,
|
|
|
|
input: PipelineData,
|
|
|
|
) -> Result<PipelineData, ShellError> {
|
2022-10-29 21:29:46 +00:00
|
|
|
let cell_paths: Vec<CellPath> = call.rest(engine_state, stack, 1)?;
|
2022-11-01 11:40:11 +00:00
|
|
|
let arg = CellPathOnlyArgs::from(cell_paths);
|
2022-07-05 11:42:01 +00:00
|
|
|
operate(length, arg, input, call.head, engine_state.ctrlc.clone())
|
2022-07-04 10:51:07 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
fn examples(&self) -> Vec<Example> {
|
|
|
|
vec![
|
|
|
|
Example {
|
|
|
|
description: "Return the lengths of multiple strings",
|
|
|
|
example: "0x[1F FF AA AB] | bytes length",
|
|
|
|
result: Some(Value::test_int(4)),
|
|
|
|
},
|
|
|
|
Example {
|
|
|
|
description: "Return the lengths of multiple strings",
|
|
|
|
example: "[0x[1F FF AA AB] 0x[1F]] | bytes length",
|
|
|
|
result: Some(Value::List {
|
|
|
|
vals: vec![Value::test_int(4), Value::test_int(1)],
|
|
|
|
span: Span::test_data(),
|
|
|
|
}),
|
|
|
|
},
|
|
|
|
]
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-11-01 11:40:11 +00:00
|
|
|
fn length(val: &Value, _args: &CellPathOnlyArgs, span: Span) -> Value {
|
2022-10-29 21:29:46 +00:00
|
|
|
match val {
|
|
|
|
Value::Binary {
|
|
|
|
val,
|
|
|
|
span: val_span,
|
Reduced LOC by replacing several instances of `Value::Int {}`, `Value::Float{}`, `Value::Bool {}`, and `Value::String {}` with `Value::int()`, `Value::float()`, `Value::boolean()` and `Value::string()` (#7412)
# Description
While perusing Value.rs, I noticed the `Value::int()`, `Value::float()`,
`Value::boolean()` and `Value::string()` constructors, which seem
designed to make it easier to construct various Values, but which aren't
used often at all in the codebase. So, using a few find-replaces
regexes, I increased their usage. This reduces overall LOC because
structures like this:
```
Value::Int {
val: a,
span: head
}
```
are changed into
```
Value::int(a, head)
```
and are respected as such by the project's formatter.
There are little readability concerns because the second argument to all
of these is `span`, and it's almost always extremely obvious which is
the span at every callsite.
# User-Facing Changes
None.
# Tests + Formatting
Don't forget to add tests that cover your changes.
Make sure you've run and fixed any issues with these commands:
- `cargo fmt --all -- --check` to check standard code formatting (`cargo
fmt --all` applies these changes)
- `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A
clippy::needless_collect` to check that you're using the standard code
style
- `cargo test --workspace` to check that all tests pass
# After Submitting
If your PR had any user-facing changes, update [the
documentation](https://github.com/nushell/nushell.github.io) after the
PR is merged, if necessary. This will help us keep the docs up to date.
2022-12-09 16:37:51 +00:00
|
|
|
} => Value::int(val.len() as i64, *val_span),
|
2022-10-29 21:29:46 +00:00
|
|
|
other => Value::Error {
|
|
|
|
error: ShellError::UnsupportedInput(
|
|
|
|
format!(
|
|
|
|
"Input's type is {}. This command only works with bytes.",
|
|
|
|
other.get_type()
|
|
|
|
),
|
|
|
|
span,
|
|
|
|
),
|
|
|
|
},
|
2022-07-04 10:51:07 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
mod test {
|
|
|
|
use super::*;
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_examples() {
|
|
|
|
use crate::test_examples;
|
|
|
|
|
|
|
|
test_examples(BytesLen {})
|
|
|
|
}
|
|
|
|
}
|