Mirrors/nushell
2
0
Fork 0
mirror of https://github.com/nushell/nushell synced 2024-12-28 22:13:10 +00:00
Code Issues Projects Releases Packages Wiki Activity
nushell/crates/nu-command/Cargo.toml

170 lines
4.7 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 04:59:53 +00:00
[package]
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 20:25:38 +00:00
authors = ["The Nushell Project Developers"]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
build = "build.rs"
Update incorrect crate descriptions (#5159)
2022-04-11 18:17:06 +00:00
description = "Nushell's built-in commands"
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 20:25:38 +00: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 04:59:53 +00:00
name = "nu-command"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-command"
Update to `0.76.1` version for development (#8161) # Description For tracking in `version` for bug reports during development. Might be used for an urgent hotfix if necessary.
2023-02-21 23:21:39 +00:00
version = "0.76.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 20:08:17 +00:00
Add nu-protocol
2021-09-02 01:29:43 +00:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
Disable auto-benchmark harness for crates (#8057) # Description This disables automatic detection of `#[bench]` and other benchmarks within the crates. Our benchmarks should all live in `benches` This fixes a problem with criterion flags and should also reduce the build requirements for `cargo bench` a bit Taken from https://github.com/nushell/nushell/pull/7952 See: https://bheisler.github.io/criterion.rs/book/faq.html#cargo-bench-gives-unrecognized-option-errors-for-valid-command-line-options # User-Facing Changes None
2023-02-12 22:22:00 +00:00
[lib]
bench = false
Add nu-protocol
2021-09-02 01:29:43 +00:00
[dependencies]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
nu-ansi-term = "0.46.0"
Cratification: Break out nu_cmd_lang into a separate crate (#8181) # Description This breaks out the core_commands into a separate crate called nu_cmd_lang _(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 -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-24 15:54:42 +00:00
nu-cmd-lang = { path = "../nu-cmd-lang", version = "0.76.1" }
Update to `0.76.1` version for development (#8161) # Description For tracking in `version` for bug reports during development. Might be used for an urgent hotfix if necessary.
2023-02-21 23:21:39 +00:00
nu-color-config = { path = "../nu-color-config", version = "0.76.1" }
nu-engine = { path = "../nu-engine", version = "0.76.1" }
nu-explore = { path = "../nu-explore", version = "0.76.1" }
nu-glob = { path = "../nu-glob", version = "0.76.1" }
nu-json = { path = "../nu-json", version = "0.76.1" }
nu-parser = { path = "../nu-parser", version = "0.76.1" }
nu-path = { path = "../nu-path", version = "0.76.1" }
nu-pretty-hex = { path = "../nu-pretty-hex", version = "0.76.1" }
nu-protocol = { path = "../nu-protocol", version = "0.76.1" }
nu-system = { path = "../nu-system", version = "0.76.1" }
nu-table = { path = "../nu-table", version = "0.76.1" }
nu-term-grid = { path = "../nu-term-grid", version = "0.76.1" }
nu-utils = { path = "../nu-utils", version = "0.76.1" }
upgrade num-format (#6694)
2022-10-10 11:25:57 +00:00
num-format = { version = "0.4.3" }
Add a very silly ls
2021-09-10 01:06:44 +00:00
# Potential dependencies for extras
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
Inflector = "0.11"
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 12:58:32 +00:00
alphanumeric-sort = "1.4.4"
Try to fix #7380 (#7446) fix https://github.com/nushell/nushell/issues/7380
2022-12-15 14:47:04 +00: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 13:16:14 +00:00
base64 = "0.21.0"
Binary into int (#5941) * Add support for binary to into int * Add test
2022-07-03 18:31:50 +00:00
byteorder = "1.4.3"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00: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 19:25:13 +00:00
calamine = "0.19.1"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
chrono = { version = "0.4.23", features = ["std", "unstable-locales"], default-features = false }
Port date commands to engine-q
2021-10-31 06:54:51 +00:00
chrono-humanize = "0.2.1"
Bump chrono-tz from 0.6.3 to 0.8.1 (#7907)
2023-01-30 01:38:39 +00:00
chrono-tz = "0.8.1"
Update crossterm to version 0.24 (#6172) - Includes version bump for `lscolors = 0.11` and `reedline` as git patch
2022-07-30 09:41:15 +00:00
crossterm = "0.24.0"
bump csv crate to the latest 1.1.6 (#4939)
2022-03-24 17:59:27 +00:00
csv = "1.1.6"
Bump dialoguer from 0.9.0 to 0.10.3 (#7765)
2023-01-16 02:04:47 +00: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 05:44:56 +00: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 03:41:02 +00:00
dtparse = "1.2.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00:00
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 18:57:40 +00:00
fancy-regex = "0.11.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00: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 11:44:05 +00:00
filetime = "0.2.15"
Bump fs_extra from 1.2.0 to 1.3.0 (#7976)
2023-02-06 09:59:58 +00:00
fs_extra = "1.3.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 04:59:53 +00:00
htmlescape = "0.3.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 13:16:14 +00: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 01:57:48 +00:00
indicatif = "0.17.2"
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 11:55:23 +00:00
is-root = "0.1.2"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00: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 18:57:40 +00:00
lscolors = { version = "0.12.0", features = ["crossterm"], default-features = false }
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00: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 18:46:23 +00:00
mime_guess = "2.0.4"
Dependency update: update notify version to v5 (#8114) # Description Relative: #8060 While investigating, I found we need to update notify, which is a good step to remove some duplicate dependencies. As title, here are some goods and bads after updating: ## Good keep dependency up to date, and remove duplidate dependency(cfg-if, winapi) in Cargo.lock. ## Bad Introduce some breaking changes: After updating to notify v5, I found that we have to remove `Rename` events. But I've testing under notify v4, and it doesn't work good if we running the following command on MacOS: ``` touch a mv a b ``` It fires file create event, but no file rename event. So `rename` event is not really reliable, so I think it's ok for us to remove `Rename` events. The reason to remove `--debounce-ms` flag: It's not provided by defualt file watcher, we can use [PollWatcher](https://docs.rs/notify/latest/notify/poll/struct.PollWatcher.html), but it scans filesystem, which is really expensive. So I just remove the flag. # User-Facing Changes 1. `--debounce-ms` flag is removed 2. no longer watch `Rename` event. # 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-22 21:35:09 +00:00
notify = "5.1.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00: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 20:52:04 +00:00
num-traits = "0.2.14"
Bump once_cell from 1.16.0 to 1.17.0 (#7732)
2023-01-11 23:00:44 +00: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 18:47:37 +00:00
open = "3.2.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00:00
pathdiff = "0.2.1"
Update `powierza-coefficient` to `1.0.2` (#7625)
2022-12-29 14:55:00 +00:00
powierza-coefficient = "1.0.2"
Bump quick-xml from 0.25.0 to 0.27.1 (#7768)
2023-01-16 02:06:31 +00:00
quick-xml = "0.27"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00: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 04:52:37 +00:00
rayon = "1.6.1"
Bump regex from 1.6.0 to 1.7.1 (#7833)
2023-01-23 01:44:10 +00: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 13:16:14 +00:00
reqwest = { version = "0.11", features = ["blocking", "json"] }
Bump roxmltree from 0.17.0 to 0.18.0 (#8065) Bumps [roxmltree](https://github.com/RazrFalcon/roxmltree) from 0.17.0 to 0.18.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/RazrFalcon/roxmltree/blob/master/CHANGELOG.md">roxmltree's changelog</a>.</em></p> <blockquote> <h2>[0.18.0] - 2023-02-04</h2> <h3>Added</h3> <ul> <li><code>StringStorage</code> that exposes an internal string storage.</li> <li>Allocated strings are stored as <code>Arc&lt;str&gt;</code> and not <code>String</code> now.</li> <li><code>Node::text_storage</code></li> <li><code>Node::tail_storage</code></li> <li><code>Attribute::value_storage</code></li> <li><code>Node::range</code></li> </ul> <h3>Removed</h3> <ul> <li><code>Node::position</code>. Use <code>Node::range</code> instead.</li> </ul> <h3>Fixed</h3> <ul> <li>Some methods return longer lifetimes now. Thanks to <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a></li> <li>Overly verbose Debug implementations. Thanks to <a href="https://github.com/adamreichold"><code>@​adamreichold</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/RazrFalcon/roxmltree/commit/8f6f14bbc7bcaf39bd65956c1858b7c78b99791f"><code>8f6f14b</code></a> Version bump.</li> <li><a href="https://github.com/RazrFalcon/roxmltree/commit/c4d622fccc9d082b799a281bc6fc9b66267c285a"><code>c4d622f</code></a> Store node's end position again.</li> <li><a href="https://github.com/RazrFalcon/roxmltree/commit/3d33827a7571b28fc4e890cb42db054fc6e615c2"><code>3d33827</code></a> Use ref-counted owned strings.</li> <li><a href="https://github.com/RazrFalcon/roxmltree/commit/e81718610aa8943664c937844f60dda34bce4556"><code>e817186</code></a> Expose 'input lifetime where it is the backing lifetime.</li> <li><a href="https://github.com/RazrFalcon/roxmltree/commit/0b12673528ce049e94d080156e139b59a51dbc05"><code>0b12673</code></a> Use consistent debug impls for the various iterators that avoid formatting th...</li> <li>See full diff in <a href="https://github.com/RazrFalcon/roxmltree/compare/v0.17.0...v0.18.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=roxmltree&package-manager=cargo&previous-version=0.17.0&new-version=0.18.0)](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-02-13 02:35:09 +00:00
roxmltree = "0.18.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00: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 18:09:31 +00: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 13:16:14 +00:00
serde = { version = "1.0.123", features = ["derive"] }
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00:00
serde_urlencoded = "0.7.0"
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 19:56:15 +00:00
serde_yaml = "0.9.4"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00:00
sha2 = "0.10.0"
Look up git commit hash ourselves, drop libgit2 dependency (#5548)
2022-05-16 01:57:25 +00:00
# Disable default features b/c the default features build Git (very slow to compile)
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
percent-encoding = "2.2.0"
Pin `reedline` to `0.16.0` (#8142) # Description See release notes: https://github.com/nushell/reedline/releases/tag/v0.16.0 # User-Facing Changes Only internal # Tests + Formatting (-)
2023-02-20 21:44:04 +00:00
reedline = { version = "0.16.0", features = ["bashisms", "sqlite"] }
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
rusqlite = { version = "0.28.0", features = ["bundled"], optional = true }
Bump shadow-rs from 0.16.3 to 0.20.0 (#7837)
2023-01-23 01:55:51 +00:00
shadow-rs = { version = "0.20.0", default-features = false }
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
sqlparser = { version = "0.30.0", features = ["serde"], optional = true }
Bump sysinfo from 0.27.7 to 0.28.0 (#8132) Bumps [sysinfo](https://github.com/GuillaumeGomez/sysinfo) from 0.27.7 to 0.28.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/GuillaumeGomez/sysinfo/blob/master/CHANGELOG.md">sysinfo's changelog</a>.</em></p> <blockquote> <h1>0.28.0</h1> <ul> <li>Linux: Fix name and CPU usage for processes tasks.</li> <li>unix: Keep all users, even &quot;not real&quot; accounts.</li> <li>Windows: Use SID for Users ID.</li> <li>Fix C API.</li> <li>Disable default cdylib compilation.</li> <li>Add <code>serde</code> feature to enable serialization.</li> <li>Linux: Handle <code>Idle</code> state in <code>ProcessStatus</code>.</li> <li>Linux: Add brand and name of ARM CPUs.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/GuillaumeGomez/sysinfo/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sysinfo&package-manager=cargo&previous-version=0.27.7&new-version=0.28.0)](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-02-20 02:58:07 +00:00
sysinfo = "0.28.0"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
tabled = "0.10.0"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 16:18:06 +00: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 20:55:01 +00: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 16:18:06 +00:00
titlecase = "2.0.0"
Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command (#7990) # Description Added fix for #7970 - Upgraded toml crate version from version from 0.5.8 to 0.7.1 for package nu-command # Tests + Formatting Added two tests to support the toml upgrade. - `cargo test --package nu-command --lib -- formats::from::toml::tests --nocapture` Executed all tests. - `cargo test --workspace` --------- Co-authored-by: Nitin Londhe <nitin.londhe@genmills.com>
2023-02-06 20:15:14 +00:00
toml = "0.7.1"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
unicode-segmentation = "1.10.0"
unicode-width = "0.1.10"
`du` command (#916) * wip on `du` command * working
2022-02-03 17:35:06 +00:00
url = "2.2.1"
Bump uuid from 1.2.2 to 1.3.0 (#8130) Bumps [uuid](https://github.com/uuid-rs/uuid) from 1.2.2 to 1.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/uuid-rs/uuid/releases">uuid's releases</a>.</em></p> <blockquote> <h2>1.3.0</h2> <h2>What's Changed</h2> <ul> <li>Fix error message. by <a href="https://github.com/basbossink-ds"><code>@​basbossink-ds</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/656">uuid-rs/uuid#656</a></li> <li>implement Arbitrary::size_hint by <a href="https://github.com/Ekleog"><code>@​Ekleog</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/657">uuid-rs/uuid#657</a></li> <li>Always use hyphenated format regardless of flags by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/658">uuid-rs/uuid#658</a></li> <li>Update windows-sys requirement from 0.42.0 to 0.45.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/654">uuid-rs/uuid#654</a></li> <li>Prepare for 1.3.0 release by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/659">uuid-rs/uuid#659</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/basbossink-ds"><code>@​basbossink-ds</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/656">uuid-rs/uuid#656</a></li> <li><a href="https://github.com/Ekleog"><code>@​Ekleog</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/657">uuid-rs/uuid#657</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/uuid-rs/uuid/compare/1.2.2...1.3.0">https://github.com/uuid-rs/uuid/compare/1.2.2...1.3.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/uuid-rs/uuid/commit/573362627c354bd13432e9aa9cdc3465e00aaff3"><code>5733626</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/659">#659</a> from uuid-rs/cargo/1.3.0</li> <li><a href="https://github.com/uuid-rs/uuid/commit/59ac0470146d8c4ee73c57475993468302f6d2a6"><code>59ac047</code></a> prepare for 1.3.0 release</li> <li><a href="https://github.com/uuid-rs/uuid/commit/e01078785036347100a0e992e05e6ef121df13f0"><code>e010787</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/654">#654</a> from uuid-rs/dependabot/cargo/windows-sys-0.45.0</li> <li><a href="https://github.com/uuid-rs/uuid/commit/b90b8206035b3c22b6b9762c12fc5208d2cabbf0"><code>b90b820</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/658">#658</a> from uuid-rs/fix/alternate-format</li> <li><a href="https://github.com/uuid-rs/uuid/commit/1af8269957b784650ea39cd4b114e575d1b96c12"><code>1af8269</code></a> fix up tests around alternative format</li> <li><a href="https://github.com/uuid-rs/uuid/commit/e7eaf5b4a2f37c1742d06ccf37bae7f83ce3b00d"><code>e7eaf5b</code></a> always use hyphenated format regardless of flags</li> <li><a href="https://github.com/uuid-rs/uuid/commit/52197cd2752e9e57c6adf5f58bfd00c830e8241d"><code>52197cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/657">#657</a> from Ekleog/arbitrary-size-hint</li> <li><a href="https://github.com/uuid-rs/uuid/commit/b362542ee26e9e29b996994f6a1cd25c3c3b8e00"><code>b362542</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/656">#656</a> from basbossink-ds/fix/655-deserialize-error-msg</li> <li><a href="https://github.com/uuid-rs/uuid/commit/212b90227712d47b564347f6c67c258812c5a56c"><code>212b902</code></a> implement Arbitrary::size_hint</li> <li><a href="https://github.com/uuid-rs/uuid/commit/40d8711f11e603f9ea01e192e30f087b969b27eb"><code>40d8711</code></a> Also fix the doc comment</li> <li>Additional commits viewable in <a href="https://github.com/uuid-rs/uuid/compare/1.2.2...1.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=uuid&package-manager=cargo&previous-version=1.2.2&new-version=1.3.0)](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-02-21 23:32:52 +00:00
uuid = { version = "1.3.0", features = ["v4"] }
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 13:16:14 +00:00
wax = { version = "0.5.0" }
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
which = { version = "4.4.0", optional = true }
`string | fill` counts clusters, not graphemes; and doesn't count ANSI escape codes (#8134) Enhancement of new `fill` command (#7846) to handle content including ANSI escape codes for formatting or multi-code-point Unicode grapheme clusters. In both of these cases, the content is (many) bytes longer than its visible length, and `fill` was counting the extra bytes so not adding enough fill characters. # Description This script: ```rust # the teacher emoji `\u{1F9D1}\u{200D}\u{1F3EB}` is 3 code points, but only 1 print position wide. echo "This output should be 3 print positions wide, with leading and trailing `+`" $"\u{1F9D1}\u{200D}\u{1F3EB}" | fill -c "+" -w 3 -a "c" echo "This output should be 3 print positions wide, with leading and trailing `+`" $"(ansi green)a(ansi reset)" | fill -c "+" -w 3 -a c echo "" ``` Was producing this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` 🧑‍🏫 This output should be 3 print positions wide, with leading and trailing `+` a ``` After this PR, it produces this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` +🧑‍🏫+ This output should be 3 print positions wide, with leading and trailing `+` +a+ ``` # User-Facing Changes Users may have to undo fixes they may have introduced to work around the former behavior. I have one such in my prompt string that I can now revert. # Tests + Formatting Don't forget to add tests that cover your changes. -- Done Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting `fill` command not documented in the book, and it still talks about `str lpad/rpad`. I'll fix. Note added dependency on a new library `print-positions`, which is an iterator that yields a complete print position (cluster + Ansi sequence) per call. Should this be vendored?
2023-02-20 12:32:20 +00:00
print-positions = "0.6.1"
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 01:01:31 +00: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 18:54:36 +00:00
[target.'cfg(windows)'.dependencies]
Bump winreg from 0.10.1 to 0.11.0 (#8128) Bumps [winreg](https://github.com/gentoo90/winreg-rs) from 0.10.1 to 0.11.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gentoo90/winreg-rs/blob/master/CHANGELOG.md">winreg's changelog</a>.</em></p> <blockquote> <h2>0.11.0</h2> <ul> <li>Migrate to the 2018 edition of Rust</li> <li>Move the code from <code>lib.rs</code> to separate files</li> <li>Use <a href="https://crates.io/crates/cfg-if"><code>cfg-if</code></a> instead of <code>build.rs</code> to fail build on non-windows systems</li> <li>Reimplement deserialization logic, implement [de]serialization for byte arrays (<a href="https://github-redirect.dependabot.com/gentoo90/winreg-rs/issues/49">#49</a>)</li> <li>Fix some typos and <code>clippy</code> warnings</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f34742d674fd3472bdad036849fe888e6474c07e"><code>f34742d</code></a> Bump version to 0.11.0</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/75f2593f6285d06aea031db9cfed3be0bdfd40aa"><code>75f2593</code></a> Move the changelog to a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/1f6f877ed73c5b94dd81b883c3acb3f9d14ffd85"><code>1f6f877</code></a> Fix some clippy warnings</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/7a32d642cd8489ab827f0fce984011b67d26672d"><code>7a32d64</code></a> Implement [de]serialization for byte arrays</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/8464557c2d75b6397571b25c0e93195aed29b05d"><code>8464557</code></a> Reimplement deserialization logic</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/9e8dc28029ffeb14fdff76a30c896e8b52825533"><code>9e8dc28</code></a> Put serialization tests into a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/04f7d232c7abaf6069020c52b8da77f9f1e5f5f2"><code>04f7d23</code></a> Use <code>cfg-if</code> to fail build on non-windows systems</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/c3ac5ba5eaa83916c2fbad270bb1a83fee9f7715"><code>c3ac5ba</code></a> Move the code from <code>lib.rs</code> to separate files</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/17378a9ca4c1f8fc2dc668a5dfe2f5d6bd54cc82"><code>17378a9</code></a> Migrate to the 2018 edition of Rust</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f4d45923abf53b1aee8f9f7e2f002c459a97b717"><code>f4d4592</code></a> Remove Appveyor. It's broken anyway</li> <li>Additional commits viewable in <a href="https://github.com/gentoo90/winreg-rs/compare/v0.10.1...v0.11.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=winreg&package-manager=cargo&previous-version=0.10.1&new-version=0.11.0)](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-02-20 02:57:46 +00:00
winreg = "0.11.0"
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 18:54:36 +00:00
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 04:59:53 +00:00
[target.'cfg(unix)'.dependencies]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
libc = "0.2"
nu-command ls - bump umask crate to 2.0.0 (#5514)
2022-05-11 21:13:45 +00:00
umask = "2.0.0"
Update some deps (#3011)
2021-02-05 20:54:54 +00:00
users = "0.11.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 04:59:53 +00: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 18:21:19 +00:00
[target.'cfg(not(any(target_os = "android", target_os = "ios")))'.dependencies.trash]
optional = true
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
version = "3.0.1"
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 18:21:19 +00: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 08:14:40 +00:00
[dependencies.polars]
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 17:45:09 +00:00
features = [
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 12:06:31 +00:00
"arg_where",
"checked_arithmetic",
"concat_str",
"cross_join",
"csv-file",
"cum_agg",
"default",
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
"dtype-categorical",
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 12:06:31 +00:00
"dtype-datetime",
"dtype-struct",
"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-12 23:30:20 +00:00
"ipc",
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 12:06:31 +00: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 17:45:09 +00:00
]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
optional = true
Update polars to 0.27.2 (#8154) Mostly to get rid of https://github.com/pola-rs/polars/pull/6098/files This currently breaks nushell's table formatting: ``` nu ❯ open-df forcing.arrow | first could not mmap compressed IPC file, defaulting to normal read╭───┬──────────┬────┬────────┬──────────┬───────┬──────────┬──────┬──────────┬─────╮ │ # │ time │ id │ demand │ drainage │ E_pot │ infiltra │ P │ priority │ ... │ │ │ │ │ │ │ │ tion │ │ │ │ ├───┼──────────┼────┼────────┼──────────┼───────┼──────────┼──────┼──────────┼─────┤ │ 0 │ 4 years │ 1 │ 0.00 │ 0.02 │ 0.00 │ 0.00 │ 0.00 │ 4.00 │ ... │ │ │ ago │ │ │ │ │ │ │ │ │ ╰───┴──────────┴────┴────────┴──────────┴───────┴──────────┴──────┴──────────┴─────╯ ``` @visr
2023-02-21 23:32:28 +00:00
version = "0.27.2"
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 08:14:40 +00: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 16:37:27 +00:00
[target.'cfg(windows)'.dependencies.windows]
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 18:57:40 +00:00
features = ["Win32_Foundation", "Win32_Storage_FileSystem", "Win32_System_SystemServices"]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
version = "0.44.0"
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 16:37:27 +00:00
add rm command + stubs for open and save
2021-10-10 04:13:15 +00:00
[features]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
dataframe = ["num", "polars", "sqlparser"]
plugin feature flag
2021-11-02 20:56:00 +00:00
plugin = ["nu-parser/plugin"]
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 18:57:40 +00:00
sqlite = ["rusqlite"] # TODO: given that rusqlite is included in reedline, should we just always include it?
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
trash-support = ["trash"]
which-support = ["which"]
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 04:59:53 +00:00
[build-dependencies]
Bump shadow-rs from 0.16.3 to 0.20.0 (#7837)
2023-01-23 01:55:51 +00: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 04:59:53 +00:00
[dev-dependencies]
Update to `0.76.1` version for development (#8161) # Description For tracking in `version` for bug reports during development. Might be used for an urgent hotfix if necessary.
2023-02-21 23:21:39 +00:00
nu-test-support = { path = "../nu-test-support", version = "0.76.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 17:39:27 +00: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 20:59:01 +00:00
dirs-next = "2.0.0"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # 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-02-11 18:59:11 +00:00
hamcrest2 = "0.3.0"
Bump proptest from 1.0.0 to 1.1.0 (#8063) Bumps [proptest](https://github.com/proptest-rs/proptest) from 1.0.0 to 1.1.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/proptest-rs/proptest/commit/75c749ee503d4ba7285b1aad4eb7440052a830e7"><code>75c749e</code></a> bump version to 1.1.0</li> <li><a href="https://github.com/proptest-rs/proptest/commit/a7c75a1bcb83777744d39cfce327ea6df002f867"><code>a7c75a1</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/proptest-rs/proptest/issues/295">#295</a> from proptest-rs/replays-dont-count-cases</li> <li><a href="https://github.com/proptest-rs/proptest/commit/a854d2ed7a6fa06526850331c7176e05bec090f0"><code>a854d2e</code></a> [replays-dont-count-cases] persisted failures are not counted against success...</li> <li><a href="https://github.com/proptest-rs/proptest/commit/f8eff506039ebe250b2d9e0a1c773edaa54de656"><code>f8eff50</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/proptest-rs/proptest/issues/291">#291</a> from schuelermine/fix/prop_assert_ne!</li> <li><a href="https://github.com/proptest-rs/proptest/commit/d38268304c5810daa17394a2133f8e136d65a2d8"><code>d382683</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/proptest-rs/proptest/issues/294">#294</a> from proptest-rs/fix-ci</li> <li><a href="https://github.com/proptest-rs/proptest/commit/ad0a4d311c3a368f9d752b7ec12cb35a98f0cec2"><code>ad0a4d3</code></a> [fix-ci] changed the line for where the error occurs</li> <li><a href="https://github.com/proptest-rs/proptest/commit/00f29af8e8138d4f58e592a1362bec1715733a41"><code>00f29af</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/proptest-rs/proptest/issues/288">#288</a> from proptest-rs/const-generic-arbitrary</li> <li><a href="https://github.com/proptest-rs/proptest/commit/a16853f4fc78fe1104df50eab374c6de5ca5d99c"><code>a16853f</code></a> Fix prop_assert_ne! requiring import of prop_assert!</li> <li><a href="https://github.com/proptest-rs/proptest/commit/b513a32c72d6ac0177cacfacee6e9816a06635cf"><code>b513a32</code></a> Config : support disabling failure persistence via env var (<a href="https://github-redirect.dependabot.com/proptest-rs/proptest/issues/287">#287</a>)</li> <li><a href="https://github.com/proptest-rs/proptest/commit/7a94e165895502b7034b6f4c17293846456421d9"><code>7a94e16</code></a> note that PROPTEST_CASES and other env var requires the std feature (<a href="https://github-redirect.dependabot.com/proptest-rs/proptest/issues/262">#262</a>)</li> <li>Additional commits viewable in <a href="https://github.com/proptest-rs/proptest/compare/1.0.0...v1.1.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=proptest&package-manager=cargo&previous-version=1.0.0&new-version=1.1.0)](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-02-13 02:31:53 +00:00
proptest = "1.1.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 20:59:01 +00:00
quickcheck = "1.0.3"
list keybinding options (#906) * list keybinding optins * list keybinding options * clippy error
2022-02-04 06:47:18 +00:00
quickcheck_macros = "1.0.0"
Bump rstest from 0.15.0 to 0.16.0 (#8064) [//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [rstest](https://github.com/la10736/rstest) from 0.15.0 to 0.16.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/la10736/rstest/releases">rstest's releases</a>.</em></p> <blockquote> <h2>0.16.0</h2> <p>Use values expression to define test names.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/la10736/rstest/blob/master/CHANGELOG.md">rstest's changelog</a>.</em></p> <blockquote> <h2>[0.16.0] 2022/11/27</h2> <h3>Changed</h3> <ul> <li>Show <code>TEST START</code> banner only when trace some argument: See <a href="https://github-redirect.dependabot.com/la10736/rstest/issues/158">#158</a> for details.</li> <li>Add values to test name: See <a href="https://github-redirect.dependabot.com/la10736/rstest/issues/160">#160</a> for details.</li> </ul> <h3>Fixed</h3> <ul> <li>Updated test fixtures to 1.64.0 compiler's error messages.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/la10736/rstest/commit/d7ff088126a402d297a8b79d24d3b88d3aafd86e"><code>d7ff088</code></a> Update checkout list</li> <li><a href="https://github.com/la10736/rstest/commit/4386575950f92c710c6016a6f301adb64bd52d90"><code>4386575</code></a> Version 0.16.0 chengelog</li> <li><a href="https://github.com/la10736/rstest/commit/41749a881ef9faead0c17ef186704b70a7c18f12"><code>41749a8</code></a> Fix clippy warning</li> <li><a href="https://github.com/la10736/rstest/commit/daaddde1a0f5b73284d5d69fe4f6d2826054aaae"><code>daaddde</code></a> Bump to 0.16.0 version and upgrade dependency</li> <li><a href="https://github.com/la10736/rstest/commit/576768e4b375129d41cabd201a06bfb7a278351c"><code>576768e</code></a> Fixed dev dependency in rstest_macros</li> <li><a href="https://github.com/la10736/rstest/commit/a6eb3a96cb02c4021d686a10e4c3744948ba0adc"><code>a6eb3a9</code></a> Update rstest_test version</li> <li><a href="https://github.com/la10736/rstest/commit/4a18dd0bd1723e9b924a4b2b687c797736efb7ee"><code>4a18dd0</code></a> Update version</li> <li><a href="https://github.com/la10736/rstest/commit/29648832cead27597a8d9cf47f5b4b1eee2bd366"><code>2964883</code></a> Update dependency version</li> <li><a href="https://github.com/la10736/rstest/commit/5ad7e3fd61086d648ed17a9998653017ab56423f"><code>5ad7e3f</code></a> <a href="https://github-redirect.dependabot.com/la10736/rstest/issues/160">#160</a> Add test for module annotation</li> <li><a href="https://github.com/la10736/rstest/commit/a302be019fdf824413a6f15360f793348d91752b"><code>a302be0</code></a> <a href="https://github-redirect.dependabot.com/la10736/rstest/issues/160">#160</a> Tests fixed and add unit for allow</li> <li>Additional commits viewable in <a href="https://github.com/la10736/rstest/compare/0.15.0...0.16.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rstest&package-manager=cargo&previous-version=0.15.0&new-version=0.16.0)](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-02-13 02:34:09 +00:00
rstest = { version = "0.16.0", default-features = false }
Reference in a new issue Copy permalink