History

Darren Schroeder 616f065324 make std.nu tests work on mac (#8576 ) # Description This PR is to make test_dirs.nu work better on macos. closes #8528 # User-Facing Changes _(List of all changes that impact the user experience here. This helps us keep track of breaking changes.)_ # 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 > 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-03-23 07:08:01 -05:00
..
README.md	standard library: fix the readme (#8526 )	2023-03-20 17:05:49 +13:00
std.nu	stdlib: Implement common assert commands (#8515 )	2023-03-20 08:57:28 -05:00
test_asserts.nu	stdlib: Implement common assert commands (#8515 )	2023-03-20 08:57:28 -05:00
test_dirs.nu	make std.nu tests work on mac (#8576 )	2023-03-23 07:08:01 -05:00
test_logger.nu	stdlib: Implement common assert commands (#8515 )	2023-03-20 08:57:28 -05:00
test_std.nu	stdlib: Implement common assert commands (#8515 )	2023-03-20 08:57:28 -05:00
tests.nu	std lib: extend test runner capabilities (#8499 )	2023-03-20 18:48:48 +01:00

README.md

Welcome to the standard library of `nushell`!

The standard library is a pure-nushell collection of commands to allow anyone to build complex applications using standardized tools gathered incrementally.

In this library, you might find rust-like assert commands to write tests, tools to manipulate paths and strings, etc, etc, ...

🧰 use the standard library in the REPL or in scripts

in order to "import" the standard library to either the interactive REPL of nushell or inside some .nu script, you might want to use the use command!

use /path/to/standard_library/std.nu

🔍 a concrete example

my name is @amtoine and i use the ghq tool to manage git projects

Note

ghq stores any repository inside $env.GHQ_ROOT under <host>/<owner>/<repo>/

the path to my local fork of nushell is then defined as
let-env NUSHELL_REPO = ($env.GHQ_ROOT | path join "github.com" "amtoine" "nushell")
and the full path to the standard library is defined as
let-env STD_LIB = ($env.NUSHELL_REPO | path join "crates" "nu-utils" "standard_library")
see the content of $env.STD_LIB 😋
>_ ls $env.STD_LIB | get name | str replace $env.STD_LIB "" | str trim -l -c "/"
╭───┬───────────╮
│ 0 │ README.md │
│ 1 │ std.nu    │
│ 2 │ tests.nu  │
╰───┴───────────╯
finally we can use the standard library and have access to the commands it exposes 👍
>_ use std.nu
>_ help std
Module: std

Exported commands:
  assert (std assert), assert eq (std assert eq), assert ne (std assert ne), match (std match)

This module does not export environment.

✏️ contribute to the standard library

all the commands of the standard_library are located in std.nu
the tests are located in files that have a name starting with "test_", e.g. test_std.nu
a test runner, at tests.nu, allows to run all the tests automatically

🔧 add new commands

add new standard commands by appending to std.nu
add associated tests to test_std.nu or preferably to test_<submodule>.nu.
- define a new exported (!) test_<feature> command
- import the assert functions you need at the top of the functions, e.g. use std.nu "assert eq"

🧪 run the tests

the following call should return no errors

NU_LOG_LEVEL=DEBUG nu /path/to/standard_library/tests.nu

🔍 a concrete example

with STD_LIB defined as in the example above
NU_LOG_LEVEL=DEBUG nu ($env.STD_LIB | path join "tests.nu")