<!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> Related meta-issue: #10239. # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> This PR will modify some `str`-related commands so that they can be evaluated at parse time. See the following list for those implemented by this pr. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> Available now: - `str` subcommands - `trim` - `contains` - `distance` - `ends-with` - `expand` - `index-of` - `join` - `replace` - `reverse` - `starts-with` - `stats` - `substring` - `capitalize` - `downcase` - `upcase` - `split` subcommands - `chars` - `column` - `list` - `row` - `words` - `format` subcommands - `date` - `duration` - `filesize` - string related commands - `parse` - `detect columns` - `encode` & `decode` # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use toolkit.nu; toolkit test stdlib"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> Unresolved questions: - [ ] Is there any routine of testing const expressions? I haven't found any yet. - [ ] Is const expressions required to behave just like there non-const version, like what rust promises? # 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. --> Unresolved questions: - [ ] Do const commands need special marks in the docs?
129 lines
3.5 KiB
Rust
129 lines
3.5 KiB
Rust
use nu_engine::command_prelude::*;
|
|
|
|
use std::io::Write;
|
|
|
|
#[derive(Clone)]
|
|
pub struct StrJoin;
|
|
|
|
impl Command for StrJoin {
|
|
fn name(&self) -> &str {
|
|
"str join"
|
|
}
|
|
|
|
fn signature(&self) -> Signature {
|
|
Signature::build("str join")
|
|
.input_output_types(vec![
|
|
(Type::List(Box::new(Type::Any)), Type::String),
|
|
(Type::String, Type::String),
|
|
])
|
|
.optional(
|
|
"separator",
|
|
SyntaxShape::String,
|
|
"Optional separator to use when creating string.",
|
|
)
|
|
.allow_variants_without_examples(true)
|
|
.category(Category::Strings)
|
|
}
|
|
|
|
fn usage(&self) -> &str {
|
|
"Concatenate multiple strings into a single string, with an optional separator between each."
|
|
}
|
|
|
|
fn search_terms(&self) -> Vec<&str> {
|
|
vec!["collect", "concatenate"]
|
|
}
|
|
|
|
fn is_const(&self) -> bool {
|
|
true
|
|
}
|
|
|
|
fn run(
|
|
&self,
|
|
engine_state: &EngineState,
|
|
stack: &mut Stack,
|
|
call: &Call,
|
|
input: PipelineData,
|
|
) -> Result<PipelineData, ShellError> {
|
|
let separator: Option<String> = call.opt(engine_state, stack, 0)?;
|
|
run(engine_state, call, input, separator)
|
|
}
|
|
|
|
fn run_const(
|
|
&self,
|
|
working_set: &StateWorkingSet,
|
|
call: &Call,
|
|
input: PipelineData,
|
|
) -> Result<PipelineData, ShellError> {
|
|
let separator: Option<String> = call.opt_const(working_set, 0)?;
|
|
run(working_set.permanent(), call, input, separator)
|
|
}
|
|
|
|
fn examples(&self) -> Vec<Example> {
|
|
vec![
|
|
Example {
|
|
description: "Create a string from input",
|
|
example: "['nu', 'shell'] | str join",
|
|
result: Some(Value::test_string("nushell")),
|
|
},
|
|
Example {
|
|
description: "Create a string from input with a separator",
|
|
example: "['nu', 'shell'] | str join '-'",
|
|
result: Some(Value::test_string("nu-shell")),
|
|
},
|
|
]
|
|
}
|
|
}
|
|
|
|
fn run(
|
|
engine_state: &EngineState,
|
|
call: &Call,
|
|
input: PipelineData,
|
|
separator: Option<String>,
|
|
) -> Result<PipelineData, ShellError> {
|
|
let config = engine_state.config.clone();
|
|
|
|
let span = call.head;
|
|
|
|
let metadata = input.metadata();
|
|
let mut iter = input.into_iter();
|
|
let mut first = true;
|
|
|
|
let output = ByteStream::from_fn(span, None, ByteStreamType::String, move |buffer| {
|
|
// Write each input to the buffer
|
|
if let Some(value) = iter.next() {
|
|
// Write the separator if this is not the first
|
|
if first {
|
|
first = false;
|
|
} else if let Some(separator) = &separator {
|
|
write!(buffer, "{}", separator)?;
|
|
}
|
|
|
|
match value {
|
|
Value::Error { error, .. } => {
|
|
return Err(*error);
|
|
}
|
|
// Hmm, not sure what we actually want.
|
|
// `to_expanded_string` formats dates as human readable which feels funny.
|
|
Value::Date { val, .. } => write!(buffer, "{val:?}")?,
|
|
value => write!(buffer, "{}", value.to_expanded_string("\n", &config))?,
|
|
}
|
|
Ok(true)
|
|
} else {
|
|
Ok(false)
|
|
}
|
|
});
|
|
|
|
Ok(PipelineData::ByteStream(output, metadata))
|
|
}
|
|
|
|
#[cfg(test)]
|
|
mod tests {
|
|
use super::*;
|
|
#[test]
|
|
fn test_examples() {
|
|
use crate::test_examples;
|
|
|
|
test_examples(StrJoin {})
|
|
}
|
|
}
|