nushell/crates/nu-command/tests/commands/skip/until.rs

44 lines
1.3 KiB
Rust
Raw Normal View History

2020-07-14 17:04:00 +02:00
use nu_test_support::{nu, pipeline};
#[test]
fn condition_is_met() {
let sample = r#"
[["Chicken Collection", "29/04/2020", "30/04/2020", "31/04/2020"];
["Yellow Chickens", "", "", ""],
[Andrés, 0, 0, 1],
[JT, 0, 0, 1],
[Jason, 0, 0, 1],
[Yehuda, 0, 0, 1],
["Blue Chickens", "", "", ""],
[Andrés, 0, 0, 2],
[JT, 0, 0, 2],
[Jason, 0, 0, 2],
[Yehuda, 0, 0, 2],
["Red Chickens", "", "", ""],
[Andrés, 0, 0, 1],
[JT, 0, 0, 1],
[Jason, 0, 0, 1],
[Yehuda, 0, 0, 3]]
"#;
2020-07-14 17:04:00 +02:00
let actual = nu!(pipeline(&format!(
r#"
{sample}
| skip until {{|row| $row."Chicken Collection" == "Red Chickens" }}
| skip 1
| into int "31/04/2020"
2020-07-14 17:04:00 +02:00
| get "31/04/2020"
| math sum
"#
)));
2020-07-14 17:04:00 +02:00
assert_eq!(actual.out, "6");
2020-07-14 17:04:00 +02:00
}
#[test]
fn fail_on_non_iterator() {
let actual = nu!("1 | skip until {|row| $row == 2}");
Input output checking (#9680) # Description This PR tights input/output type-checking a bit more. There are a lot of commands that don't have correct input/output types, so part of the effort is updating them. This PR now contains updates to commands that had wrong input/output signatures. It doesn't add examples for these new signatures, but that can be follow-up work. # User-Facing Changes BREAKING CHANGE BREAKING CHANGE This work enforces many more checks on pipeline type correctness than previous nushell versions. This strictness may uncover incompatibilities in existing scripts or shortcomings in the type information for internal commands. # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` 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 > ``` --> # 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. -->
2023-07-14 05:20:35 +02:00
assert!(actual.err.contains("command doesn't support"));
}