forked from extern/nushell
18fdc5a229
# Description Closes: #8108 Adding a new `-b` flag to `rename` command. I have thought about making it as a positional argument, but I don't think it's ok because we alredy have `...rest` parameters Here are how they works: ``` # Rename fields based on a given closure > {a: 1, b: 2} | rename -b {str upcase} ╭───┬───╮ │ A │ 1 │ │ B │ 2 │ ╰───┴───╯ # Rename fields based on fields' value > {a: abc, b: def} | rename -b {|it| $it.value | str upcase} ╭─────┬─────╮ │ ABC │ abc │ │ DEF │ def │ ╰─────┴─────╯ ``` # User-Facing 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 - `cargo run -- crates/nu-std/tests/run.nu` 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. --> |
||
|---|---|---|
| .. | ||
| assets | ||
| src | ||
| tests | ||
| Cargo.toml | ||
| LICENSE | ||