nushell/scripts/install-all.ps1

32 lines
966 B
PowerShell
Raw Normal View History

# Usage: Just run `powershell install-all.ps1` in nushell root directory
Write-Output "-----------------------------------------------------------------"
Write-Output "Installing nushell (nu) and all the plugins"
Write-Output "-----------------------------------------------------------------"
Write-Output ""
Write-Output "Install nushell from local..."
Write-Output "----------------------------------------------"
cargo install --force --path . --locked
2022-08-11 16:40:35 +02:00
$NU_PLUGINS = @(
'nu_plugin_example',
'nu_plugin_gstat',
'nu_plugin_inc',
2022-08-11 16:40:35 +02:00
'nu_plugin_query',
Move some `from xxx` commands to plugin (#7942) # Description From nushell 0.8 philosophy: https://github.com/nushell/nushell.github.io/blob/main/contributor-book/philosophy_0_80.md#core-categories > The following categories should be moved to plugins: Uncommon format support So this pr is trying to move following commands to plugin: - [X] from eml - [x] from ics - [x] from ini - [x] from vcf And we can have a new plugin handles for these formatting, currently it's implemented here: https://github.com/WindSoilder/nu_plugin_format The command usage should be the same to original command. If it's ok, the plugin can support more formats like [parquet](https://github.com/fdncred/nu_plugin_from_parquet), or [EDN format](https://github.com/nushell/nushell/issues/6415), or something else. Just create a draft pr to show what's the blueprint looks like, and is it a good direction to move forward? # 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 -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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.
2023-02-13 13:42:08 +01:00
'nu_plugin_custom_values',
'nu_plugin_formats'
)
2022-08-11 16:40:35 +02:00
foreach ( $plugin in $NU_PLUGINS) {
Write-Output ''
Write-Output "----------------------------------------------"
Write-Output "Install plugin $plugin from local..."
Write-Output "----------------------------------------------"
Set-Location crates/$plugin
cargo install --force --path .
Set-Location ../../
}