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

167 lines
4.6 KiB
TOML
Raw Normal View History

nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
[package]
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 21:25:38 +01:00
authors = ["The Nushell Project Developers"]
Update incorrect crate descriptions (#5159)
2022-04-11 20:17:06 +02:00
description = "Nushell's built-in commands"
Add licenses (#4893) * Add licenses * Add licenses
2022-03-22 21:25:38 +01:00
edition = "2021"
license = "MIT"
nu-cli refactor moving commands into their own crate nu-command (#2910) * move commands, futures.rs, script.rs, utils * move over maybe_print_errors * add nu_command crate references to nu_cli * in commands.rs open up to pub mod from pub(crate) * nu-cli, nu-command, and nu tests are now passing * cargo fmt * clean up nu-cli/src/prelude.rs * code cleanup * for some reason lex.rs was not formatted, may be causing my error * remove mod completion from lib.rs which was not being used along with quickcheck macros * add in allow unused imports * comment out one failing external test; comment out one failing internal test * revert commenting out failing tests; something else might be going on; someone with a windows machine should check and see what is going on with these failing windows tests * Update Cargo.toml Extend the optional features to nu-command Co-authored-by: Jonathan Turner <jonathandturner@users.noreply.github.com>
2021-01-12 05:59:53 +01:00
name = "nu-command"
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 19:59:11 +01:00
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-command"
Bump to `0.78.1` development version (#8741) # Description either just development or hotfix
2023-04-05 03:36:10 +02:00
version = "0.78.1"
Port version (#467) * First iteration of the version command * Cleanup * Fix the installed plugins bug * Fix fmt check issue * Fix clippy warning * Fixing all clippy warnings * Remove old code
2021-12-11 21:08:17 +01:00
Add nu-protocol
2021-09-02 03:29:43 +02:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
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 23:22:00 +01:00
[lib]
bench = false
Add nu-protocol
2021-09-02 03:29:43 +02:00
[dependencies]
Bump to `0.78.1` development version (#8741) # Description either just development or hotfix
2023-04-05 03:36:10 +02:00
nu-cmd-lang = { path = "../nu-cmd-lang", version = "0.78.1" }
nu-color-config = { path = "../nu-color-config", version = "0.78.1" }
nu-engine = { path = "../nu-engine", version = "0.78.1" }
nu-explore = { path = "../nu-explore", version = "0.78.1" }
nu-glob = { path = "../nu-glob", version = "0.78.1" }
nu-json = { path = "../nu-json", version = "0.78.1" }
nu-parser = { path = "../nu-parser", version = "0.78.1" }
nu-path = { path = "../nu-path", version = "0.78.1" }
nu-pretty-hex = { path = "../nu-pretty-hex", version = "0.78.1" }
nu-protocol = { path = "../nu-protocol", version = "0.78.1" }
nu-system = { path = "../nu-system", version = "0.78.1" }
nu-table = { path = "../nu-table", version = "0.78.1" }
nu-term-grid = { path = "../nu-term-grid", version = "0.78.1" }
nu-utils = { path = "../nu-utils", version = "0.78.1" }
upgrade num-format (#6694)
2022-10-10 13:25:57 +02:00
num-format = { version = "0.4.3" }
Add a very silly ls
2021-09-10 03:06:44 +02:00
Bump version to `0.77.0` (#8410)
2023-03-14 19:46:42 +01:00
nu-ansi-term = "0.47.0"
Add a very silly ls
2021-09-10 03:06:44 +02: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 19:59:11 +01:00
Inflector = "0.11"
Bump alphanumeric-sort from 1.4.4 to 1.5.0 (#8532)
2023-03-22 14:02:45 +01:00
alphanumeric-sort = "1.5.0"
Try to fix #7380 (#7446) fix https://github.com/nushell/nushell/issues/7380
2022-12-15 15:47:04 +01:00
atty = "0.2.14"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-01-13 14:16:14 +01:00
base64 = "0.21.0"
Binary into int (#5941) * Add support for binary to into int * Add test
2022-07-03 20:31:50 +02:00
byteorder = "1.4.3"
Bump bytesize from 1.1.0 to 1.2.0 (#8236) Bumps [bytesize](https://github.com/hyunsik/bytesize) from 1.1.0 to 1.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/hyunsik/bytesize/releases">bytesize's releases</a>.</em></p> <blockquote> <h2>Release 1.2.0</h2> <h2>Changes</h2> <ul> <li>serde improvements <a href="https://github-redirect.dependabot.com/hyunsik/bytesize/issues/29">#29</a> (<a href="https://github.com/joeroback"><code>@​joeroback</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/hyunsik/bytesize/commit/476dc867b2a38fda50cfe065859664fcafc522f7"><code>476dc86</code></a> Remove -dev suffix for release</li> <li><a href="https://github.com/hyunsik/bytesize/commit/eaaf3bc0970a4ff74c0475efdab37152124d087e"><code>eaaf3bc</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/hyunsik/bytesize/issues/29">#29</a> from joeroback/serde_improvements</li> <li><a href="https://github.com/hyunsik/bytesize/commit/c7a785bd2c82ef95589792b3567446891ef27d62"><code>c7a785b</code></a> resolves <a href="https://github-redirect.dependabot.com/hyunsik/bytesize/issues/27">#27</a>, fixes several clippy warnings with u16/u8 and is_digit/is_ascii...</li> <li><a href="https://github.com/hyunsik/bytesize/commit/db44636f05670bea80efa64957d91d87395bfca8"><code>db44636</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/hyunsik/bytesize/issues/28">#28</a> from ileixe/master</li> <li><a href="https://github.com/hyunsik/bytesize/commit/58cf4a502411381206647e51171ba191c0d3a516"><code>58cf4a5</code></a> Change as_u64() to const</li> <li><a href="https://github.com/hyunsik/bytesize/commit/065c00b54ff75f399c61f4dd1ea792def6ea1070"><code>065c00b</code></a> Change the crate version to 1.2.0-dev</li> <li>See full diff in <a href="https://github.com/hyunsik/bytesize/compare/v1.1.0...v1.2.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=bytesize&package-manager=cargo&previous-version=1.1.0&new-version=1.2.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-27 07:48:14 +01:00
bytesize = "1.2.0"
couple minor updates to xml deps (#7311) # Description Just some minor updates to xml deps # User-Facing Changes _(List of all changes that impact the user experience here. This helps us keep track of breaking changes.)_ # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2022-12-01 20:25:13 +01:00
calamine = "0.19.1"
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 19:59:11 +01:00
chrono = { version = "0.4.23", features = ["std", "unstable-locales"], default-features = false }
Port date commands to engine-q
2021-10-31 07:54:51 +01:00
chrono-humanize = "0.2.1"
Bump chrono-tz from 0.6.3 to 0.8.1 (#7907)
2023-01-30 02:38:39 +01:00
chrono-tz = "0.8.1"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
crossterm = "0.26"
Bump csv from 1.1.6 to 1.2.0 (#8235) Bumps [csv](https://github.com/BurntSushi/rust-csv) from 1.1.6 to 1.2.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/BurntSushi/rust-csv/commit/fa01b78533a58d6c1087990a79a42c97c6edd069"><code>fa01b78</code></a> 1.2.0</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/2ba20b55d91688d5e0e86b204d9fc2990c7e6df9"><code>2ba20b5</code></a> readme: various updates</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/521294f87b3e1e286829f85a34f397e007f081ed"><code>521294f</code></a> msrv: set rust-version = 1.60</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/31c8ebc49d6134f666a6607783883e50460ed87d"><code>31c8ebc</code></a> readme: updates and set rust-version</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/a0e83883e2f862103edf42b130639cba50fb02f3"><code>a0e8388</code></a> deps: drop 'bstr'</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/9e1126a3f42574cafd31b2309ce686b66444e865"><code>9e1126a</code></a> cargo: update some fields</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/d7a4f7dcc6d7d2395a194595f1fd1803fcc9d809"><code>d7a4f7d</code></a> rust: move to 2021 edition</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/022ac05205e2a525711481e77cf8d6df2c254833"><code>022ac05</code></a> error: drop 'source' impl</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/9ab83111a7ec047d6542dbd23d305cb1bf0a23ef"><code>9ab8311</code></a> *: better import grouping and short hand struct init</li> <li><a href="https://github.com/BurntSushi/rust-csv/commit/ea0273c531b7f09fabefd6bea68c7a99d42554de"><code>ea0273c</code></a> *: fix all warnings and update code</li> <li>Additional commits viewable in <a href="https://github.com/BurntSushi/rust-csv/compare/1.1.6...1.2.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=csv&package-manager=cargo&previous-version=1.1.6&new-version=1.2.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-27 07:48:51 +01:00
csv = "1.2.0"
Bump dialoguer from 0.9.0 to 0.10.3 (#7765)
2023-01-16 03:04:47 +01:00
dialoguer = { default-features = false, version = "0.10.3" }
removes unused features. (#6938) * removes unused features. * Adds back multithreading feature to sysinfo. * Adds back alloc for percent-encoding * Adds updated lock file. * Missed one sysinfo. * `indexmap` just defaults * Revert `miette``default-features=false` Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-11-12 06:44:56 +01:00
digest = { default-features = false, version = "0.10.0" }
Pick up fix in dtparse for nanosec truncation noted at bottom of #8337 (#8805) # Description Pick up [enhancement in `dtparse`](https://github.com/bspeice/dtparse/pull/41), to preserve nanoseconds in string-to-date conversions. # User-Facing Changes An especially eagle-eyed user might notice that prior versions of nushell were losing nanosecond precision when converting string format date/time to datetime. Before: ```nushell 〉'2023-03-02T01:02:03.987654321' | into datetime | date to-record ╭────────────┬───────────╮ │ year │ 2023 │ │ month │ 3 │ │ day │ 2 │ │ hour │ 1 │ │ minute │ 2 │ │ second │ 3 │ │ nanosecond │ 987654000 │ │ timezone │ -04:00 │ ╰────────────┴───────────╯ ``` Now, it just works(tm) ```nushell 〉'2023-03-02T01:02:03.987654321' | into datetime | date to-record ╭────────────┬───────────╮ │ year │ 2023 │ │ month │ 3 │ │ day │ 2 │ │ hour │ 1 │ │ minute │ 2 │ │ second │ 3 │ │ nanosecond │ 987654321 │ │ timezone │ -04:00 │ ╰────────────┴───────────╯ ``` # Tests + Formatting Don't forget to add tests that cover your changes. 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 Some (unrelated) tests did fail [^err] - [x] `cargo run -- crates/nu-std/tests.nu` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. # (Unrelated) test failures noted [^err]: Several tests are failing, unrelated to this PR ``` failures: ---- modules::module_import_env_1 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env main.nu; use main.nu foo; foo · ───┬─── · ╰── file not found ╰──── thread 'modules::module_import_env_1' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"foo"`', tests/modules/mod.rs:316:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ---- modules::module_import_env_2 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env main.nu; $env.FOO · ───┬─── · ╰── file not found ╰──── thread 'modules::module_import_env_2' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"foo"`', tests/modules/mod.rs:341:9 ---- overlays::overlay_use_do_cd_file_relative stdout ---- === stderr thread 'overlays::overlay_use_do_cd_file_relative' panicked at 'assertion failed: `(left == right)` left: `"nushell"`, right: `"test1"`', tests/overlays/mod.rs:919:9 ---- overlays::overlay_use_dont_cd_overlay stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env test1/test2/spam.nu; $env.PWD | path basename · ─────────┬───────── · ╰── file not found ╰──── thread 'overlays::overlay_use_dont_cd_overlay' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"overlay_use_dont_cd_overlay"`', tests/overlays/mod.rs:946:9 ---- parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env lol/lol.nu; $env.FOO · ─────┬──── · ╰── file not found ╰──── thread 'parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"good"`', tests/parsing/mod.rs:177:9 ---- parsing::parse_file_relative_to_parsed_file_simple stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env lol/lol/lol.nu; $env.LOL · ───────┬────── · ╰── file not found ╰──── thread 'parsing::parse_file_relative_to_parsed_file_simple' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"lol"`', tests/parsing/mod.rs:99:9 ---- shell::const_nu_lib_dirs_relative stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[main.nu:1:1] 1 │ const NU_LIB_DIRS = [ 'scripts' ] 2 │ source-env foo.nu · ───┬── thread 'shell::const_nu_lib_dirs_relative' panicked at 'assertion failed: outcome.err.is_empty()', tests/shell/mod.rs:166:9 ---- shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines stdout ---- === stderr thread 'shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"AndrásWithKitKat"`', tests/shell/pipeline/commands/external.rs:198:13 ---- shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings stdout ---- === stderr thread 'shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"jt_likes_cake.txt"`', tests/shell/pipeline/commands/external.rs:173:13 failures: modules::module_import_env_1 modules::module_import_env_2 overlays::overlay_use_do_cd_file_relative overlays::overlay_use_dont_cd_overlay parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1 parsing::parse_file_relative_to_parsed_file_simple shell::const_nu_lib_dirs_relative shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings test result: FAILED. 386 passed; 9 failed; 20 ignored; 0 measured; 0 filtered out; finished in 98.06s error: test failed, to rerun pass `-p nu --test main` failures: ---- modules::module_import_env_1 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env main.nu; use main.nu foo; foo · ───┬─── · ╰── file not found ╰──── thread 'modules::module_import_env_1' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"foo"`', tests/modules/mod.rs:316:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ---- modules::module_import_env_2 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env main.nu; $env.FOO · ───┬─── · ╰── file not found ╰──── thread 'modules::module_import_env_2' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"foo"`', tests/modules/mod.rs:341:9 ---- overlays::overlay_use_do_cd_file_relative stdout ---- === stderr thread 'overlays::overlay_use_do_cd_file_relative' panicked at 'assertion failed: `(left == right)` left: `"nushell"`, right: `"test1"`', tests/overlays/mod.rs:919:9 ---- overlays::overlay_use_dont_cd_overlay stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env test1/test2/spam.nu; $env.PWD | path basename · ─────────┬───────── · ╰── file not found ╰──── thread 'overlays::overlay_use_dont_cd_overlay' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"overlay_use_dont_cd_overlay"`', tests/overlays/mod.rs:946:9 ---- parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env lol/lol.nu; $env.FOO · ─────┬──── · ╰── file not found ╰──── thread 'parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"good"`', tests/parsing/mod.rs:177:9 ---- parsing::parse_file_relative_to_parsed_file_simple stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env lol/lol/lol.nu; $env.LOL · ───────┬────── · ╰── file not found ╰──── thread 'parsing::parse_file_relative_to_parsed_file_simple' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"lol"`', tests/parsing/mod.rs:99:9 ---- shell::const_nu_lib_dirs_relative stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[main.nu:1:1] 1 │ const NU_LIB_DIRS = [ 'scripts' ] 2 │ source-env foo.nu · ───┬── thread 'shell::const_nu_lib_dirs_relative' panicked at 'assertion failed: outcome.err.is_empty()', tests/shell/mod.rs:166:9 ---- shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines stdout ---- === stderr thread 'shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"AndrásWithKitKat"`', tests/shell/pipeline/commands/external.rs:198:13 ---- shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings stdout ---- === stderr thread 'shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"jt_likes_cake.txt"`', tests/shell/pipeline/commands/external.rs:173:13 failures: modules::module_import_env_1 modules::module_import_env_2 overlays::overlay_use_do_cd_file_relative overlays::overlay_use_dont_cd_overlay parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1 parsing::parse_file_relative_to_parsed_file_simple shell::const_nu_lib_dirs_relative shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings test result: FAILED. 386 passed; 9 failed; 20 ignored; 0 measured; 0 filtered out; finished in 98.06s error: test failed, to rerun pass `-p nu --test main` failures: ---- modules::module_import_env_1 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env main.nu; use main.nu foo; foo · ───┬─── · ╰── file not found ╰──── thread 'modules::module_import_env_1' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"foo"`', tests/modules/mod.rs:316:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ---- modules::module_import_env_2 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env main.nu; $env.FOO · ───┬─── · ╰── file not found ╰──── thread 'modules::module_import_env_2' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"foo"`', tests/modules/mod.rs:341:9 ---- overlays::overlay_use_do_cd_file_relative stdout ---- === stderr thread 'overlays::overlay_use_do_cd_file_relative' panicked at 'assertion failed: `(left == right)` left: `"nushell"`, right: `"test1"`', tests/overlays/mod.rs:919:9 ---- overlays::overlay_use_dont_cd_overlay stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env test1/test2/spam.nu; $env.PWD | path basename · ─────────┬───────── · ╰── file not found ╰──── thread 'overlays::overlay_use_dont_cd_overlay' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"overlay_use_dont_cd_overlay"`', tests/overlays/mod.rs:946:9 ---- parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1 stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env lol/lol.nu; $env.FOO · ─────┬──── · ╰── file not found ╰──── thread 'parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"good"`', tests/parsing/mod.rs:177:9 ---- parsing::parse_file_relative_to_parsed_file_simple stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[source:1:1] 1 │ source-env lol/lol/lol.nu; $env.LOL · ───────┬────── · ╰── file not found ╰──── thread 'parsing::parse_file_relative_to_parsed_file_simple' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"lol"`', tests/parsing/mod.rs:99:9 ---- shell::const_nu_lib_dirs_relative stdout ---- === stderr Error: nu::shell::file_not_found × File not found ╭─[main.nu:1:1] 1 │ const NU_LIB_DIRS = [ 'scripts' ] 2 │ source-env foo.nu · ───┬── thread 'shell::const_nu_lib_dirs_relative' panicked at 'assertion failed: outcome.err.is_empty()', tests/shell/mod.rs:166:9 ---- shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines stdout ---- === stderr thread 'shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"AndrásWithKitKat"`', tests/shell/pipeline/commands/external.rs:198:13 ---- shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings stdout ---- === stderr thread 'shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings' panicked at 'assertion failed: `(left == right)` left: `""`, right: `"jt_likes_cake.txt"`', tests/shell/pipeline/commands/external.rs:173:13 failures: modules::module_import_env_1 modules::module_import_env_2 overlays::overlay_use_do_cd_file_relative overlays::overlay_use_dont_cd_overlay parsing::parse_file_relative_to_parsed_file_dont_use_cwd_1 parsing::parse_file_relative_to_parsed_file_simple shell::const_nu_lib_dirs_relative shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_lines shell::pipeline::commands::external::it_evaluation::takes_rows_of_nu_value_strings test result: FAILED. 386 passed; 9 failed; 20 ignored; 0 measured; 0 filtered out; finished in 98.06s error: test failed, to rerun pass `-p nu --test main` ```
2023-04-14 14:24:46 +02:00
dtparse = "1.4.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01: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 19:57:40 +01:00
fancy-regex = "0.11.0"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
filesize = "0.2.0"
Implement rest of `touch` flags (#5119) * Add timestamp flag to `touch` command * Add modify flag to `touch` command * Add date flag to `touch` command * Remove unnecessary `touch` test and fix tests setups * Change `touch` flags descriptions * Update `touch` example * Add reference flag to `touch` command * Add access flag to `touch` command * Add no-create flag to `touch` command * Replace `unwrap` with `expect`
2022-04-07 13:44:05 +02:00
filetime = "0.2.15"
Bump fs_extra from 1.2.0 to 1.3.0 (#7976)
2023-02-06 10:59:58 +01: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 05:59:53 +01: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 14:16:14 +01:00
indexmap = { version = "1.7", features = ["serde-1"] }
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 02:57:48 +01:00
indicatif = "0.17.2"
Attempts to add a command that checks if nushell is running with admin priveleges (#5712) * attempts to add is-admin command * fmt and clippy * fmt * Update is_admin.rs * typos * typo in example
2022-06-06 13:55:23 +02:00
is-root = "0.1.2"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
itertools = "0.10.0"
log = "0.4.14"
Update crossterm version to 0.26 (#8623) # Description This pr is a companion to https://github.com/nushell/reedline/pull/560 Fortunally, we don't need to change too much nushell code. ## Additional note about lscolor dependency https://github.com/sharkdp/lscolors/pull/58~~ lscolor is using 0.26 for now
2023-04-14 22:14:57 +02:00
lscolors = { version = "0.14", default-features = false, features = ["nu-ansi-term"] }
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
md5 = { package = "md-5", version = "0.10.0" }
Bump miette from 5.6.0 to 5.7.0 (#8720)
2023-04-06 22:39:54 +02:00
miette = { version = "5.7.0", features = ["fancy-no-backtrace"] }
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
mime = "0.3.16"
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2022-12-27 19:46:23 +01:00
mime_guess = "2.0.4"
Revert to notify v4 (#8367) This reverts https://github.com/nushell/nushell/pull/8114 which upgraded to `notify` (a file watching crate used by the `watch` command) v5. `notify` v5 has several breaking changes and it's much harder to use. It no longer includes debouncing of file system events, which I think is essential functionality for `watch`. @WindSoilder was going to try writing our own debouncing functionality but I don't think he had time to finish it. @WindSoilder Is it OK if we revert this for the 0.77 release (March 14)? We can try again for 0.78
2023-03-09 06:45:58 +01:00
notify = "4.0.17"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
num = { version = "0.4.0", optional = true }
Add `bits shl` and `bits shr` command (#6202) * Add `bits shift-left` and `bits shift-right` command * update bits shift error tips * some code refactor * update shift right * some code refactor for bits shift commands * rename bits shift commands align with bits operators * update search term * Update crates/nu-command/src/bits/not.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * Update crates/nu-command/src/bits/shift_left.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * Update crates/nu-command/src/bits/shift_right.rs Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com> * ci skip * change default number-bytes for bits shift * fix bits not tests * fix bits tests Co-authored-by: Stefan Holderbach <sholderbach@users.noreply.github.com>
2022-08-02 22:52:04 +02:00
num-traits = "0.2.14"
Bump once_cell from 1.16.0 to 1.17.0 (#7732)
2023-01-12 00:00:44 +01:00
once_cell = "1.17"
Upgrade `open` crate to fix WSL bug (#8905) This PR upgrades the [`open`](https://github.com/Byron/open-rs) crate (used in the `start` command) from 4.0.1 to 4.0.2. This fixes a bug where `open` doesn't always work properly on WSL: https://github.com/Byron/open-rs/pull/71
2023-04-17 07:05:40 +02:00
open = "4.0.2"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
pathdiff = "0.2.1"
Update `powierza-coefficient` to `1.0.2` (#7625)
2022-12-29 15:55:00 +01:00
powierza-coefficient = "1.0.2"
Bump quick-xml from 0.27.1 to 0.28.1 (#8533)
2023-03-20 18:46:28 +01:00
quick-xml = "0.28"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
rand = "0.8"
Bump rayon from 1.6.1 to 1.7.0 (#8328) Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.6.1 to 1.7.0. <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.7.0 / rayon-core 1.11.0 (2023-03-03)</h1> <ul> <li>The minimum supported <code>rustc</code> is now 1.59.</li> <li>Added a fallback when threading is unsupported.</li> <li>The new <code>ParallelIterator::take_any</code> and <code>skip_any</code> methods work like unordered <code>IndexedParallelIterator::take</code> and <code>skip</code>, counting items in whatever order they are visited in parallel.</li> <li>The new <code>ParallelIterator::take_any_while</code> and <code>skip_any_while</code> methods work like unordered <code>Iterator::take_while</code> and <code>skip_while</code>, which previously had no parallel equivalent. The &quot;while&quot; condition may be satisfied from anywhere in the parallel iterator, affecting all future items regardless of position.</li> <li>The new <code>yield_now</code> and <code>yield_local</code> functions will cooperatively yield execution to Rayon, either trying to execute pending work from the entire pool or from just the local deques of the current thread, respectively.</li> </ul> <h1>Release rayon-core 1.10.2 (2023-01-22)</h1> <ul> <li>Fixed miri-reported UB for SharedReadOnly tags protected by a call.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rayon-rs/rayon/commit/7ffaf3463be2339cb5bad86dc87b602ed067fc7c"><code>7ffaf34</code></a> Merge <a href="https://github-redirect.dependabot.com/rayon-rs/rayon/issues/716">#716</a></li> <li><a href="https://github.com/rayon-rs/rayon/commit/163003e0e3b3489ee96c6b58ba28983c72f58d91"><code>163003e</code></a> bump the release date</li> <li><a href="https://github.com/rayon-rs/rayon/commit/f7d75532fcbc8151b97dec85131e5a0be3db4b4f"><code>f7d7553</code></a> Release rayon 1.3.0 / rayon-core 1.7.0</li> <li><a href="https://github.com/rayon-rs/rayon/commit/b98bb23f0595cbf56afba8f641b366a0433f002e"><code>b98bb23</code></a> Remove unneeded extern crate statements</li> <li><a href="https://github.com/rayon-rs/rayon/commit/9b92c7deb93aedda14ca4401c5fc40a7cff596b0"><code>9b92c7d</code></a> cargo fmt</li> <li><a href="https://github.com/rayon-rs/rayon/commit/e02f439bbfacc534b0a1c07aa6d5bfdc76ed85b8"><code>e02f439</code></a> Remove useless 'use crate;' in favor of the crate prelude</li> <li><a href="https://github.com/rayon-rs/rayon/commit/a1db0fe390e87e8316fd40240c88fbc0b2b79a7c"><code>a1db0fe</code></a> Fix clippy::flat_map_identity</li> <li><a href="https://github.com/rayon-rs/rayon/commit/4e4025693f2e155abc98486b8e6f04e6e33e0a9a"><code>4e40256</code></a> Update ci/compat-Cargo.lock</li> <li><a href="https://github.com/rayon-rs/rayon/commit/1f9d117d51782b338910c26357b697beca2eca47"><code>1f9d117</code></a> Remove cfg(rayon_unstable)</li> <li><a href="https://github.com/rayon-rs/rayon/commit/198ca7f6aa28c08a56301ce3c1826c3e34955da7"><code>198ca7f</code></a> Remove rayon-futures</li> <li>Additional commits viewable in <a href="https://github.com/rayon-rs/rayon/compare/rayon-core-v1.6.1...rayon-core-v1.7.0">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.6.1&new-version=1.7.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-03-06 04:32:16 +01:00
rayon = "1.7.0"
Bump regex from 1.6.0 to 1.7.1 (#7833)
2023-01-23 02:44:10 +01:00
regex = "1.7.1"
changes Reqwest to Ureq. (#8320) # Description _(Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes.)_ This pull request removes `Reqwest` and replaces it with `Ureq` to remove some of our dependencies, giving us faster compile times as well as smaller binaries. `Ureq` does not have an async runtime included so we do not need build heavy dependencies such as `Tokio`. From older tests I had the number of build units be reduced from `430 -> 392`. The default of `Ureq` uses `Rustls` but it has been configured to instead use `native_tls` which should work exactly the same as the `tls` works now. I removed `content-length` from the http commands as after refactoring i did not see a reason to have it available, correct me if this is something we should preserve. In the medium, to long term, we should maybe consider changing to `rustls` to have the same `tls` on all platforms. # 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-03-05 23:48:13 +01:00
ureq = { version = "2.6.2", default-features = false, features = ["json", "charset", "native-tls", "gzip"] }
native-tls = "0.2.11"
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 03:35:09 +01:00
roxmltree = "0.18.0"
Bump rust-embed from 6.4.1 to 6.6.0 (#8330) Bumps [rust-embed](https://github.com/pyros2097/rust-embed) from 6.4.1 to 6.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pyrossh/rust-embed/blob/master/changelog.md">rust-embed's changelog</a>.</em></p> <blockquote> <h2>[6.6.0] - 2023-03-05</h2> <ul> <li>sort_by_file_name() requires walkdir v2.3.2 <a href="https://github-redirect.dependabot.com/pyrossh/rust-embed/issues/206">#206</a></li> <li>Add <code>mime-guess</code> feature to statically store mimetype <a href="https://github-redirect.dependabot.com/pyrossh/rust-embed/issues/192">#192</a></li> </ul> <h2>[6.4.2] - 2022-10-20</h2> <ul> <li>Fail the proc macro if include/exclude are used without the feature <a href="https://github-redirect.dependabot.com/pyrossh/rust-embed/issues/187">#187</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/pyros2097/rust-embed/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rust-embed&package-manager=cargo&previous-version=6.4.1&new-version=6.6.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-03-06 04:36:14 +01:00
rust-embed = "6.6.0"
Fix mv data loss when changing folder case (step 1) (#6599) * Fix mv data loss when changing folder case (step 1) * Use same-file to detect when changing case on Windows
2022-09-23 20:09:31 +02:00
same-file = "1.0.6"
update base64 implementation to newer crate (#7739) # Description This PR updates the base64 crate, which has changed significantly, so all the base64 implementations had to be changed too. Tests pass. I hope that's enough. # User-Facing Changes None, except added a new character encoding imap-mutf7 as mutf7. # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-01-13 14:16:14 +01:00
serde = { version = "1.0.123", features = ["derive"] }
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
serde_urlencoded = "0.7.0"
update a few nushell dependencies (#6291) * update a few nushell dependencies * update a test
2022-08-10 21:56:15 +02:00
serde_yaml = "0.9.4"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01:00
sha2 = "0.10.0"
Look up git commit hash ourselves, drop libgit2 dependency (#5548)
2022-05-16 03:57:25 +02:00
# Disable default features b/c the default features build Git (very slow to compile)
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 19:59:11 +01:00
percent-encoding = "2.2.0"
rusqlite = { version = "0.28.0", features = ["bundled"], optional = true }
Bump sqlparser from 0.30.0 to 0.32.0 (#8428) Bumps [sqlparser](https://github.com/sqlparser-rs/sqlparser-rs) from 0.30.0 to 0.32.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sqlparser-rs/sqlparser-rs/blob/main/CHANGELOG.md">sqlparser's changelog</a>.</em></p> <blockquote> <h2>[0.32.0] 2023-03-6</h2> <h3>Added</h3> <ul> <li>Support ClickHouse <code>CREATE TABLE</code> with <code>ORDER BY</code> (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/824">#824</a>) - Thanks <a href="https://github.com/ankrgyl"><code>@​ankrgyl</code></a></li> <li>Support PostgreSQL exponentiation <code>^</code> operator (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/813">#813</a>) - Thanks <a href="https://github.com/michael-2956"><code>@​michael-2956</code></a></li> <li>Support <code>BIGNUMERIC</code> type in BigQuery (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/811">#811</a>) - Thanks <a href="https://github.com/togami2864"><code>@​togami2864</code></a></li> <li>Support for optional trailing commas (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/810">#810</a>) - Thanks <a href="https://github.com/ankrgyl"><code>@​ankrgyl</code></a></li> </ul> <h3>Fixed</h3> <ul> <li>Fix table alias parsing regression by backing out redshift column definition list (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/827">#827</a>) - Thanks <a href="https://github.com/alamb"><code>@​alamb</code></a></li> <li>Fix typo in <code>ReplaceSelectElement</code> <code>colum_name</code> --&gt; <code>column_name</code> (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/822">#822</a>) - Thanks <a href="https://github.com/togami2864"><code>@​togami2864</code></a></li> </ul> <h2>[0.31.0] 2023-03-1</h2> <h3>Added</h3> <ul> <li>Support raw string literals for BigQuery dialect (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/812">#812</a>) - Thanks <a href="https://github.com/togami2864"><code>@​togami2864</code></a></li> <li>Support <code>SELECT * REPLACE &lt;Expr&gt; AS &lt;Identifier&gt;</code> in BigQuery dialect (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/798">#798</a>) - Thanks <a href="https://github.com/togami2864"><code>@​togami2864</code></a></li> <li>Support byte string literals for BigQuery dialect (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/802">#802</a>) - Thanks <a href="https://github.com/togami2864"><code>@​togami2864</code></a></li> <li>Support columns definition list for system information functions in RedShift dialect (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/769">#769</a>) - Thanks <a href="https://github.com/mskrzypkows"><code>@​mskrzypkows</code></a></li> <li>Support <code>TRANSIENT</code> keyword in Snowflake dialect (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/807">#807</a>) - Thanks <a href="https://github.com/mobuchowski"><code>@​mobuchowski</code></a></li> <li>Support <code>JSON</code> keyword (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/799">#799</a>) - Thanks <a href="https://github.com/togami2864"><code>@​togami2864</code></a></li> <li>Support MySQL Character Set Introducers (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/788">#788</a>) - Thanks <a href="https://github.com/mskrzypkows"><code>@​mskrzypkows</code></a></li> </ul> <h3>Fixed</h3> <ul> <li>Fix clippy error in ci (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/803">#803</a>) - Thanks <a href="https://github.com/togami2864"><code>@​togami2864</code></a></li> <li>Handle offset in map key in BigQuery dialect (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/797">#797</a>) - Thanks <a href="https://github.com/Ziinc"><code>@​Ziinc</code></a></li> <li>Fix a typo (precendence -&gt; precedence) (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/794">#794</a>) - Thanks <a href="https://github.com/SARDONYX-sard"><code>@​SARDONYX-sard</code></a></li> <li>use post_* visitors for mutable visits (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/789">#789</a>) - Thanks <a href="https://github.com/lovasoa"><code>@​lovasoa</code></a></li> </ul> <h3>Changed</h3> <ul> <li>Add another known user (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/787">#787</a>) - Thanks <a href="https://github.com/joocer"><code>@​joocer</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/5f815c2b08e7e916412ed326ae425ada5bfa4c08"><code>5f815c2</code></a> (cargo-release) version 0.32.0</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/1d358592ab0052305ee8ec8da5bb4059eed36e34"><code>1d35859</code></a> Changelog for 0.32.0 (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/830">#830</a>)</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/7f4c9132d71029636f00a5c7ebe1d21898887c47"><code>7f4c913</code></a> Fix table alias parsing regression in 0.31.0 by backing out redshift column d...</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/d69b875367385cfc1d18296f390674cfc3729e4a"><code>d69b875</code></a> ClickHouse CREATE TABLE Fixes: add ORDER BY and fix clause ordering (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/824">#824</a>)</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/1cf913e7173a27897c0d198782e385de806dbcbd"><code>1cf913e</code></a> feat: Support PostgreSQL exponentiation. (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/813">#813</a>)</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/fbbf1a4e848bcaed8740854e91ce9e4481b2c115"><code>fbbf1a4</code></a> feat: support <code>BIGNUMERIC</code> of bigquery (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/811">#811</a>)</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/b45306819c34397fc65f116ab1cc85178ee1bb6e"><code>b453068</code></a> Add support for trailing commas (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/810">#810</a>)</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/2285bb44ba55f2256c17d72b33dc620573f225b6"><code>2285bb4</code></a> chore: fix typo (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/822">#822</a>)</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/b8384152769ec22febe143c471d9d2fa292c9d37"><code>b838415</code></a> (cargo-release) version 0.31.0</li> <li><a href="https://github.com/sqlparser-rs/sqlparser-rs/commit/66ec634c67173c661ef3dee6b02bed35f20a0f54"><code>66ec634</code></a> Update CHANGELOG for version 0.31 (<a href="https://redirect.github.com/sqlparser-rs/sqlparser-rs/issues/820">#820</a>)</li> <li>Additional commits viewable in <a href="https://github.com/sqlparser-rs/sqlparser-rs/compare/v0.30.0...v0.32.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sqlparser&package-manager=cargo&previous-version=0.30.0&new-version=0.32.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) --- **Note:** Dependabot was ignoring updates to this dependency, but since you've updated it yourself we've started tracking it for you again. 🤖 <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-03-15 18:33:09 +01:00
sqlparser = { version = "0.32.0", features = ["serde"], optional = true }
Fix CPU usage info in `sys` (#8321) Closes #8264. This PR does a few things to fix the `usage` column in `sys.cpu`: 1. Sleep a while (~400ms) between calls to `sys.refresh_cpu()`, [as required by `sysinfo`](https://docs.rs/sysinfo/latest/sysinfo/trait.SystemExt.html#method.refresh_cpu) 2. Change `sys` to return a `LazyRecord` (so you can do things like `sys | get host` instantly without waiting for CPU info) 3. Update our `sysinfo` dependency to [fix CPU usage calculations on Linux](https://github.com/GuillaumeGomez/sysinfo/pull/946) CPU usage is no longer always reported as zero: ![image](https://user-images.githubusercontent.com/26268125/222929775-5e9cbe18-95d9-4ecb-baf8-1e843f5c7086.png)
2023-03-04 23:48:34 +01:00
sysinfo = "0.28.2"
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 19:59:11 +01: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 18:18:06 +02:00
terminal_size = "0.2.1"
update crate thiserror to version 1.0.31 in crates nu-cli, nu-command, nu-parser, nu-protocol (#5919)
2022-06-30 22:55:01 +02:00
thiserror = "1.0.31"
update some dependencies (#6009) * update some dependencies * there may be some bugs here but it seems to compile and run * clippy
2022-07-11 18:18:06 +02:00
titlecase = "2.0.0"
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 21:15:14 +01: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 19:59:11 +01:00
unicode-segmentation = "1.10.0"
unicode-width = "0.1.10"
`du` command (#916) * wip on `du` command * working
2022-02-03 18:35:06 +01: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-22 00:32:52 +01: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 14:16:14 +01: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 19:59:11 +01: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 13:32:20 +01: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 03:01:31 +02:00
add a new command to query the registry on windows (#6670) * add a new command to query the registry on windows * cross platform tweaks * return nushell datatype * change visibility of exec and registry commands
2022-10-07 20:54:36 +02:00
[target.'cfg(windows)'.dependencies]
Bump winreg from 0.11.0 to 0.50.0 (#8837)
2023-04-14 14:15:01 +02:00
winreg = "0.50.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 20:54:36 +02: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 05:59:53 +01: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 19:59:11 +01:00
libc = "0.2"
Bump umask from 2.0.0 to 2.1.0 (#8835)
2023-04-14 14:15:22 +02:00
umask = "2.1.0"
Update some deps (#3011)
2021-02-05 21:54:54 +01: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 05:59:53 +01:00
Termux/Android target support for v0.60.0 (#4956) * Add android as target os for procfs-based ps * Turn off code for dealing with trash on platforms which are known to not support a standard trash protocol * Update lib.rs * Update lib.rs Co-authored-by: JT <547158+jntrnr@users.noreply.github.com>
2022-03-26 19:21:19 +01:00
[target.'cfg(not(any(target_os = "android", target_os = "ios")))'.dependencies.trash]
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 19:59:11 +01: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 19:21:19 +01:00
Dataframe feature (#361) * custom value trait * functions for custom value trait * custom trait behind flag * open dataframe command * command to-df for basic types * follow path for dataframe * dataframe operations * dataframe not default feature * custom as default feature * corrected examples in command
2021-11-23 09:14:40 +01:00
[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 18:45:09 +01:00
features = [
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 14:06:31 +02:00
"arg_where",
"checked_arithmetic",
"concat_str",
"cross_join",
"csv-file",
"cum_agg",
"default",
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 19:59:11 +01:00
"dtype-categorical",
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 14:06:31 +02: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-13 01:30:20 +02:00
"ipc",
lazy dataframe reader (#6321) * lazy dataframe reader * correct space for polars dependencies
2022-08-14 14:06:31 +02:00
"is_in",
"json",
"lazy",
"object",
"parquet",
"random",
"rolling_window",
"rows",
"serde",
"serde-lazy",
"strings",
"strings",
"to_dummies",
Migration of series commands (#515) * corrected missing shellerror type * batch dataframe commands * removed option to find declaration with input * ordered dataframe folders * dataframe command name * series commands * date commands * series commands * series commands * clippy correction * rename commands
2021-12-18 18:45:09 +01:00
]
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 19:59:11 +01: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-22 00:32:28 +01: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 09:14:40 +01:00
Fix `ls` for Windows system files (#5703) * Fix `ls` for Windows system files * Fix non-Windows builds * Make Clippy happy on non-Windows platforms * Fix new test on GitHub runners * Move ls Windows code into its own module
2022-06-03 18:37:27 +02:00
[target.'cfg(windows)'.dependencies.windows]
print nushell startup time (#7831) # Description This PR shows the startup time and decreases the banner. This startup time output can be disabled with the `show_banner: false` setting in the config. This is the startup in debug mode. ![image](https://user-images.githubusercontent.com/343840/213955410-f319f8d4-1f96-47ae-8366-1c564a08d3e4.png) On my mac in release mode ``` Startup Time: 368ms 429µs 83ns ``` On my mac without a config as `nu --config foo --env-config foo` ``` Startup Time: 11ms 663µs 791ns ``` I could really go either way on this. If people don't like this change, we don't have to merge it. # User-Facing Changes Startup Time # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-01-23 19:57:40 +01:00
features = ["Win32_Foundation", "Win32_Storage_FileSystem", "Win32_System_SystemServices"]
Bump windows from 0.46.0 to 0.48.0 (#8721) Bumps [windows](https://github.com/microsoft/windows-rs) from 0.46.0 to 0.48.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/windows-rs/releases">windows's releases</a>.</em></p> <blockquote> <h2>0.48.0</h2> <p>This release includes an update to all crates to address a target version reliability issue. This issue is detailed here: <a href="https://redirect.github.com/microsoft/windows-rs/issues/2410#issuecomment-1490802715">microsoft/windows-rs#2410</a></p> <h2>What's Changed</h2> <ul> <li>Improve target version reliability by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2412">microsoft/windows-rs#2412</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0">https://github.com/microsoft/windows-rs/compare/0.47.0...0.48.0</a></p> <h2>0.47.0</h2> <p>As a reminder, updates are only published by request (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2397">#2397</a>; <a href="https://redirect.github.com/microsoft/win32metadata/issues/1507">microsoft/win32metadata#1507</a>). This release provides an update to the <code>windows</code> crate. It does not include an update to the <code>windows-sys</code> crate.</p> <p>This update adds support for standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>) as well as requested fixes to the Win32 metadata that prevented some APIs from being used.</p> <h2>What's Changed</h2> <ul> <li>Workaround for <code>rustdoc</code> regression by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2381">microsoft/windows-rs#2381</a></li> <li>Token privilege samples by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2382">microsoft/windows-rs#2382</a></li> <li>Apply <code>const</code> parameter metadata by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2384">microsoft/windows-rs#2384</a></li> <li>Advanced metadata filtering by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2385">microsoft/windows-rs#2385</a></li> <li>Update Win32 metadata v46 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2387">microsoft/windows-rs#2387</a></li> <li>Support standalone code generation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2396">microsoft/windows-rs#2396</a></li> <li>Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2399">microsoft/windows-rs#2399</a></li> <li>Update Win32 metadata v47 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2400">microsoft/windows-rs#2400</a></li> <li>Version 0.47.0 by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2401">microsoft/windows-rs#2401</a></li> <li>Add CLR test for lib validation by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2403">microsoft/windows-rs#2403</a></li> <li>Restore reproducible libs by <a href="https://github.com/riverar"><code>@​riverar</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2402">microsoft/windows-rs#2402</a></li> <li>Check diff for all targets by <a href="https://github.com/kennykerr"><code>@​kennykerr</code></a> in <a href="https://redirect.github.com/microsoft/windows-rs/pull/2404">microsoft/windows-rs#2404</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0">https://github.com/microsoft/windows-rs/compare/0.46.0...0.47.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/windows-rs/commit/406944152ef28d3273236edc958c2bfbf825775d"><code>4069441</code></a> Improve target version reliability (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2412">#2412</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/ec95c1e6ac1eeabb6f8c91c41d0197ecf43fa75c"><code>ec95c1e</code></a> Check diff for all targets (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2404">#2404</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/91e0a5c0793476bdbd355e3487b7c9580f12f558"><code>91e0a5c</code></a> Restore reproducible libs (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2402">#2402</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/36ea325a8debcb7de885c7f6ede8baada9bb2a4c"><code>36ea325</code></a> Add CLR test for lib validation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2403">#2403</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/e03d14e2d0898f85bc2573f13dcd46929f971a87"><code>e03d14e</code></a> Version 0.47.0 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2401">#2401</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f86349d6915714c0a05ef181af20b62ddfcc125c"><code>f86349d</code></a> Update Win32 metadata v47 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2400">#2400</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3e3c87b5ed5d500e87a31fede90fd8d35df60fa9"><code>3e3c87b</code></a> Update readme to include <code>windows-targets</code> and <code>windows-bindgen</code> (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2399">#2399</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/6672c6d28a629fcdaf8eea8c1531e92980bf8d4c"><code>6672c6d</code></a> Support standalone code generation (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2396">#2396</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/f3ef2cdfa7d812f1951d0421999fd1bbfa9fb7ae"><code>f3ef2cd</code></a> Update Win32 metadata v46 (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2387">#2387</a>)</li> <li><a href="https://github.com/microsoft/windows-rs/commit/3507dcd3b183b3dc67f7658d194635c0c5c4c92b"><code>3507dcd</code></a> Advanced metadata filtering (<a href="https://redirect.github.com/microsoft/windows-rs/issues/2385">#2385</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/windows-rs/compare/0.46.0...0.48.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=windows&package-manager=cargo&previous-version=0.46.0&new-version=0.48.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-04-05 23:54:26 +02:00
version = "0.48.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 18:37:27 +02:00
add rm command + stubs for open and save
2021-10-10 06:13:15 +02: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 19:59:11 +01:00
dataframe = ["num", "polars", "sqlparser"]
plugin feature flag
2021-11-02 21:56:00 +01: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 19:57:40 +01: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 19:59:11 +01: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 05:59:53 +01:00
[dev-dependencies]
Bump to `0.78.1` development version (#8741) # Description either just development or hotfix
2023-04-05 03:36:10 +02:00
nu-test-support = { path = "../nu-test-support", version = "0.78.1" }
Bump mockito from 0.32.5 to 1.0.0 (#8426) Bumps [mockito](https://github.com/lipanski/mockito) from 0.32.5 to 1.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lipanski/mockito/releases">mockito's releases</a>.</em></p> <blockquote> <h2>1.0.0</h2> <p>:balloon: 7 years and 63 releases later, it's finally time for the 1.0 :balloon:</p> <h2>Changes</h2> <ul> <li><strong>[Breaking]</strong> The legacy interface was removed in this version</li> <li><strong>[Breaking]</strong> <code>Mock::with_body_from_fn</code> was renamed to <code>Mock::with_chunked_body</code> - the former is still supported with a deprecation warning</li> <li>Mocks are only cleared when the server is dropped, not when the mock is dropped - this means you <strong>don't have to assign mocks to variables any more</strong> (unless you want to call other methods on them)</li> <li>Introduced the <code>Mock::remove</code> and <code>Mock::remove_async</code> methods to remove mocks on demand</li> </ul> <h2>Major changes since 0.31</h2> <ul> <li>Tests can now run in parallel</li> <li>Support for HTTP2</li> <li>An async interface for all actions (though the sync interface is also available)</li> <li>Mock multiple server/hosts at the same time</li> </ul> <p>For a list of all the changes please check the <a href="https://github.com/lipanski/mockito/releases">release log</a>.</p> <h2>Migrating to the new API</h2> <p>Legacy API:</p> <pre lang="rust"><code>let m1 = mockito::mock(&quot;GET&quot;, &quot;/hello&quot;).with_body(&quot;hello&quot;).create(); let m2 = mockito::mock(&quot;GET&quot;, &quot;/bye&quot;).with_body(&quot;bye&quot;).create(); <p>// Use one of these to configure your client let host = mockito:server_address(); let url = mockito::server_url(); </code></pre></p> <p>New API:</p> <pre lang="rust"><code>let mut server = mockito::Server::new(); server.mock(&quot;GET&quot;, &quot;/hello&quot;).with_body(&quot;hello&quot;).create(); server.mock(&quot;GET&quot;, &quot;/bye&quot;).with_body(&quot;bye&quot;).create(); <p>// Use one of these to configure your client let host = server.host_with_port(); let url = server.url(); </code></pre></p> <blockquote> <p>If you can't migrate to the new API in one go, consider using version 0.32.5, which supports both the legacy API as well as the new API.</p> </blockquote> <h2>Migrating to the async API</h2> <p>In order to write async tests, you'll need to use the <code>_async</code> methods:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lipanski/mockito/commit/9a07811955104fbe5e4f4fd4a35571bc37d06db1"><code>9a07811</code></a> Bump to 1.0.0</li> <li><a href="https://github.com/lipanski/mockito/commit/000c435f0e0e6b3d484e6d0feeffe9608fe7190e"><code>000c435</code></a> Merge pull request <a href="https://redirect.github.com/lipanski/mockito/issues/165">#165</a> from lipanski/one-zero</li> <li><a href="https://github.com/lipanski/mockito/commit/68c56290a142a64252514ee183ed25ad4b3b46bd"><code>68c5629</code></a> Remove mocks when the server is dropped, not when the mock is dropped</li> <li><a href="https://github.com/lipanski/mockito/commit/ac9042d02286b3e5fd5e0187a0edf4d20e09b5d7"><code>ac9042d</code></a> Add the Windows line-ending fix to the test runner</li> <li><a href="https://github.com/lipanski/mockito/commit/0ce9788e00c4d9b671ef5a49deb1925556445645"><code>0ce9788</code></a> Disable color tests on Windows</li> <li><a href="https://github.com/lipanski/mockito/commit/ad2ebcbaab7697119f4f5ac7d798999b7be5df5a"><code>ad2ebcb</code></a> Fine-tuning the Windows test runner</li> <li><a href="https://github.com/lipanski/mockito/commit/abb9e91d7180f85899760e2c26afd93b39e10170"><code>abb9e91</code></a> Run Windows tests on Github Actions</li> <li><a href="https://github.com/lipanski/mockito/commit/5a7c96eaecb2c160ceb6cddaa26eec2fb7e27ac0"><code>5a7c96e</code></a> Rename Mock::with_body_from_fn to Mock::with_chunked_body</li> <li><a href="https://github.com/lipanski/mockito/commit/ed338faedf5d701e04d6a46af07911cecf06377c"><code>ed338fa</code></a> Uncomment threads tests</li> <li><a href="https://github.com/lipanski/mockito/commit/6e2064de9516a06d8d252ffe61d570e5915123d3"><code>6e2064d</code></a> Drop legacy interface</li> <li>Additional commits viewable in <a href="https://github.com/lipanski/mockito/compare/0.32.5...1.0.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=mockito&package-manager=cargo&previous-version=0.32.5&new-version=1.0.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-03-16 11:40:49 +01:00
mockito = "1.0.0"
Move nu-test-support into dev deps on nu-command (#6940) This reduces the number of dependencies to build for `cargo build` or `cargo run` by around 19. Will not speed up CI as we need to `cargo test` but should help for `cargo install` or users just building from source. Time saved on my machine ~0.8 secs so likely unnoticable in noise. Larger future goal is reducing longer dependency chains to allow more parallel compilation.
2022-10-29 19:39:27 +02:00
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
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 19:59:11 +01:00
hamcrest2 = "0.3.0"
Add initial nu-test-support port (#913) * Add initial nu-test-support port * finish changing binary name * Oops, these aren't Windows-safe tests
2022-02-02 21:59:01 +01:00
quickcheck = "1.0.3"
list keybinding options (#906) * list keybinding optins * list keybinding options * clippy error
2022-02-04 07:47:18 +01:00
quickcheck_macros = "1.0.0"
Bump rstest from 0.16.0 to 0.17.0 (#8534)
2023-03-20 18:27:29 +01:00
rstest = { version = "0.17.0", default-features = false }
Reference in New Issue Copy Permalink