mirror of
https://github.com/nushell/nushell.git
synced 2024-12-25 08:29:07 +01:00
222c0f11c3
# Description Fixes the issue where there is no way to escape `FOO=BAR` in a way that treats it as a file path/executable name. Previously `^FOO=BAR` would be handled as an environment shorthand. Now, environment shorthands are not allowed to start with `^`. To create an environment shorthand value that uses `^` as the first character of the environment variable name, use quotes, eg `"^FOO"=BAR` # User-Facing Changes This should enable `=` being in paths and external command names in command position. # 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. |
||
|---|---|---|
| .. | ||
| assets/nu_json | ||
| const_ | ||
| fixtures | ||
| hooks | ||
| modules | ||
| overlays | ||
| parsing | ||
| path | ||
| plugins | ||
| scope | ||
| shell | ||
| main.rs | ||