mirror of
https://github.com/nushell/nushell.git
synced 2025-05-05 23:42:56 +00:00
4fe7865ad0
# Description This PR allows the `into string` command to pass the `--group-digits` flag which already existed in this code but was hard coded to `false`. Now you can do things like ```nushell ❯ 1234567890 | into string --group-digits 1,234,567,890 ❯ ls | into string size --group-digits | last 5 ╭─#─┬────────name─────────┬─type─┬──size──┬───modified───╮ │ 0 │ README.md │ file │ 12,606 │ 4 weeks ago │ │ 1 │ rust-toolchain.toml │ file │ 1,125 │ 2 weeks ago │ │ 2 │ SECURITY.md │ file │ 2,712 │ 7 months ago │ │ 3 │ toolkit.nu │ file │ 21,929 │ 2 months ago │ │ 4 │ typos.toml │ file │ 542 │ 7 months ago │ ╰─#─┴────────name─────────┴─type─┴──size──┴───modified───╯ ❯ "12345" | into string --group-digits 12,345 ``` # 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` 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 > ``` --> # 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. -->
Nushell core libraries and plugins
These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.
Foundational libraries are split into two kinds of crates:
- Core crates - those crates that work together to build the Nushell language engine
- Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.
Plugins are likewise also split into two types:
- Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
- Extra plugins - these plugins run a wide range of different capabilities like working with different file types, charting, viewing binary data, and more.