mirror of
https://github.com/nushell/nushell
synced 2024-12-28 14:03:09 +00:00
8f4feeb119
# Description This is supposed to be a Quality-of-Life command that just makes some things easier when dealing with a nushell config. Really all it does is show you the current config in a flattened state. That's it. I was thinking this could be useful when comparing config settings between old and new config files. There are still room for improvements. For instance, closures are listed as an int. They can be updated with a `view source <int>` pipeline but that could all be built in too. ![image](https://github.com/user-attachments/assets/5d8981a3-8d03-4eb3-8361-2f3c3c560660) The command works by getting the current configuration, serializing it to json, then flattening that json. BTW, there's a new flatten_json.rs in nu-utils. Theoretically all this mess could be done in a custom command script, but it's proven to be exceedingly difficult based on the work from discord. Here's some more complex items to flatten. ![image](https://github.com/user-attachments/assets/b44e2ec8-cf17-41c4-bf8d-7f26317db071) # 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. -->
42 lines
1 KiB
TOML
42 lines
1 KiB
TOML
[package]
|
|
authors = ["The Nushell Project Developers"]
|
|
description = "Nushell utility functions"
|
|
edition = "2021"
|
|
license = "MIT"
|
|
name = "nu-utils"
|
|
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-utils"
|
|
version = "0.100.1"
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
[[bin]]
|
|
name = "utils"
|
|
path = "src/main.rs"
|
|
bench = false
|
|
|
|
[lib]
|
|
bench = false
|
|
|
|
[dependencies]
|
|
crossterm = { workspace = true, optional = true }
|
|
fancy-regex = { workspace = true }
|
|
lscolors = { workspace = true, default-features = false, features = ["nu-ansi-term"] }
|
|
log = { workspace = true }
|
|
num-format = { workspace = true }
|
|
strip-ansi-escapes = { workspace = true }
|
|
serde = { workspace = true }
|
|
serde_json = { workspace = true }
|
|
sys-locale = "0.3"
|
|
unicase = "2.8.0"
|
|
|
|
[features]
|
|
default = ["os"]
|
|
os = ["crossterm"]
|
|
|
|
[target.'cfg(windows)'.dependencies]
|
|
crossterm_winapi = "0.9"
|
|
|
|
[target.'cfg(unix)'.dependencies]
|
|
nix = { workspace = true, default-features = false, features = ["user", "fs"] }
|
|
|
|
[lints]
|
|
workspace = true
|