mirror of
https://github.com/nushell/nushell.git
synced 2024-11-25 01:43:47 +01:00
664dd291eb
# Description This PR reverts some changes to NU_LIB_DIRS and NU_PLUGIN_DIRS in the default_env.config file. Our practice is to have default configs that match if you were to run `nu -n`. I agree with this goal, but until someone adds NU_LIB_DIRS and NU_PLUGIN_DIRS, we should revert this change and not penalize users, breaking their scripts that run with `nu -c blah` when `blah` is located in the default_env's NU_LIB_DIRS. # 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 std testing; testing run-tests --path crates/nu-std"` 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. --> |
||
|---|---|---|
| .. | ||
| src | ||
| .gitignore | ||
| Cargo.toml | ||
| LICENSE | ||