1072bd06c3
# Description Mention the expected substring in: - `fn run_test_contains()` - `fn test_ide_contains()` - `fn fail_test()` # Developer-Facing Changes You can read the test failure to figure out what is going on, don't necessarily have to look up the test New look of failure ``` failures: ---- tests::test_math::broken_math stdout ---- stdout: stderr: Error: nu::parser::incomplete_math_expression × Incomplete math expression. ╭─[/tmp/.tmpz0V8nC:1:1] 1 │ 3 + · ┬ · ╰── incomplete math expression ╰──── Expected error to contain: Incomplete universe thread 'tests::test_math::broken_math' panicked at 'assertion failed: !stderr.is_empty() && stderr.contains(expected)', src/tests.rs:181:5 ``` |
||
|---|---|---|
| .. | ||
| tests | ||
| command.rs | ||
| config_files.rs | ||
| ide.rs | ||
| logger.rs | ||
| main.rs | ||
| README.md | ||
| run.rs | ||
| signals.rs | ||
| terminal.rs | ||
| test_bins.rs | ||
| tests.rs | ||
Nushell REPL
This directory contains the main Nushell REPL (read eval print loop) as part of the CLI portion of Nushell, which creates the nu binary itself.
Current versions of the nu binary will use the Nu argument parsing logic to parse the commandline arguments passed to nu, leaving the logic here to be a thin layer around what the core libraries.