nushell/tests/shell/pipeline/commands/internal.rs

1777 lines
38 KiB
Rust
Raw Normal View History

2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
#[cfg(feature = "which")]
use nu_test_support::fs::Stub::FileWithContent;
2022-02-07 20:11:34 +01:00
=======
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
use nu_test_support::fs::Stub::FileWithContentToBeTrimmed;
use nu_test_support::nu;
use nu_test_support::pipeline;
use nu_test_support::playground::Playground;
#[test]
fn takes_rows_of_nu_value_strings_and_pipes_it_to_stdin_of_external() {
Playground::setup("internal_to_external_pipe_test_1", |dirs, sandbox| {
sandbox.with_files(vec![FileWithContentToBeTrimmed(
"nu_times.csv",
r#"
name,rusty_luck,origin
Jason,1,Canada
Jonathan,1,New Zealand
Andrés,1,Ecuador
AndKitKatz,1,Estados Unidos
"#,
)]);
let actual = nu!(
cwd: dirs.test(), pipeline(
r#"
open nu_times.csv
| get origin
| each { ^echo $it | nu --testbin chop | lines }
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
| nth 2
2022-02-07 20:11:34 +01:00
=======
| get 2
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
));
// chop will remove the last escaped double quote from \"Estados Unidos\"
assert_eq!(actual.out, "Ecuado");
})
}
2021-04-19 22:18:29 +02:00
#[test]
fn treats_dot_dot_as_path_not_range() {
Playground::setup("dot_dot_dir", |dirs, sandbox| {
sandbox.with_files(vec![FileWithContentToBeTrimmed(
"nu_times.csv",
r#"
name,rusty_luck,origin
Jason,1,Canada
"#,
)]);
let actual = nu!(
cwd: dirs.test(), pipeline(
r#"
mkdir temp;
cd temp;
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
echo (open ../nu_times.csv).name | autoview;
2022-02-07 20:11:34 +01:00
=======
echo (open ../nu_times.csv).name.0 | table;
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-04-19 22:18:29 +02:00
cd ..;
rmdir temp
"#
));
// chop will remove the last escaped double quote from \"Estados Unidos\"
assert_eq!(actual.out, "Jason");
})
}
#[test]
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
fn tags_dont_persist_through_column_path() {
Playground::setup("dot_dot_dir", |dirs, sandbox| {
sandbox.with_files(vec![FileWithContentToBeTrimmed(
"nu_times.csv",
r#"
name,rusty_luck,origin
Jason,1,Canada
"#,
)]);
let actual = nu!(
cwd: dirs.test(), pipeline(
r#"
mkdir temp;
cd temp;
let x = (open ../nu_times.csv).name;
$x | tags | get anchor | autoview;
cd ..;
rmdir temp
"#
));
// chop will remove the last escaped double quote from \"Estados Unidos\"
assert!(actual.err.contains("isn't a column"));
})
}
#[test]
fn tags_persist_through_vars() {
Playground::setup("dot_dot_dir", |dirs, sandbox| {
sandbox.with_files(vec![FileWithContentToBeTrimmed(
"nu_times.csv",
r#"
name,rusty_luck,origin
Jason,1,Canada
"#,
)]);
let actual = nu!(
cwd: dirs.test(), pipeline(
r#"
mkdir temp;
cd temp;
let x = (open ../nu_times.csv);
$x | tags | get anchor.file | autoview;
cd ..;
rmdir temp
"#
));
// chop will remove the last escaped double quote from \"Estados Unidos\"
assert!(actual.out.contains("nu_times.csv"));
})
}
#[test]
2022-02-07 20:11:34 +01:00
=======
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
fn subexpression_properly_redirects() {
let actual = nu!(
cwd: ".",
r#"
echo (nu --testbin cococo "hello") | str collect
"#
);
assert_eq!(actual.out, "hello");
}
#[test]
fn argument_subexpression() {
let actual = nu!(
cwd: ".",
r#"
echo "foo" | each { echo (echo $it) }
"#
);
assert_eq!(actual.out, "foo");
}
#[test]
fn subexpression_handles_dot() {
Playground::setup("subexpression_handles_dot", |dirs, sandbox| {
sandbox.with_files(vec![FileWithContentToBeTrimmed(
"nu_times.csv",
r#"
name,rusty_luck,origin
Jason,1,Canada
Jonathan,1,New Zealand
Andrés,1,Ecuador
AndKitKatz,1,Estados Unidos
"#,
)]);
let actual = nu!(
cwd: dirs.test(), pipeline(
r#"
echo (open nu_times.csv)
| get name
| each { nu --testbin chop $it | lines }
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
| nth 3
2022-02-07 20:11:34 +01:00
=======
| get 3
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
));
assert_eq!(actual.out, "AndKitKat");
})
}
#[test]
fn string_interpolation_with_it() {
let actual = nu!(
cwd: ".",
r#"
echo "foo" | each { echo $"($it)" }
"#
);
assert_eq!(actual.out, "foo");
}
#[test]
fn string_interpolation_with_it_column_path() {
let actual = nu!(
cwd: ".",
r#"
echo [[name]; [sammie]] | each { echo $"($it.name)" }
"#
);
assert_eq!(actual.out, "sammie");
}
#[test]
fn string_interpolation_shorthand_overlap() {
let actual = nu!(
cwd: ".",
r#"
$"3 + 4 = (3 + 4)"
"#
);
assert_eq!(actual.out, "3 + 4 = 7");
}
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
=======
// FIXME: jt - we don't currently have a way to escape the single ticks easily
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
#[test]
fn string_interpolation_and_paren() {
let actual = nu!(
cwd: ".",
r#"
$"a paren is ('(')"
"#
);
assert_eq!(actual.out, "a paren is (");
}
#[test]
fn string_interpolation_with_unicode() {
//カ = U+30AB : KATAKANA LETTER KA
let actual = nu!(
cwd: ".",
r#"
$""
"#
);
assert_eq!(actual.out, "");
}
#[test]
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
fn bignum_large_integer() {
let actual = nu!(
cwd: ".",
r#"
echo 91231720741731287123917
"#
);
assert_eq!(actual.out, "91231720741731287123917");
}
#[test]
fn bignum_large_decimal() {
let actual = nu!(
cwd: ".",
r#"
echo 91231720741731287123917.1
"#
);
assert_eq!(actual.out, "91231720741731287123917.1");
}
#[test]
2022-02-07 20:11:34 +01:00
=======
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
fn run_custom_command() {
let actual = nu!(
cwd: ".",
r#"
def add-me [x y] { $x + $y}; add-me 10 5
"#
);
assert_eq!(actual.out, "15");
}
#[test]
fn run_custom_command_with_flag() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
def foo [--bar:number] { if ($bar | empty?) { echo "empty" } { echo $bar } }; foo --bar 10
2022-02-07 20:11:34 +01:00
=======
def foo [--bar:number] { if ($bar | empty?) { echo "empty" } else { echo $bar } }; foo --bar 10
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "10");
}
#[test]
fn run_custom_command_with_flag_missing() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
def foo [--bar:number] { if ($bar | empty?) { echo "empty" } { echo $bar } }; foo
2022-02-07 20:11:34 +01:00
=======
def foo [--bar:number] { if ($bar | empty?) { echo "empty" } else { echo $bar } }; foo
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "empty");
}
#[test]
fn run_custom_subcommand() {
let actual = nu!(
cwd: ".",
r#"
def "str double" [x] { echo $x $x | str collect }; str double bob
"#
);
assert_eq!(actual.out, "bobbob");
}
#[test]
fn run_inner_custom_command() {
let actual = nu!(
cwd: ".",
r#"
def outer [x] { def inner [y] { echo $y }; inner $x }; outer 10
"#
);
assert_eq!(actual.out, "10");
}
#[test]
fn run_broken_inner_custom_command() {
let actual = nu!(
cwd: ".",
r#"
def outer [x] { def inner [y] { echo $y }; inner $x }; inner 10
"#
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("not found"));
2022-02-07 20:11:34 +01:00
=======
assert!(!actual.err.is_empty());
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
2021-01-22 22:28:32 +01:00
#[test]
fn run_custom_command_with_rest() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
2021-01-22 22:28:32 +01:00
def rest-me [...rest: string] { echo $rest.1 $rest.0}; rest-me "hello" "world" | to json
2022-02-07 20:11:34 +01:00
=======
def rest-me [...rest: string] { echo $rest.1 $rest.0}; rest-me "hello" "world" | to json --raw
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-01-22 22:28:32 +01:00
"#
);
assert_eq!(actual.out, r#"["world","hello"]"#);
}
#[test]
fn run_custom_command_with_rest_and_arg() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
2021-01-22 22:28:32 +01:00
def rest-me-with-arg [name: string, ...rest: string] { echo $rest.1 $rest.0 $name}; rest-me-with-arg "hello" "world" "yay" | to json
2022-02-07 20:11:34 +01:00
=======
def rest-me-with-arg [name: string, ...rest: string] { echo $rest.1 $rest.0 $name}; rest-me-with-arg "hello" "world" "yay" | to json --raw
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-01-22 22:28:32 +01:00
"#
);
assert_eq!(actual.out, r#"["yay","world","hello"]"#);
}
#[test]
fn run_custom_command_with_rest_and_flag() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
2021-01-22 22:28:32 +01:00
def rest-me-with-flag [--name: string, ...rest: string] { echo $rest.1 $rest.0 $name}; rest-me-with-flag "hello" "world" --name "yay" | to json
2022-02-07 20:11:34 +01:00
=======
def rest-me-with-flag [--name: string, ...rest: string] { echo $rest.1 $rest.0 $name}; rest-me-with-flag "hello" "world" --name "yay" | to json --raw
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-01-22 22:28:32 +01:00
"#
);
assert_eq!(actual.out, r#"["world","hello","yay"]"#);
}
#[test]
fn run_custom_command_with_empty_rest() {
let actual = nu!(
cwd: ".",
r#"
def rest-me-with-empty-rest [...rest: string] { echo $rest }; rest-me-with-empty-rest
"#
);
assert_eq!(actual.out, r#""#);
assert_eq!(actual.err, r#""#);
}
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
=======
//FIXME: jt: blocked on https://github.com/nushell/engine-q/issues/912
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
#[test]
fn run_custom_command_with_rest_other_name() {
let actual = nu!(
cwd: ".",
r#"
def say-hello [
greeting:string,
...names:string # All of the names
] {
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
echo $"($greeting), ($names | sort-by | str collect ' ')"
2022-02-07 20:11:34 +01:00
=======
echo $"($greeting), ($names | sort-by | str collect)"
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
say-hello Salutations E D C A B
"#
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert_eq!(actual.out, r#"Salutations, A B C D E"#);
2022-02-07 20:11:34 +01:00
=======
assert_eq!(actual.out, r#"Salutations, ABCDE"#);
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
assert_eq!(actual.err, r#""#);
}
#[test]
fn alias_a_load_env() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
def activate-helper [] { [[name, value]; [BOB, SAM]] }; alias activate = load-env (activate-helper); activate; $nu.env.BOB
2022-02-07 20:11:34 +01:00
=======
def activate-helper [] { {BOB: SAM} }; alias activate = load-env (activate-helper); activate; $env.BOB
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, r#"SAM"#);
}
#[test]
2021-05-20 06:26:54 +02:00
fn let_variable() {
let actual = nu!(
cwd: ".",
r#"
let x = 5
let y = 12
$x + $y
"#
);
assert_eq!(actual.out, "17");
}
#[test]
2021-05-20 06:26:54 +02:00
fn let_doesnt_leak() {
let actual = nu!(
cwd: ".",
r#"
do { let x = 5 }; echo $x
"#
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("unknown variable"));
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("variable not found"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
2021-05-20 06:26:54 +02:00
fn let_env_variable() {
let actual = nu!(
cwd: ".",
r#"
let-env TESTENVVAR = "hello world"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
echo $nu.env.TESTENVVAR
2022-02-07 20:11:34 +01:00
=======
echo $env.TESTENVVAR
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "hello world");
}
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
#[test]
fn let_env_hides_variable() {
let actual = nu!(
cwd: ".",
r#"
let-env TESTENVVAR = "hello world"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
echo $nu.env.TESTENVVAR
let-env TESTENVVAR = $nothing
echo $nu.env.TESTENVVAR
2022-02-07 20:11:34 +01:00
=======
echo $env.TESTENVVAR
hide TESTENVVAR
echo $env.TESTENVVAR
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
"#
);
assert_eq!(actual.out, "hello world");
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
assert!(actual.err.contains("error"));
assert!(actual.err.contains("Unknown column"));
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("did you mean"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
}
#[test]
fn let_env_hides_variable_in_parent_scope() {
let actual = nu!(
cwd: ".",
r#"
let-env TESTENVVAR = "hello world"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
echo $nu.env.TESTENVVAR
do {
let-env TESTENVVAR = $nothing
echo $nu.env.TESTENVVAR
}
echo $nu.env.TESTENVVAR
"#
);
assert_eq!(actual.out, "hello worldhello world");
assert!(actual.err.contains("error"));
assert!(actual.err.contains("Unknown column"));
2022-02-07 20:11:34 +01:00
=======
echo $env.TESTENVVAR
do {
hide TESTENVVAR
echo $env.TESTENVVAR
}
echo $env.TESTENVVAR
"#
);
assert_eq!(actual.out, "hello world");
assert!(actual.err.contains("did you mean"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
}
#[test]
fn unlet_env_variable() {
let actual = nu!(
cwd: ".",
r#"
let-env TEST_VAR = "hello world"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
unlet-env TEST_VAR
echo $nu.env.TEST_VAR
2022-02-07 20:11:34 +01:00
=======
hide TEST_VAR
echo $env.TEST_VAR
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert!(actual.err.contains("did you mean"));
}
#[test]
fn unlet_nonexistent_variable() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
unlet-env NONEXISTENT_VARIABLE
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
"#
);
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
assert!(actual.err.contains("error"));
assert!(actual.err.contains("Not an environment variable"));
2022-02-07 20:11:34 +01:00
=======
hide NONEXISTENT_VARIABLE
"#
);
assert!(actual.err.contains("did not find"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
}
#[test]
fn unlet_variable_in_parent_scope() {
let actual = nu!(
cwd: ".",
r#"
let-env DEBUG = "1"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
echo $nu.env.DEBUG
do {
let-env DEBUG = "2"
echo $nu.env.DEBUG
unlet-env DEBUG
echo $nu.env.DEBUG
}
echo $nu.env.DEBUG
2022-02-07 20:11:34 +01:00
=======
echo $env.DEBUG
do {
let-env DEBUG = "2"
echo $env.DEBUG
hide DEBUG
echo $env.DEBUG
}
echo $env.DEBUG
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
"#
);
assert_eq!(actual.out, "1211");
}
#[test]
2021-05-20 06:26:54 +02:00
fn let_env_doesnt_leak() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
do { let-env xyz = "my message" }; echo $nu.env.xyz
2022-02-07 20:11:34 +01:00
=======
do { let-env xyz = "my message" }; echo $env.xyz
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert!(actual.err.contains("did you mean"));
}
2021-01-03 08:48:02 +01:00
#[test]
2021-05-20 06:26:54 +02:00
fn proper_shadow_let_env_aliases() {
2021-01-03 08:48:02 +01:00
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
let-env DEBUG = true; echo $nu.env.DEBUG | autoview; do { let-env DEBUG = false; echo $nu.env.DEBUG } | autoview; echo $nu.env.DEBUG
2022-02-07 20:11:34 +01:00
=======
let-env DEBUG = true; echo $env.DEBUG | table; do { let-env DEBUG = false; echo $env.DEBUG } | table; echo $env.DEBUG
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-01-03 08:48:02 +01:00
"#
);
assert_eq!(actual.out, "truefalsetrue");
}
#[test]
fn load_env_variable() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
echo [[name, value]; [TESTENVVAR, "hello world"]] | load-env
echo $nu.env.TESTENVVAR
2022-02-07 20:11:34 +01:00
=======
echo {TESTENVVAR: "hello world"} | load-env
echo $env.TESTENVVAR
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "hello world");
}
#[test]
fn load_env_variable_arg() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
load-env [[name, value]; [TESTENVVAR, "hello world"]]
echo $nu.env.TESTENVVAR
2022-02-07 20:11:34 +01:00
=======
load-env {TESTENVVAR: "hello world"}
echo $env.TESTENVVAR
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "hello world");
}
#[test]
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
fn load_env_variable_arg_and_stream() {
let actual = nu!(
cwd: ".",
r#"
echo [[name, value]; [TESTVARSTREAM, "true"]] | load-env [[name, value]; [TESTVARARG, "false"]]
echo $nu.env | format "{TESTVARSTREAM} {TESTVARARG}"
"#
);
assert_eq!(actual.out, "true false");
}
#[test]
2022-02-07 20:11:34 +01:00
=======
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
fn load_env_doesnt_leak() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
do { echo [[name, value]; [xyz, "my message"]] | load-env }; echo $nu.env.xyz
2022-02-07 20:11:34 +01:00
=======
do { echo { name: xyz, value: "my message" } | load-env }; echo $env.xyz
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert!(actual.err.contains("did you mean"));
}
#[test]
fn proper_shadow_load_env_aliases() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
let-env DEBUG = true; echo $nu.env.DEBUG | autoview; do { echo [[name, value]; [DEBUG, false]] | load-env; echo $nu.env.DEBUG } | autoview; echo $nu.env.DEBUG
2022-02-07 20:11:34 +01:00
=======
let-env DEBUG = true; echo $env.DEBUG | table; do { echo {DEBUG: "false"} | load-env; echo $env.DEBUG } | table; echo $env.DEBUG
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "truefalsetrue");
}
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
=======
//FIXME: jt: load-env can not currently hide variables because $nothing no longer hides
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
#[test]
fn load_env_can_hide_var_envs() {
let actual = nu!(
cwd: ".",
r#"
let-env DEBUG = "1"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
echo $nu.env.DEBUG
load-env [[name, value]; [DEBUG $nothing]]
echo $nu.env.DEBUG
2022-02-07 20:11:34 +01:00
=======
echo $env.DEBUG
load-env [[name, value]; [DEBUG $nothing]]
echo $env.DEBUG
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
"#
);
assert_eq!(actual.out, "1");
assert!(actual.err.contains("error"));
assert!(actual.err.contains("Unknown column"));
}
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
=======
//FIXME: jt: load-env can not currently hide variables because $nothing no longer hides
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
#[test]
fn load_env_can_hide_var_envs_in_parent_scope() {
let actual = nu!(
cwd: ".",
r#"
let-env DEBUG = "1"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
echo $nu.env.DEBUG
do {
load-env [[name, value]; [DEBUG $nothing]]
echo $nu.env.DEBUG
}
echo $nu.env.DEBUG
2022-02-07 20:11:34 +01:00
=======
echo $env.DEBUG
do {
load-env [[name, value]; [DEBUG $nothing]]
echo $env.DEBUG
}
echo $env.DEBUG
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
Allow environment variables to be hidden (#3950) * Allow environment variables to be hidden This change allows environment variables in Nushell to have a value of `Nothing`, which can be set by the user by passing `$nothing` to `let-env` and friends. Environment variables with a value of Nothing behave as if they are not set at all. This allows a user to shadow the value of an environment variable in a parent scope, effectively removing it from their current scope. This was not possible before, because a scope can not affect its parent scopes. This is a workaround for issues like #3920. Additionally, this allows a user to simultaneously set, change and remove multiple environment variables via `load-env`. Any environment variables set to $nothing will be hidden and thus act as if they are removed. This simplifies working with virtual environments, which rely on setting multiple environment variables, including PATH, to specific values, and remove/change them on deactivation. One surprising behavior is that an environment variable set to $nothing will act as if it is not set when querying it (via $nu.env.X), but it is still possible to remove it entirely via `unlet-env`. If the same environment variable is present in the parent scope, the value in the parent scope will be visible to the user. This might be surprising behavior to users who are not familiar with the implementation details. An additional corner case is the the shorthand form of `with-env` does not work with this feature. Using `X=$nothing` will set $nu.env.X to the string "$nothing". The long-form works as expected: `with-env [X $nothing] {...}`. * Remove unused import * Allow all primitives to be convert to strings
2021-08-26 15:15:58 +02:00
"#
);
assert_eq!(actual.out, "11");
assert!(actual.err.contains("error"));
assert!(actual.err.contains("Unknown column"));
}
2021-01-03 08:48:02 +01:00
#[test]
2021-05-20 06:26:54 +02:00
fn proper_shadow_let_aliases() {
2021-01-03 08:48:02 +01:00
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
let DEBUG = false; echo $DEBUG | autoview; do { let DEBUG = true; echo $DEBUG } | autoview; echo $DEBUG
2022-02-07 20:11:34 +01:00
=======
let DEBUG = $false; echo $DEBUG | table; do { let DEBUG = $true; echo $DEBUG } | table; echo $DEBUG
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-01-03 08:48:02 +01:00
"#
);
assert_eq!(actual.out, "falsetruefalse");
}
2021-05-20 06:26:54 +02:00
#[test]
fn block_params_override() {
2021-05-20 06:26:54 +02:00
let actual = nu!(
cwd: ".",
r#"
[1, 2, 3] | each { |a| echo $it }
2021-05-20 06:26:54 +02:00
"#
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("unknown variable"));
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("variable not found"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-05-20 06:26:54 +02:00
}
#[test]
fn block_params_override_correct() {
2021-05-20 06:26:54 +02:00
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
[1, 2, 3] | each { |a| echo $a } | to json
2022-02-07 20:11:34 +01:00
=======
[1, 2, 3] | each { |a| echo $a } | to json --raw
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-05-20 06:26:54 +02:00
"#
);
assert_eq!(actual.out, "[1,2,3]");
2021-05-20 06:26:54 +02:00
}
2021-06-06 07:14:51 +02:00
#[test]
fn hex_number() {
let actual = nu!(
cwd: ".",
r#"
0x10
"#
);
assert_eq!(actual.out, "16");
}
#[test]
fn binary_number() {
let actual = nu!(
cwd: ".",
r#"
0b10
"#
);
assert_eq!(actual.out, "2");
}
#[test]
fn octal_number() {
let actual = nu!(
cwd: ".",
r#"
0o10
"#
);
assert_eq!(actual.out, "8");
}
#[test]
fn run_dynamic_blocks() {
let actual = nu!(
cwd: ".",
r#"
let block = { echo "holaaaa" }; do $block
"#
);
assert_eq!(actual.out, "holaaaa");
}
#[cfg(feature = "which")]
2020-05-19 14:57:25 +02:00
#[test]
fn argument_subexpression_reports_errors() {
2020-05-19 14:57:25 +02:00
let actual = nu!(
cwd: ".",
"echo (ferris_is_not_here.exe)"
2020-05-19 14:57:25 +02:00
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
2020-05-19 14:57:25 +02:00
assert!(actual.err.contains("Command not found"));
2022-02-07 20:11:34 +01:00
=======
assert!(!actual.err.is_empty());
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2020-05-19 14:57:25 +02:00
}
#[test]
fn can_process_one_row_from_internal_and_pipes_it_to_stdin_of_external() {
let actual = nu!(
cwd: ".",
2020-05-18 05:52:56 +02:00
r#"echo "nushelll" | nu --testbin chop"#
);
assert_eq!(actual.out, "nushell");
}
2021-05-24 07:27:10 +02:00
#[test]
fn bad_operator() {
let actual = nu!(
cwd: ".",
r#"
2 $ 2
"#
);
assert!(actual.err.contains("operator"));
}
#[test]
fn index_out_of_bounds() {
let actual = nu!(
cwd: ".",
r#"
let foo = [1, 2, 3]; echo $foo.5
"#
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("unknown row"));
}
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("too large"));
}
//FIXME: jt - umm, do we actually want to support this?
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
#[test]
fn dash_def() {
let actual = nu!(
cwd: ".",
r#"
def - [x, y] { $x - $y }; - 4 1
"#
);
assert_eq!(actual.out, "3");
}
#[test]
fn negative_decimal_start() {
let actual = nu!(
cwd: ".",
r#"
-1.3 + 4
"#
);
assert_eq!(actual.out, "2.7");
}
2021-08-06 23:49:37 +02:00
#[test]
fn string_inside_of() {
let actual = nu!(
cwd: ".",
r#"
"bob" in "bobby"
"#
);
assert_eq!(actual.out, "true");
}
#[test]
fn string_not_inside_of() {
let actual = nu!(
cwd: ".",
r#"
"bob" not-in "bobby"
"#
);
assert_eq!(actual.out, "false");
}
#[test]
fn index_row() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
let foo = [[name]; [joe] [bob]]; echo $foo.1 | to json
"#
);
assert_eq!(actual.out, r#"{"name":"bob"}"#);
2022-02-07 20:11:34 +01:00
=======
let foo = [[name]; [joe] [bob]]; echo $foo.1 | to json --raw
"#
);
assert_eq!(actual.out, r#"{"name": "bob"}"#);
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn index_cell() {
let actual = nu!(
cwd: ".",
r#"
let foo = [[name]; [joe] [bob]]; echo $foo.name.1
"#
);
assert_eq!(actual.out, "bob");
}
#[test]
fn index_cell_alt() {
let actual = nu!(
cwd: ".",
r#"
let foo = [[name]; [joe] [bob]]; echo $foo.1.name
"#
);
assert_eq!(actual.out, "bob");
}
#[test]
fn not_echoing_ranges_without_numbers() {
let actual = nu!(
cwd: ".",
r#"
echo ..
"#
);
assert_eq!(actual.out, "..");
}
#[test]
fn not_echoing_exclusive_ranges_without_numbers() {
let actual = nu!(
cwd: ".",
r#"
echo ..<
"#
);
assert_eq!(actual.out, "..<");
}
2020-05-27 20:07:53 +02:00
#[test]
fn echoing_ranges() {
let actual = nu!(
cwd: ".",
r#"
echo 1..3 | math sum
2020-05-27 20:07:53 +02:00
"#
);
assert_eq!(actual.out, "6");
}
#[test]
fn echoing_exclusive_ranges() {
let actual = nu!(
cwd: ".",
r#"
echo 1..<4 | math sum
"#
);
assert_eq!(actual.out, "6");
}
#[test]
fn table_literals1() {
let actual = nu!(
cwd: ".",
r#"
echo [[name age]; [foo 13]] | get age
"#
);
assert_eq!(actual.out, "13");
}
#[test]
fn table_literals2() {
let actual = nu!(
cwd: ".",
r#"
echo [[name age] ; [bob 13] [sally 20]] | get age | math sum
"#
);
assert_eq!(actual.out, "33");
}
#[test]
fn list_with_commas() {
let actual = nu!(
cwd: ".",
r#"
echo [1, 2, 3] | math sum
"#
);
assert_eq!(actual.out, "6");
}
#[test]
fn range_with_left_var() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
echo [[size]; [3]] | each { echo $it.size..10 } | math sum
2022-02-07 20:11:34 +01:00
=======
({ size: 3}.size)..10 | math sum
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "52");
}
#[test]
fn range_with_right_var() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
echo [[size]; [30]] | each { echo 4..$it.size } | math sum
2022-02-07 20:11:34 +01:00
=======
4..({ size: 30}.size) | math sum
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
"#
);
assert_eq!(actual.out, "459");
}
#[test]
fn range_with_open_left() {
let actual = nu!(
cwd: ".",
r#"
echo ..30 | math sum
"#
);
assert_eq!(actual.out, "465");
}
#[test]
fn exclusive_range_with_open_left() {
let actual = nu!(
cwd: ".",
r#"
echo ..<31 | math sum
"#
);
assert_eq!(actual.out, "465");
}
#[test]
fn range_with_open_right() {
let actual = nu!(
cwd: ".",
r#"
echo 5.. | first 10 | math sum
"#
);
assert_eq!(actual.out, "95");
}
#[test]
fn exclusive_range_with_open_right() {
let actual = nu!(
cwd: ".",
r#"
echo 5..< | first 10 | math sum
"#
);
assert_eq!(actual.out, "95");
}
#[test]
fn range_with_mixed_types() {
let actual = nu!(
cwd: ".",
r#"
echo 1..10.5 | math sum
"#
);
assert_eq!(actual.out, "55");
}
#[test]
fn filesize_math() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
100 * 10kb
"#
);
assert_eq!(actual.out, "1000.0 KB");
2022-02-07 20:11:34 +01:00
=======
100 * 10kib
"#
);
assert_eq!(actual.out, "1000.0 KiB");
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
// why 1000.0 KB instead of 1.0 MB?
// looks like `byte.get_appropriate_unit(false)` behaves this way
}
#[test]
fn filesize_math2() {
let actual = nu!(
cwd: ".",
r#"
100 / 10kb
"#
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("Coercion"));
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("doesn't support"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn filesize_math3() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
100kb / 10
"#
);
assert_eq!(actual.out, "10.0 KB");
2022-02-07 20:11:34 +01:00
=======
100kib / 10
"#
);
assert_eq!(actual.out, "10.0 KiB");
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn filesize_math4() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
100kb * 5
"#
);
assert_eq!(actual.out, "500.0 KB");
2022-02-07 20:11:34 +01:00
=======
100kib * 5
"#
);
assert_eq!(actual.out, "500.0 KiB");
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn filesize_math5() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
1001 * 1kb
"#
);
assert_eq!(actual.out, "1.0 MB");
2022-02-07 20:11:34 +01:00
=======
1000 * 1kib
"#
);
assert_eq!(actual.out, "1000.0 KiB");
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn filesize_math6() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
1001 * 1mb
"#
);
assert_eq!(actual.out, "1.0 GB");
2022-02-07 20:11:34 +01:00
=======
1000 * 1mib
"#
);
assert_eq!(actual.out, "1000.0 MiB");
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn filesize_math7() {
let actual = nu!(
cwd: ".",
r#"
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
1001 * 1gb
"#
);
assert_eq!(actual.out, "1.0 TB");
2022-02-07 20:11:34 +01:00
=======
1000 * 1gib
"#
);
assert_eq!(actual.out, "1000.0 GiB");
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn exclusive_range_with_mixed_types() {
let actual = nu!(
cwd: ".",
r#"
echo 1..<10.5 | math sum
"#
);
assert_eq!(actual.out, "55");
}
#[test]
fn table_with_commas() {
let actual = nu!(
cwd: ".",
r#"
echo [[name, age, height]; [JT, 42, 185] [Unknown, 99, 99]] | get age | math sum
"#
);
assert_eq!(actual.out, "141");
}
2021-06-04 18:54:18 +02:00
#[test]
fn duration_overflow() {
let actual = nu!(
cwd: ".", pipeline(
r#"
ls | get modified | each { $it + 10000000000000000day }
"#)
);
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
2021-06-04 18:54:18 +02:00
assert!(actual.err.contains("Duration overflow"));
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("duration too large"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-06-04 18:54:18 +02:00
}
#[test]
fn date_and_duration_overflow() {
let actual = nu!(
cwd: ".", pipeline(
r#"
ls | get modified | each { $it + 1000000000day }
"#)
);
// assert_eq!(actual.err, "overflow");
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
2021-06-04 18:54:18 +02:00
assert!(actual.err.contains("Duration and date addition overflow"));
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("duration too large"));
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
2021-06-04 18:54:18 +02:00
}
#[test]
fn pipeline_params_simple() {
let actual = nu!(
cwd: ".", pipeline(
r#"
echo 1 2 3 | $in.1 * $in.2
"#)
);
assert_eq!(actual.out, "6");
}
#[test]
fn pipeline_params_inner() {
let actual = nu!(
cwd: ".", pipeline(
r#"
echo 1 2 3 | (echo $in.2 6 7 | $in.0 * $in.1 * $in.2)
"#)
);
assert_eq!(actual.out, "126");
}
#[test]
fn better_table_lex() {
let actual = nu!(
cwd: ".", pipeline(
r#"
let table = [
[name, size];
[small, 7]
[medium, 10]
[large, 12]
];
$table.1.size
"#)
);
assert_eq!(actual.out, "10");
}
#[test]
fn better_subexpr_lex() {
let actual = nu!(
cwd: ".", pipeline(
r#"
(echo boo
sam | str length | math sum)
"#)
);
assert_eq!(actual.out, "6");
}
#[test]
fn subsubcommand() {
let actual = nu!(
cwd: ".", pipeline(
r#"
def "aws s3 rb" [url] { $url + " loaded" }; aws s3 rb localhost
"#)
);
assert_eq!(actual.out, "localhost loaded");
}
#[test]
fn manysubcommand() {
let actual = nu!(
cwd: ".", pipeline(
r#"
def "aws s3 rb ax vf qqqq rrrr" [url] { $url + " loaded" }; aws s3 rb ax vf qqqq rrrr localhost
"#)
);
assert_eq!(actual.out, "localhost loaded");
}
2021-07-07 21:21:02 +02:00
#[test]
fn nothing_string_1() {
let actual = nu!(
cwd: ".", pipeline(
r#"
$nothing == "foo"
"#)
);
assert_eq!(actual.out, "false");
}
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
2021-07-07 21:21:02 +02:00
#[test]
fn nothing_string_2() {
let actual = nu!(
cwd: ".", pipeline(
r#"
"" == $nothing
"#)
);
assert_eq!(actual.out, "true");
}
2022-02-07 20:11:34 +01:00
=======
// FIXME: no current way to hide aliases
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
#[test]
fn unalias_shadowing() {
let actual = nu!(
cwd: ".", pipeline(
r#"
def test-shadowing [] {
alias greet = echo hello;
let xyz = { greet };
unalias greet;
do $xyz
};
test-shadowing
"#)
);
assert_eq!(actual.out, "hello");
}
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
=======
// FIXME: no current way to hide aliases
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
#[test]
fn unalias_does_not_escape_scope() {
let actual = nu!(
cwd: ".", pipeline(
r#"
def test-alias [] {
alias greet = echo hello;
(unalias greet);
greet
};
test-alias
"#)
);
assert_eq!(actual.out, "hello");
}
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
=======
// FIXME: no current way to hide aliases
#[ignore]
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
#[test]
fn unalias_hides_alias() {
let actual = nu!(cwd: ".", pipeline(
r#"
def test-alias [] {
alias ll = ls -l;
unalias ll;
ll
};
test-alias
"#)
);
assert!(actual.err.contains("not found"));
}
mod parse {
use nu_test_support::nu;
/*
The debug command's signature is:
Usage:
> debug {flags}
flags:
-h, --help: Display this help message
-r, --raw: Prints the raw value representation.
*/
#[test]
fn errors_if_flag_passed_is_not_exact() {
let actual = nu!(cwd: ".", "debug -ra");
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("unexpected flag"),);
let actual = nu!(cwd: ".", "debug --rawx");
assert!(actual.err.contains("unexpected flag"),);
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("unknown flag"),);
let actual = nu!(cwd: ".", "debug --rawx");
assert!(actual.err.contains("unknown flag"),);
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn errors_if_flag_is_not_supported() {
let actual = nu!(cwd: ".", "debug --ferris");
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("unexpected flag"),);
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("unknown flag"),);
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
#[test]
fn errors_if_passed_an_unexpected_argument() {
let actual = nu!(cwd: ".", "debug ferris");
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
assert!(actual.err.contains("unexpected argument"),);
2022-02-07 20:11:34 +01:00
=======
assert!(actual.err.contains("extra positional argument"),);
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
}
}
mod tilde_expansion {
use nu_test_support::nu;
#[test]
#[should_panic]
fn as_home_directory_when_passed_as_argument_and_begins_with_tilde() {
let actual = nu!(
cwd: ".",
r#"
echo ~
"#
);
assert!(!actual.out.contains('~'),);
}
#[test]
fn does_not_expand_when_passed_as_argument_and_does_not_start_with_tilde() {
let actual = nu!(
cwd: ".",
r#"
echo "1~1"
"#
);
assert_eq!(actual.out, "1~1");
}
}
mod variable_scoping {
use nu_test_support::nu;
macro_rules! test_variable_scope {
($func:literal == $res:literal $(,)*) => {
let actual = nu!(
cwd: ".",
$func
);
assert_eq!(actual.out, $res);
};
}
macro_rules! test_variable_scope_list {
($func:literal == $res:expr $(,)*) => {
let actual = nu!(
cwd: ".",
$func
);
let result: Vec<&str> = actual.out.matches("ZZZ").collect();
assert_eq!(result, $res);
};
}
#[test]
fn access_variables_in_scopes() {
test_variable_scope!(
r#" def test [input] { echo [0 1 2] | do { do { echo $input } } }
test ZZZ "#
== "ZZZ"
);
test_variable_scope!(
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
r#" def test [input] { echo [0 1 2] | do { do { if $input == "ZZZ" { echo $input } { echo $input } } } }
2022-02-07 20:11:34 +01:00
=======
r#" def test [input] { echo [0 1 2] | do { do { if $input == "ZZZ" { echo $input } else { echo $input } } } }
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
test ZZZ "#
== "ZZZ"
);
test_variable_scope!(
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
r#" def test [input] { echo [0 1 2] | do { do { if $input == "ZZZ" { echo $input } { echo $input } } } }
2022-02-07 20:11:34 +01:00
=======
r#" def test [input] { echo [0 1 2] | do { do { if $input == "ZZZ" { echo $input } else { echo $input } } } }
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
test ZZZ "#
== "ZZZ"
);
test_variable_scope!(
r#" def test [input] { echo [0 1 2] | do { echo $input } }
test ZZZ "#
== "ZZZ"
);
test_variable_scope!(
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
r#" def test [input] { echo [0 1 2] | do { if $input == $input { echo $input } { echo $input } } }
2022-02-07 20:11:34 +01:00
=======
r#" def test [input] { echo [0 1 2] | do { if $input == $input { echo $input } else { echo $input } } }
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
test ZZZ "#
== "ZZZ"
);
test_variable_scope_list!(
r#" def test [input] { echo [0 1 2] | each { echo $input } }
test ZZZ "#
== ["ZZZ", "ZZZ", "ZZZ"]
);
test_variable_scope_list!(
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
r#" def test [input] { echo [0 1 2] | each { if $it > 0 {echo $input} {echo $input}} }
2022-02-07 20:11:34 +01:00
=======
r#" def test [input] { echo [0 1 2] | each { if $it > 0 {echo $input} else {echo $input}} }
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
test ZZZ "#
== ["ZZZ", "ZZZ", "ZZZ"]
);
test_variable_scope_list!(
2022-02-07 20:11:34 +01:00
<<<<<<< HEAD
r#" def test [input] { echo [0 1 2] | each { if $input == $input {echo $input} {echo $input}} }
2022-02-07 20:11:34 +01:00
=======
r#" def test [input] { echo [0 1 2] | each { if $input == $input {echo $input} else {echo $input}} }
2022-02-07 20:11:34 +01:00
>>>>>>> 9259a56a28f1dd3a4b720ad815aa19c6eaf6adce
test ZZZ "#
== ["ZZZ", "ZZZ", "ZZZ"]
);
}
}