chore: Add nu_plugin_polars to build and install scripts (#13550)

- 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.
-->
This commit is contained in:
kurokirasama 2024-08-06 16:23:56 -04:00 committed by GitHub
parent eca2975b3d
commit 926331dbfb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
5 changed files with 5 additions and 0 deletions

View File

@ -16,6 +16,7 @@ NU_PLUGINS=(
'nu_plugin_inc' 'nu_plugin_inc'
'nu_plugin_query' 'nu_plugin_query'
'nu_plugin_custom_values' 'nu_plugin_custom_values'
'nu_plugin_polars'
) )
echo "Building nushell" echo "Building nushell"

View File

@ -33,6 +33,7 @@ let plugins = [
nu_plugin_example, nu_plugin_example,
nu_plugin_custom_values, nu_plugin_custom_values,
nu_plugin_formats, nu_plugin_formats,
nu_plugin_polars
] ]
for plugin in $plugins { for plugin in $plugins {

View File

@ -17,6 +17,7 @@ $NU_PLUGINS = @(
'nu_plugin_query', 'nu_plugin_query',
'nu_plugin_custom_values', 'nu_plugin_custom_values',
'nu_plugin_formats' 'nu_plugin_formats'
'nu_plugin_polars'
) )
foreach ( $plugin in $NU_PLUGINS) { foreach ( $plugin in $NU_PLUGINS) {

View File

@ -21,6 +21,7 @@ NU_PLUGINS=(
'nu_plugin_example' 'nu_plugin_example'
'nu_plugin_custom_values' 'nu_plugin_custom_values'
'nu_plugin_formats' 'nu_plugin_formats'
'nu_plugin_polars'
) )
for plugin in "${NU_PLUGINS[@]}" for plugin in "${NU_PLUGINS[@]}"

View File

@ -14,6 +14,7 @@ NU_PLUGINS=(
'nu_plugin_example' 'nu_plugin_example'
'nu_plugin_formats' 'nu_plugin_formats'
'nu_plugin_custom_values' 'nu_plugin_custom_values'
'nu_plugin_polars'
) )
cargo uninstall nu cargo uninstall nu