extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-10-16 23:33:49 +02:00
Code Issues Packages Projects Releases Wiki Activity
ab480856a5
nushell/crates/nu-command/Cargo.toml

166 lines
4.6 KiB
TOML
Raw Normal View History

nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
[package]
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 21:25:38 +01:00
authors = ["The Nushell Project Developers"]
Update incorrect crate descriptions (#5159)
2022-04-11 20:17:06 +02:00
description = "Nushell's built-in commands"
Add repository info to all workspace crates (#6320) This helps people who find these crates on crates.io
2022-08-14 14:21:20 +02:00
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-command"
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 21:25:38 +01:00
edition = "2021"
license = "MIT"
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
name = "nu-command"
Bump to `0.74.1` development version (#7721) # Description May be used for hotfix if needed
2023-01-11 22:30:41 +01:00
version = "0.74.1"
Port version (#467) * First iteration of the version command * Cleanup * Fix the installed plugins bug * Fix fmt check issue * Fix clippy warning * Fixing all clippy warnings * Remove old code
2021-12-11 21:08:17 +01:00
build = "build.rs"
Add nu-protocol
2021-09-02 03:29:43 +02:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
nu-color-config = { path = "../nu-color-config", version = "0.74.1" }
nu-engine = { path = "../nu-engine", version = "0.74.1" }
Bump to `0.74.1` development version (#7721) # Description May be used for hotfix if needed
2023-01-11 22:30:41 +01:00
nu-glob = { path = "../nu-glob", version = "0.74.1" }
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
nu-json = { path = "../nu-json", version = "0.74.1" }
nu-parser = { path = "../nu-parser", version = "0.74.1" }
nu-path = { path = "../nu-path", version = "0.74.1" }
nu-pretty-hex = { path = "../nu-pretty-hex", version = "0.74.1" }
nu-protocol = { path = "../nu-protocol", version = "0.74.1" }
nu-system = { path = "../nu-system", version = "0.74.1" }
nu-table = { path = "../nu-table", version = "0.74.1" }
nu-term-grid = { path = "../nu-term-grid", version = "0.74.1" }
Bump to `0.74.1` development version (#7721) # Description May be used for hotfix if needed
2023-01-11 22:30:41 +01:00
nu-utils = { path = "../nu-utils", version = "0.74.1" }
nu-explore = { path = "../nu-explore", version = "0.74.1" }
Update nu-ansi-term to remove `Deref` impl (#5706) Resolves an unexpected issue due to `Deref` and `ToString` interacting Details: https://github.com/nushell/nu-ansi-term/pull/5 and https://github.com/nushell/reedline/pull/435#issuecomment-1141348209 Also updates reedline: Includes a fix for a panic when the directory containing the history is deleted during a running reedline session. (nushell/reedline#436)
2022-06-03 21:38:54 +02:00
nu-ansi-term = "0.46.0"
upgrade num-format (#6694)
2022-10-10 13:25:57 +02:00
num-format = { version = "0.4.3" }
Add a very silly ls
2021-09-10 03:06:44 +02:00
# Potential dependencies for extras
enable cd to work with directory abbreviations (#5452) * enable cd to work with abbreviations * add abbreviation example * fix tests * make it configurable
2022-05-06 14:58:32 +02:00
alphanumeric-sort = "1.4.4"
Try to fix #7380 (#7446) fix https://github.com/nushell/nushell/issues/7380
2022-12-15 15:47:04 +01:00
atty = "0.2.14"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
base64 = "0.21.0"
Binary into int (#5941) * Add support for binary to into int * Add test
2022-07-03 20:31:50 +02:00
byteorder = "1.4.3"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
bytesize = "1.1.0"
couple minor updates to xml deps (#7311) # Description Just some minor updates to xml deps # 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.
2022-12-01 20:25:13 +01:00
calamine = "0.19.1"
print nushell startup time (#7831) # Description This PR shows the startup time and decreases the banner. This startup time output can be disabled with the `show_banner: false` setting in the config. This is the startup in debug mode. ![image](https://user-images.githubusercontent.com/343840/213955410-f319f8d4-1f96-47ae-8366-1c564a08d3e4.png) On my mac in release mode ``` Startup Time: 368ms 429µs 83ns ``` On my mac without a config as `nu --config foo --env-config foo` ``` Startup Time: 11ms 663µs 791ns ``` I could really go either way on this. If people don't like this change, we don't have to merge it. # User-Facing Changes Startup Time # 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-01-23 19:57:40 +01:00
chrono = { version = "0.4.23", features = ["unstable-locales", "std"], default-features = false }
Port date commands to engine-q
2021-10-31 07:54:51 +01:00
chrono-humanize = "0.2.1"
upgrade chrono to v0.4.20 (#6235)
2022-08-05 13:53:01 +02:00
chrono-tz = "0.6.3"
Update crossterm to version 0.24 (#6172) - Includes version bump for `lscolors = 0.11` and `reedline` as git patch
2022-07-30 11:41:15 +02:00
crossterm = "0.24.0"
bump csv crate to the latest 1.1.6 (#4939)
2022-03-24 18:59:27 +01:00
csv = "1.1.6"
Bump dialoguer from 0.9.0 to 0.10.3 (#7765)
2023-01-16 03:04:47 +01:00
dialoguer = { default-features = false, version = "0.10.3" }
removes unused features. (#6938) * removes unused features. * Adds back multithreading feature to sysinfo. * Adds back alloc for percent-encoding * Adds updated lock file. * Missed one sysinfo. * `indexmap` just defaults * Revert `miette``default-features=false` Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-11-12 06:44:56 +01:00
digest = { default-features = false, version = "0.10.0" }
Port str datetime to into datetime (#424) * Port str datetime to into datetime * Fix the span issue and some other small cleanups
2021-12-04 04:41:02 +01:00
dtparse = "1.2.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
eml-parser = "0.1.0"
encoding_rs = "0.8.30"
print nushell startup time (#7831) # Description This PR shows the startup time and decreases the banner. This startup time output can be disabled with the `show_banner: false` setting in the config. This is the startup in debug mode. ![image](https://user-images.githubusercontent.com/343840/213955410-f319f8d4-1f96-47ae-8366-1c564a08d3e4.png) On my mac in release mode ``` Startup Time: 368ms 429µs 83ns ``` On my mac without a config as `nu --config foo --env-config foo` ``` Startup Time: 11ms 663µs 791ns ``` I could really go either way on this. If people don't like this change, we don't have to merge it. # User-Facing Changes Startup Time # 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-01-23 19:57:40 +01:00
fancy-regex = "0.11.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
filesize = "0.2.0"
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
filetime = "0.2.15"
Re-port filesystem commands (#4387) * Re-port the filesystem commands * Remove commented out section
2022-02-09 15:56:27 +01:00
fs_extra = "1.2.0"
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
htmlescape = "0.3.1"
ical = "0.7.0"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
indexmap = { version = "1.7", features = ["serde-1"] }
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # 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 - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # 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. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
indicatif = "0.17.2"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
Inflector = "0.11"
Attempts to add a command that checks if nushell is running with admin priveleges (#5712) * attempts to add is-admin command * fmt and clippy * fmt * Update is_admin.rs * typos * typo in example
2022-06-06 13:55:23 +02:00
is-root = "0.1.2"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
itertools = "0.10.0"
log = "0.4.14"
print nushell startup time (#7831) # Description This PR shows the startup time and decreases the banner. This startup time output can be disabled with the `show_banner: false` setting in the config. This is the startup in debug mode. ![image](https://user-images.githubusercontent.com/343840/213955410-f319f8d4-1f96-47ae-8366-1c564a08d3e4.png) On my mac in release mode ``` Startup Time: 368ms 429µs 83ns ``` On my mac without a config as `nu --config foo --env-config foo` ``` Startup Time: 11ms 663µs 791ns ``` I could really go either way on this. If people don't like this change, we don't have to merge it. # User-Facing Changes Startup Time # 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-01-23 19:57:40 +01:00
lscolors = { version = "0.12.0", features = ["crossterm"], default-features = false }
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
md5 = { package = "md-5", version = "0.10.0" }
mime = "0.3.16"
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # 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.
2022-12-27 19:46:23 +01:00
mime_guess = "2.0.4"
Add watch command (#5331)
2022-04-28 16:26:34 +02:00
notify = "4.0.17"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
num = { version = "0.4.0", optional = true }
Add `bits shl` and `bits shr` command (#6202) * Add `bits shift-left` and `bits shift-right` command * update bits shift error tips * some code refactor * update shift right * some code refactor for bits shift commands * rename bits shift commands align with bits operators * update search term * Update crates/nu-command/src/bits/not.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * Update crates/nu-command/src/bits/shift_left.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * Update crates/nu-command/src/bits/shift_right.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * ci skip * change default number-bytes for bits shift * fix bits not tests * fix bits tests Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>
2022-08-02 22:52:04 +02:00
num-traits = "0.2.14"
Bump once_cell from 1.16.0 to 1.17.0 (#7732)
2023-01-12 00:00:44 +01:00
once_cell = "1.17"
let `start` open anything and everything (#7580) # Description Fixes #7546 's request. I'm unsure, so hopefully someone in charge of design can chip in. # User-Facing Changes `open` now opens directories in the default file manager. # 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-01-03 19:47:37 +01:00
open = "3.2.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
pathdiff = "0.2.1"
Update `powierza-coefficient` to `1.0.2` (#7625)
2022-12-29 15:55:00 +01:00
powierza-coefficient = "1.0.2"
Bump quick-xml from 0.25.0 to 0.27.1 (#7768)
2023-01-16 03:06:31 +01:00
quick-xml = "0.27"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
rand = "0.8"
Bump rayon from 1.5.3 to 1.6.1 (#7836) Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.5.3 to 1.6.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rayon-rs/rayon/blob/master/RELEASES.md">rayon's changelog</a>.</em></p> <blockquote> <h1>Release rayon 1.6.1 (2022-12-09)</h1> <ul> <li>Simplified <code>par_bridge</code> to only pull one item at a time from the iterator, without batching. Threads that are waiting for iterator items will now block appropriately rather than spinning CPU. (Thanks <a href="https://github.com/njaard"><code>@​njaard</code></a>!)</li> <li>Added protection against recursion in <code>par_bridge</code>, so iterators that also invoke rayon will not cause mutex recursion deadlocks.</li> </ul> <h1>Release rayon-core 1.10.1 (2022-11-18)</h1> <ul> <li>Fixed a race condition with threads going to sleep while a broadcast starts.</li> </ul> <h1>Release rayon 1.6.0 / rayon-core 1.10.0 (2022-11-18)</h1> <ul> <li>The minimum supported <code>rustc</code> is now 1.56.</li> <li>The new <code>IndexedParallelIterator::fold_chunks</code> and <code>fold_chunks_with</code> methods work like <code>ParallelIterator::fold</code> and <code>fold_with</code> with fixed-size chunks of items. This may be useful for predictable batching performance, without the allocation overhead of <code>IndexedParallelIterator::chunks</code>.</li> <li>New &quot;broadcast&quot; methods run a given function on all threads in the pool. These run at a sort of reduced priority after each thread has exhausted their local work queue, but before they attempt work-stealing from other threads. <ul> <li>The global <code>broadcast</code> function and <code>ThreadPool::broadcast</code> method will block until completion, returning a <code>Vec</code> of all return values.</li> <li>The global <code>spawn_broadcast</code> function and methods on <code>ThreadPool</code>, <code>Scope</code>, and <code>ScopeFifo</code> will run detached, without blocking the current thread.</li> </ul> </li> <li>Panicking methods now use <code>#[track_caller]</code> to report the caller's location.</li> <li>Fixed a truncated length in <code>vec::Drain</code> when given an empty range.</li> </ul> <h2>Contributors</h2> <p>Thanks to all of the contributors for this release!</p> <ul> <li><a href="https://github.com/cuviper"><code>@​cuviper</code></a></li> <li><a href="https://github.com/idanmuze"><code>@​idanmuze</code></a></li> <li><a href="https://github.com/JoeyBF"><code>@​JoeyBF</code></a></li> <li><a href="https://github.com/JustForFun88"><code>@​JustForFun88</code></a></li> <li><a href="https://github.com/kianmeng"><code>@​kianmeng</code></a></li> <li><a href="https://github.com/kornelski"><code>@​kornelski</code></a></li> <li><a href="https://github.com/ritchie46"><code>@​ritchie46</code></a></li> <li><a href="https://github.com/ryanrussell"><code>@​ryanrussell</code></a></li> <li><a href="https://github.com/steffahn"><code>@​steffahn</code></a></li> <li><a href="https://github.com/TheIronBorn"><code>@​TheIronBorn</code></a></li> <li><a href="https://github.com/willcrozi"><code>@​willcrozi</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rayon-rs/rayon/commit/401678ee554f90ab11abe70eb23737e26b489ddd"><code>401678e</code></a> Merge <a href="https://github-redirect.dependabot.com/rayon-rs/rayon/issues/709">#709</a></li> <li><a href="https://github.com/rayon-rs/rayon/commit/33e98434134f53fe18d222ea6824bb614942d290"><code>33e9843</code></a> Release rayon 1.2.1 / rayon-core 1.6.1</li> <li><a href="https://github.com/rayon-rs/rayon/commit/dd874ac5d45bb2b8bbb4e621a904bb40e36e1822"><code>dd874ac</code></a> Bump crate versions and dependencies</li> <li><a href="https://github.com/rayon-rs/rayon/commit/0c6338d2676485803db9406e964053232765a281"><code>0c6338d</code></a> Reduce Option complexity in demo cpu_time</li> <li><a href="https://github.com/rayon-rs/rayon/commit/be99e500bf08d8d83a835e7c755a629d31e97510"><code>be99e50</code></a> cargo fmt</li> <li><a href="https://github.com/rayon-rs/rayon/commit/9b4d9798def1ca954b8958fcd22b6a4088af3180"><code>9b4d979</code></a> Avoid mem::uninitialized in the demo cpu_time</li> <li><a href="https://github.com/rayon-rs/rayon/commit/5a466434abcf19107792937dbcc0b57a0b84c8ad"><code>5a46643</code></a> Avoid mem::uninitialized in par_sort_unstable</li> <li><a href="https://github.com/rayon-rs/rayon/commit/73b1061a2318e9cdb12cccfbbaafa5db3895f366"><code>73b1061</code></a> Merge <a href="https://github-redirect.dependabot.com/rayon-rs/rayon/issues/705">#705</a></li> <li><a href="https://github.com/rayon-rs/rayon/commit/54c0b0dc0c7d847eacf18bc3db8f363dafe688bc"><code>54c0b0d</code></a> Make sure that compat-Cargo.lock is fresh</li> <li><a href="https://github.com/rayon-rs/rayon/commit/4fd13b033424be5eac826571e017b1a008d0bd06"><code>4fd13b0</code></a> Regenerate compat-Cargo.lock</li> <li>Additional commits viewable in <a href="https://github.com/rayon-rs/rayon/compare/v1.5.3...rayon-core-v1.6.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rayon&package-manager=cargo&previous-version=1.5.3&new-version=1.6.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-01-23 05:52:37 +01:00
rayon = "1.6.1"
Bump regex from 1.6.0 to 1.7.1 (#7833)
2023-01-23 02:44:10 +01:00
regex = "1.7.1"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
reqwest = { version = "0.11", features = ["blocking", "json"] }
couple minor updates to xml deps (#7311) # Description Just some minor updates to xml deps # 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.
2022-12-01 20:25:13 +01:00
roxmltree = "0.16.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
rust-embed = "6.3.0"
Fix mv data loss when changing folder case (step 1) (#6599) * Fix mv data loss when changing folder case (step 1) * Use same-file to detect when changing case on Windows
2022-09-23 20:09:31 +02:00
same-file = "1.0.6"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
serde = { version = "1.0.123", features = ["derive"] }
`from vcf` `from ics` and `from ini` (#367) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from toml` command * From ods * From XLSX * From ics * From ini * From vcf * Forgot a eprintln!
2021-11-25 18:10:56 +01:00
serde_ini = "0.2.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
serde_urlencoded = "0.7.0"
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 21:56:15 +02:00
serde_yaml = "0.9.4"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
sha2 = "0.10.0"
Look up git commit hash ourselves, drop libgit2 dependency (#5548)
2022-05-16 03:57:25 +02:00
# Disable default features b/c the default features build Git (very slow to compile)
Bump shadow-rs from 0.16.3 to 0.20.0 (#7837)
2023-01-23 02:55:51 +01:00
shadow-rs = { version = "0.20.0", default-features = false }
Bump sysinfo from 0.26.4 to 0.27.7 (#7839)
2023-01-23 04:09:15 +01:00
sysinfo = "0.27.7"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
terminal_size = "0.2.1"
update crate thiserror to version 1.0.31 in crates nu-cli, nu-command, nu-parser, nu-protocol (#5919)
2022-06-30 22:55:01 +02:00
thiserror = "1.0.31"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
titlecase = "2.0.0"
`from xlsx` `from ods` and `from toml` (#352) * MathEval Variance and Stddev * Fix tests and linting * Typo * Deal with streams when they are not tables * `from toml` command * From ods * From XLSX
2021-11-19 20:23:35 +01:00
toml = "0.5.8"
allow icons to be used in `grid -c` (#378) * add icons to grid output. still needs cleanup * working but adds a dependency on ansi_term - need to fix that * update styling, added lots of green code to icons * clippy * add config point for grid icons
2021-11-29 21:37:09 +01:00
unicode-segmentation = "1.8.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
url = "2.2.1"
Url encode to escape special characters (#7664) Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com> Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>
2023-01-05 19:24:38 +01:00
percent-encoding = "2.2.0"
Bump uuid from 1.1.2 to 1.2.2 (#7734)
2023-01-12 13:48:49 +01:00
uuid = { version = "1.2.2", features = ["v4"] }
Upgrade `which` dependency to fix case on Windows (#6453)
2022-08-31 18:50:18 +02:00
which = { version = "4.3.0", optional = true }
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
reedline = { version = "0.14.0", features = ["bashisms", "sqlite"] }
wax = { version = "0.5.0" }
update some dependencies (#6131)
2022-07-26 04:09:32 +02:00
rusqlite = { version = "0.28.0", features = ["bundled"], optional = true }
update sqlparser dependency (#7772) # Description This PR updates the `sqlparser` dependency and updates code to the latest api changes. # User-Facing 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-01-16 04:30:39 +01:00
sqlparser = { version = "0.30.0", features = ["serde"], optional = true }
Complete Dataframe MVP (#3373) * Dataframe MVP * Removed test csv file * Dataframe MVP * Removed test csv file * New revision polars * New revision polars * csv file reader * argument parser for file reader * Parser from Row primitive * Column conversion * Added as f32 and f64 * Parsing row to dataframe * Removed repeated push to vector * Accept table values to create dataframe * Removed default serde * Dataframe to rows to show data * Save name of file with dataframe * Usage example * Upgrade polars version * Clippy changes * Added print function with head and tail * Move dataframe struct to folder * Lock file after running tests and merge * Optional feature for dataframe * Removed dataframe from plugins * Update primitive.rs Co-authored-by: JT <jonathandturner@users.noreply.github.com>
2021-05-12 03:01:31 +02:00
add a new command to query the registry on windows (#6670) * add a new command to query the registry on windows * cross platform tweaks * return nushell datatype * change visibility of exec and registry commands
2022-10-07 20:54:36 +02:00
[target.'cfg(windows)'.dependencies]
winreg = "0.10.1"
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
[target.'cfg(unix)'.dependencies]
nu-command ls - bump umask crate to 2.0.0 (#5514)
2022-05-11 23:13:45 +02:00
umask = "2.0.0"
Update some deps (#3011)
2021-02-05 21:54:54 +01:00
users = "0.11.0"
fix: fixcd (#6799) * fix: fixcd try to fix Log: try to fix the bug with can enter a permisson error fold * change wording * fat * fmt Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2022-11-04 19:38:39 +01:00
libc = "0.2"
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
Termux/Android target support for v0.60.0 (#4956) * Add android as target os for procfs-based ps * Turn off code for dealing with trash on platforms which are known to not support a standard trash protocol * Update lib.rs * Update lib.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-26 19:21:19 +01:00
[target.'cfg(not(any(target_os = "android", target_os = "ios")))'.dependencies.trash]
Upgrade `windows` and `trash` crates (#7259) This upgrades the `windows` and `trash` crates so we are only compiling 1 version of the `windows` crate ([I recently upgraded the version used in `trash`](https://github.com/Byron/trash-rs/pull/58)). I was hoping that this would lead to some decent compile time improvements, but unfortunately it did not. Compiling 1 version of `windows` with all the features unified is about as slow as compiling 2 versions with distinct feature sets. Still, might as well upgrade.
2022-11-29 22:05:32 +01:00
version = "3.0.0"
Termux/Android target support for v0.60.0 (#4956) * Add android as target os for procfs-based ps * Turn off code for dealing with trash on platforms which are known to not support a standard trash protocol * Update lib.rs * Update lib.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-26 19:21:19 +01:00
optional = true
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
[dependencies.polars]
dependency update: update polar to 0.26.1 (#7743) # Description As title # User-Facing 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-01-13 16:27:37 +01:00
version = "0.26.1"
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
optional = true
Migration of series commands (#515) * corrected missing shellerror type * batch dataframe commands * removed option to find declaration with input * ordered dataframe folders * dataframe command name * series commands * date commands * series commands * series commands * clippy correction * rename commands
2021-12-18 18:45:09 +01:00
features = [
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 14:06:31 +02:00
"arg_where",
"checked_arithmetic",
"concat_str",
"cross_join",
"csv-file",
"cum_agg",
"default",
"dtype-datetime",
"dtype-struct",
"dtype-categorical",
"dynamic_groupby",
Support Arrow IPC file format with dataframes (#6548) * Add support for Arrow IPC file format Add support for Arrow IPC file format to dataframes commands. Support opening of Arrow IPC-format files with extension '.arrow' or '.ipc' in the open-df command. Add a 'to arrow' command to write a dataframe to Arrow IPC format. * Add unit test for open-df on Arrow * Add -t flag to open-df command Add a `--type`/`-t` flag to the `open-df` command, to explicitly specify the type of file being used. Allowed values are the same at the set of allowed file extensions.
2022-09-13 01:30:20 +02:00
"ipc",
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 14:06:31 +02:00
"is_in",
"json",
"lazy",
"object",
"parquet",
"random",
"rolling_window",
"rows",
"serde",
"serde-lazy",
"strings",
"strings",
"to_dummies",
Migration of series commands (#515) * corrected missing shellerror type * batch dataframe commands * removed option to find declaration with input * ordered dataframe folders * dataframe command name * series commands * date commands * series commands * series commands * clippy correction * rename commands
2021-12-18 18:45:09 +01:00
]
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
Fix `ls` for Windows system files (#5703) * Fix `ls` for Windows system files * Fix non-Windows builds * Make Clippy happy on non-Windows platforms * Fix new test on GitHub runners * Move ls Windows code into its own module
2022-06-03 18:37:27 +02:00
[target.'cfg(windows)'.dependencies.windows]
Upgrade `windows` and `trash` crates (#7259) This upgrades the `windows` and `trash` crates so we are only compiling 1 version of the `windows` crate ([I recently upgraded the version used in `trash`](https://github.com/Byron/trash-rs/pull/58)). I was hoping that this would lead to some decent compile time improvements, but unfortunately it did not. Compiling 1 version of `windows` with all the features unified is about as slow as compiling 2 versions with distinct feature sets. Still, might as well upgrade.
2022-11-29 22:05:32 +01:00
version = "0.43.0"
print nushell startup time (#7831) # Description This PR shows the startup time and decreases the banner. This startup time output can be disabled with the `show_banner: false` setting in the config. This is the startup in debug mode. ![image](https://user-images.githubusercontent.com/343840/213955410-f319f8d4-1f96-47ae-8366-1c564a08d3e4.png) On my mac in release mode ``` Startup Time: 368ms 429µs 83ns ``` On my mac without a config as `nu --config foo --env-config foo` ``` Startup Time: 11ms 663µs 791ns ``` I could really go either way on this. If people don't like this change, we don't have to merge it. # User-Facing Changes Startup Time # 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-01-23 19:57:40 +01:00
features = ["Win32_Foundation", "Win32_Storage_FileSystem", "Win32_System_SystemServices"]
Fix `ls` for Windows system files (#5703) * Fix `ls` for Windows system files * Fix non-Windows builds * Make Clippy happy on non-Windows platforms * Fix new test on GitHub runners * Move ls Windows code into its own module
2022-06-03 18:37:27 +02:00
add rm command + stubs for open and save
2021-10-10 06:13:15 +02:00
[features]
trash-support = ["trash"]
Fix which-support feature (#5038)
2022-03-30 20:37:31 +02:00
which-support = ["which"]
plugin feature flag
2021-11-02 21:56:00 +01:00
plugin = ["nu-parser/plugin"]
Remove sqlparser SQLite commands (#7040)
2022-11-09 23:14:48 +01:00
dataframe = ["polars", "num", "sqlparser"]
print nushell startup time (#7831) # Description This PR shows the startup time and decreases the banner. This startup time output can be disabled with the `show_banner: false` setting in the config. This is the startup in debug mode. ![image](https://user-images.githubusercontent.com/343840/213955410-f319f8d4-1f96-47ae-8366-1c564a08d3e4.png) On my mac in release mode ``` Startup Time: 368ms 429µs 83ns ``` On my mac without a config as `nu --config foo --env-config foo` ``` Startup Time: 11ms 663µs 791ns ``` I could really go either way on this. If people don't like this change, we don't have to merge it. # User-Facing Changes Startup Time # 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-01-23 19:57:40 +01:00
sqlite = ["rusqlite"] # TODO: given that rusqlite is included in reedline, should we just always include it?
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
[build-dependencies]
Bump shadow-rs from 0.16.3 to 0.20.0 (#7837)
2023-01-23 02:55:51 +01:00
shadow-rs = { version = "0.20.0", default-features = false }
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
[dev-dependencies]
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
nu-test-support = { path = "../nu-test-support", version = "0.74.1" }
Move nu-test-support into dev deps on nu-command (#6940) This reduces the number of dependencies to build for `cargo build` or `cargo run` by around 19. Will not speed up CI as we need to `cargo test` but should help for `cargo install` or users just building from source. Time saved on my machine ~0.8 secs so likely unnoticable in noise. Larger future goal is reducing longer dependency chains to allow more parallel compilation.
2022-10-29 19:39:27 +02:00
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
hamcrest2 = "0.3.0"
dirs-next = "2.0.0"
add tests, deal with pipes, newlines, tabs for `to nuon` (#6391) * remove unnecessary FlatShape * add proptest * remove files that belonged in another PR * more tests, more chars * add exception for parser error unrelated ot PR
2022-09-01 14:08:19 +02:00
proptest = "1.0.0"
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
quickcheck = "1.0.3"
list keybinding options (#906) * list keybinding optins * list keybinding options * clippy error
2022-02-04 07:47:18 +01:00
quickcheck_macros = "1.0.0"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # 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-01-13 14:16:14 +01:00
rstest = { version = "0.15.0", default-features = false }
Reference in New Issue Copy Permalink