mirror of
https://github.com/nushell/nushell.git
synced 2024-11-07 09:04:18 +01:00
926331dbfb
- Add `nu_plugin_polars` to the list of plugins in `build-all-maclin.sh`. - Add `nu_plugin_polars` to the list of plugins in `build-all.nu`. - Add `nu_plugin_polars` to the list of plugins in `install-all.ps1`. - Add `nu_plugin_polars` to the list of plugins in `install-all.sh`. - Add `nu_plugin_polars` to the list of plugins in `uninstall-all.sh`. <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> # 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. --> |
||
---|---|---|
.. | ||
build-all-maclin.sh | ||
build-all-windows.cmd | ||
build-all.nu | ||
build.rs | ||
coverage-local.nu | ||
coverage-local.sh | ||
install-all.ps1 | ||
install-all.sh | ||
README.md | ||
test_virtualenv.nu | ||
uninstall-all.sh |
run the scripts
Note
the following table must be read as follows:
- an
x
means it works- a
?
means no data available
.nu
scripts must be run asnu .../foo.nu
.sh
scripts must be run as./.../foo.sh
.ps1
scripts must be run aspowershell .../foo.ps1
let's say a script is called
foo
- an
x
in the./scripts
column meansfoo
can be run from./scripts
- an
x
in the root column meansfoo
can be run from the root ofnushell
- an
x
in the anywhere column meansfoo
can be run from anywhere!
script | ./scripts/ |
root | anywhere |
---|---|---|---|
build-all-maclin.sh |
x | x | x |
build-all-windows.cmd |
? | x | ? |
build-all.nu |
x | x | x |
coverage-local.nu |
x | x | x |
coverage-local.sh |
x | x | x |
install-all.ps1 |
? | x | ? |
install-all.sh |
x | x | x |
uninstall-all.sh |
x | x | x |