nushell/crates/nu-command/Cargo.toml

168 lines
4.7 KiB
TOML
Raw Normal View History

[package]
authors = ["The Nushell Project Developers"]
description = "Nushell's built-in commands"
edition = "2021"
license = "MIT"
name = "nu-command"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-command"
version = "0.78.1"
2021-09-02 01:29:43 +00:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[lib]
bench = false
2021-09-02 01:29:43 +00:00
[dependencies]
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" }
2022-10-10 11:25:57 +00:00
num-format = { version = "0.4.3" }
2021-09-10 01:06:44 +00:00
2023-03-14 18:46:42 +00:00
nu-ansi-term = "0.47.0"
2021-09-10 01:06:44 +00:00
# Potential dependencies for extras
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
Inflector = "0.11"
alphanumeric-sort = "1.5.0"
atty = "0.2.14"
base64 = "0.21.0"
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 06:48:14 +00:00
bytesize = "1.2.0"
calamine = "0.19.1"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
chrono = { version = "0.4.23", features = ["std", "unstable-locales"], default-features = false }
2021-10-31 06:54:51 +00:00
chrono-humanize = "0.2.1"
chrono-tz = "0.8.1"
crossterm = "0.24.0"
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 06:48:51 +00:00
csv = "1.2.0"
dialoguer = { default-features = false, version = "0.10.3" }
digest = { default-features = false, version = "0.10.0" }
dtparse = "1.2.0"
encoding_rs = "0.8.30"
fancy-regex = "0.11.0"
filesize = "0.2.0"
filetime = "0.2.15"
fs_extra = "1.3.0"
htmlescape = "0.3.1"
indexmap = { version = "1.7", features = ["serde-1"] }
Progress bar Implementation (#7661) # Description _(Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience.)_ I implemented the status bar we talk about yesterday. The idea was inspired by the progress bar of `wget`. I decided to go for the second suggestion by `@Reilly` > 2. add an Option<usize> or whatever to RawStream (and ListStream?) for situations where you do know the length ahead of time For now only works with the command `save` but after the approve of this PR we can see how we can implement it on commands like `cp` and `mv` When using `fetch` nushell will check if there is any `content-length` attribute in the request header. If so, then `fetch` will send it through the new `Option` variable in the `RawStream` to the `save`. If we know the total size we show the progress bar ![nu_pb01](https://user-images.githubusercontent.com/38369407/210298647-07ee55ea-e751-41b1-a84d-f72ec1f6e9e5.jpg) but if we don't then we just show the stats like: data already saved, bytes per second, and time lapse. ![nu_pb02](https://user-images.githubusercontent.com/38369407/210298698-1ef65f51-40cc-4481-83de-309cbd1049cb.jpg) ![nu_pb03](https://user-images.githubusercontent.com/38369407/210298701-eef2ef13-9206-4a98-8202-e4fe5531d79d.jpg) Please let me know If I need to make any changes and I will be happy to do it. # User-Facing Changes A new flag (`--progress` `-p`) was added to the `save` command Examples: ```nu fetch https://github.com/torvalds/linux/archive/refs/heads/master.zip | save --progress -f main.zip fetch https://releases.ubuntu.com/22.04.1/ubuntu-22.04.1-desktop-amd64.iso | save --progress -f main.zip open main.zip --raw | save --progress main.copy ``` # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - I am getting some errors and its weird because the errors are showing up in files i haven't touch. Is this normal? # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. Co-authored-by: Reilly Wood <reilly.wood@icloud.com>
2023-01-11 01:57:48 +00:00
indicatif = "0.17.2"
is-root = "0.1.2"
itertools = "0.10.0"
log = "0.4.14"
lscolors = { version = "0.12.0", features = ["crossterm"], default-features = false }
md5 = { package = "md-5", version = "0.10.0" }
Bump miette from 5.5.0 to 5.6.0 (#8531) Bumps [miette](https://github.com/zkat/miette) from 5.5.0 to 5.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zkat/miette/blob/main/CHANGELOG.md">miette's changelog</a>.</em></p> <blockquote> <h2>5.6.0 (2023-03-14)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>ci:</strong> configure clippy-specific MSRV (<a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747">b658fc02</a>)</li> <li><strong>graphical:</strong> Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>) (<a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0">3497508a</a>)</li> <li><strong>atty:</strong> Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>) (<a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e">443d240f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>protocol:</strong> implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>) (<a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d">ed486c95</a>)</li> </ul> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zkat/miette/commit/78fe18e6990feacc8bdaeeb10e1439a12c111e6e"><code>78fe18e</code></a> chore: Release</li> <li><a href="https://github.com/zkat/miette/commit/2335b25ee7d22bd4ef4e1ef1dd9527fe2accd2be"><code>2335b25</code></a> docs: update changelog</li> <li><a href="https://github.com/zkat/miette/commit/443d240f49e9f48756ee88e4cdc377f09d44454e"><code>443d240</code></a> fix(atty): Switch out <code>atty</code> for <code>is-terminal</code> (<a href="https://redirect.github.com/zkat/miette/issues/229">#229</a>)</li> <li><a href="https://github.com/zkat/miette/commit/ed486c959d8e8fbd4247af7d47d7e32c8a88321d"><code>ed486c9</code></a> feat(protocol): implement <code>Ord</code> for <code>Severity</code> (<a href="https://redirect.github.com/zkat/miette/issues/240">#240</a>)</li> <li><a href="https://github.com/zkat/miette/commit/3497508aa9b8d8503d7aae997738a4323408ffa0"><code>3497508</code></a> fix(graphical): Fix wrong severity of related errors (<a href="https://redirect.github.com/zkat/miette/issues/234">#234</a>)</li> <li><a href="https://github.com/zkat/miette/commit/b658fc020b23b0715339c5c60f7c12c947f9a747"><code>b658fc0</code></a> fix(ci): configure clippy-specific MSRV</li> <li><a href="https://github.com/zkat/miette/commit/ebc61b5cf809e4215ca92c32d892cfc4ffb05fa9"><code>ebc61b5</code></a> docs: Mention miette::miette! macro under &quot;... in application code&quot; (<a href="https://redirect.github.com/zkat/miette/issues/233">#233</a>)</li> <li><a href="https://github.com/zkat/miette/commit/14f952dc91b9f27b7ae1e9e03b89744bcc682fa2"><code>14f952d</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li><a href="https://github.com/zkat/miette/commit/128c0a1fae0b578b2de5c8967b87df0d89cd1c54"><code>128c0a1</code></a> (cargo-release) start next development iteration 5.5.1-alpha.0</li> <li>See full diff in <a href="https://github.com/zkat/miette/compare/miette-derive-v5.5.0...miette-derive-v5.6.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=miette&package-manager=cargo&previous-version=5.5.0&new-version=5.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-24 09:55:25 +00:00
miette = { version = "5.6.0", features = ["fancy-no-backtrace"] }
mime = "0.3.16"
add `--mime-type(-m)` to `ls` in the `type` column (#7616) # Description This PR adds the `mime-type` to the `type` column if you add the `--mime-type(-m)` flag to `ls`. <img width="853" alt="Screenshot 2022-12-27 at 11 43 20 AM" src="https://user-images.githubusercontent.com/343840/209705499-27fe40fe-0356-4d9d-97f2-4b2dc52e0963.png"> <img width="781" alt="Screenshot 2022-12-27 at 11 45 53 AM" src="https://user-images.githubusercontent.com/343840/209705509-4d677389-fd68-401e-a7af-3fc6052743b6.png"> # User-Facing Changes If you specify the `-m` flag, you get the "guessed at" mime type. The guess is based on the file name and uses this crate https://docs.rs/mime_guess/latest/mime_guess/ for the guessing. Part of issue #7612 and and #7524 There's some debate on if the `mime-type` should be added to the `type` column or if there should be a separate `mime` column. I tend to lean on the side of `type` since it's technically a type and it's only in that column if you ask it to be there. Also, I'd prefer to reuse a column rather than having a list of sprawling columns. Also, as @KodiCraft suggested, there is precedence as with `ls -d` where the summed size is in the size column. I could go either way and if someone wants to create a `mime` column, we'd probably accept it. # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2022-12-27 18:46:23 +00:00
mime_guess = "2.0.4"
notify = "4.0.17"
num = { version = "0.4.0", optional = true }
num-traits = "0.2.14"
once_cell = "1.17"
2023-03-15 18:41:39 +00:00
open = "4.0.0"
pathdiff = "0.2.1"
powierza-coefficient = "1.0.2"
quick-xml = "0.28"
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 03:32:16 +00:00
rayon = "1.7.0"
2023-01-23 01:44:10 +00: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 22:48:13 +00: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 02:35:09 +00: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 03:36:14 +00:00
rust-embed = "6.6.0"
same-file = "1.0.6"
serde = { version = "1.0.123", features = ["derive"] }
serde_urlencoded = "0.7.0"
serde_yaml = "0.9.4"
sha2 = "0.10.0"
# Disable default features b/c the default features build Git (very slow to compile)
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
percent-encoding = "2.2.0"
reedline = { version = "0.18.0", features = ["bashisms", "sqlite"] }
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
rusqlite = { version = "0.28.0", features = ["bundled"], optional = true }
Bump 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 17:33:09 +00:00
sqlparser = { version = "0.32.0", features = ["serde"], optional = true }
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 18:59:11 +00:00
tabled = "0.10.0"
terminal_size = "0.2.1"
thiserror = "1.0.31"
titlecase = "2.0.0"
toml = "0.7.1"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
unicode-segmentation = "1.10.0"
unicode-width = "0.1.10"
url = "2.2.1"
Bump uuid from 1.2.2 to 1.3.0 (#8130) Bumps [uuid](https://github.com/uuid-rs/uuid) from 1.2.2 to 1.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/uuid-rs/uuid/releases">uuid's releases</a>.</em></p> <blockquote> <h2>1.3.0</h2> <h2>What's Changed</h2> <ul> <li>Fix error message. by <a href="https://github.com/basbossink-ds"><code>@​basbossink-ds</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/656">uuid-rs/uuid#656</a></li> <li>implement Arbitrary::size_hint by <a href="https://github.com/Ekleog"><code>@​Ekleog</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/657">uuid-rs/uuid#657</a></li> <li>Always use hyphenated format regardless of flags by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/658">uuid-rs/uuid#658</a></li> <li>Update windows-sys requirement from 0.42.0 to 0.45.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/654">uuid-rs/uuid#654</a></li> <li>Prepare for 1.3.0 release by <a href="https://github.com/KodrAus"><code>@​KodrAus</code></a> in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/659">uuid-rs/uuid#659</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/basbossink-ds"><code>@​basbossink-ds</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/656">uuid-rs/uuid#656</a></li> <li><a href="https://github.com/Ekleog"><code>@​Ekleog</code></a> made their first contribution in <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/pull/657">uuid-rs/uuid#657</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/uuid-rs/uuid/compare/1.2.2...1.3.0">https://github.com/uuid-rs/uuid/compare/1.2.2...1.3.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/uuid-rs/uuid/commit/573362627c354bd13432e9aa9cdc3465e00aaff3"><code>5733626</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/659">#659</a> from uuid-rs/cargo/1.3.0</li> <li><a href="https://github.com/uuid-rs/uuid/commit/59ac0470146d8c4ee73c57475993468302f6d2a6"><code>59ac047</code></a> prepare for 1.3.0 release</li> <li><a href="https://github.com/uuid-rs/uuid/commit/e01078785036347100a0e992e05e6ef121df13f0"><code>e010787</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/654">#654</a> from uuid-rs/dependabot/cargo/windows-sys-0.45.0</li> <li><a href="https://github.com/uuid-rs/uuid/commit/b90b8206035b3c22b6b9762c12fc5208d2cabbf0"><code>b90b820</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/658">#658</a> from uuid-rs/fix/alternate-format</li> <li><a href="https://github.com/uuid-rs/uuid/commit/1af8269957b784650ea39cd4b114e575d1b96c12"><code>1af8269</code></a> fix up tests around alternative format</li> <li><a href="https://github.com/uuid-rs/uuid/commit/e7eaf5b4a2f37c1742d06ccf37bae7f83ce3b00d"><code>e7eaf5b</code></a> always use hyphenated format regardless of flags</li> <li><a href="https://github.com/uuid-rs/uuid/commit/52197cd2752e9e57c6adf5f58bfd00c830e8241d"><code>52197cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/657">#657</a> from Ekleog/arbitrary-size-hint</li> <li><a href="https://github.com/uuid-rs/uuid/commit/b362542ee26e9e29b996994f6a1cd25c3c3b8e00"><code>b362542</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/uuid-rs/uuid/issues/656">#656</a> from basbossink-ds/fix/655-deserialize-error-msg</li> <li><a href="https://github.com/uuid-rs/uuid/commit/212b90227712d47b564347f6c67c258812c5a56c"><code>212b902</code></a> implement Arbitrary::size_hint</li> <li><a href="https://github.com/uuid-rs/uuid/commit/40d8711f11e603f9ea01e192e30f087b969b27eb"><code>40d8711</code></a> Also fix the doc comment</li> <li>Additional commits viewable in <a href="https://github.com/uuid-rs/uuid/compare/1.2.2...1.3.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=uuid&package-manager=cargo&previous-version=1.2.2&new-version=1.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-21 23:32:52 +00:00
uuid = { version = "1.3.0", features = ["v4"] }
wax = { version = "0.5.0" }
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
which = { version = "4.4.0", optional = true }
`string | fill` counts clusters, not graphemes; and doesn't count ANSI escape codes (#8134) Enhancement of new `fill` command (#7846) to handle content including ANSI escape codes for formatting or multi-code-point Unicode grapheme clusters. In both of these cases, the content is (many) bytes longer than its visible length, and `fill` was counting the extra bytes so not adding enough fill characters. # Description This script: ```rust # the teacher emoji `\u{1F9D1}\u{200D}\u{1F3EB}` is 3 code points, but only 1 print position wide. echo "This output should be 3 print positions wide, with leading and trailing `+`" $"\u{1F9D1}\u{200D}\u{1F3EB}" | fill -c "+" -w 3 -a "c" echo "This output should be 3 print positions wide, with leading and trailing `+`" $"(ansi green)a(ansi reset)" | fill -c "+" -w 3 -a c echo "" ``` Was producing this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` 🧑‍🏫 This output should be 3 print positions wide, with leading and trailing `+` a ``` After this PR, it produces this output: ```rust This output should be 3 print positions wide, with leading and trailing `+` +🧑‍🏫+ This output should be 3 print positions wide, with leading and trailing `+` +a+ ``` # User-Facing Changes Users may have to undo fixes they may have introduced to work around the former behavior. I have one such in my prompt string that I can now revert. # Tests + Formatting Don't forget to add tests that cover your changes. -- Done Make sure you've run and fixed any issues with these commands: - [x] `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - [x] `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - [x] `cargo test --workspace` to check that all tests pass # After Submitting `fill` command not documented in the book, and it still talks about `str lpad/rpad`. I'll fix. Note added dependency on a new library `print-positions`, which is an iterator that yields a complete print position (cluster + Ansi sequence) per call. Should this be vendored?
2023-02-20 12:32:20 +00:00
print-positions = "0.6.1"
[target.'cfg(windows)'.dependencies]
Bump winreg from 0.10.1 to 0.11.0 (#8128) Bumps [winreg](https://github.com/gentoo90/winreg-rs) from 0.10.1 to 0.11.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gentoo90/winreg-rs/blob/master/CHANGELOG.md">winreg's changelog</a>.</em></p> <blockquote> <h2>0.11.0</h2> <ul> <li>Migrate to the 2018 edition of Rust</li> <li>Move the code from <code>lib.rs</code> to separate files</li> <li>Use <a href="https://crates.io/crates/cfg-if"><code>cfg-if</code></a> instead of <code>build.rs</code> to fail build on non-windows systems</li> <li>Reimplement deserialization logic, implement [de]serialization for byte arrays (<a href="https://github-redirect.dependabot.com/gentoo90/winreg-rs/issues/49">#49</a>)</li> <li>Fix some typos and <code>clippy</code> warnings</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f34742d674fd3472bdad036849fe888e6474c07e"><code>f34742d</code></a> Bump version to 0.11.0</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/75f2593f6285d06aea031db9cfed3be0bdfd40aa"><code>75f2593</code></a> Move the changelog to a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/1f6f877ed73c5b94dd81b883c3acb3f9d14ffd85"><code>1f6f877</code></a> Fix some clippy warnings</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/7a32d642cd8489ab827f0fce984011b67d26672d"><code>7a32d64</code></a> Implement [de]serialization for byte arrays</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/8464557c2d75b6397571b25c0e93195aed29b05d"><code>8464557</code></a> Reimplement deserialization logic</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/9e8dc28029ffeb14fdff76a30c896e8b52825533"><code>9e8dc28</code></a> Put serialization tests into a separate file</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/04f7d232c7abaf6069020c52b8da77f9f1e5f5f2"><code>04f7d23</code></a> Use <code>cfg-if</code> to fail build on non-windows systems</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/c3ac5ba5eaa83916c2fbad270bb1a83fee9f7715"><code>c3ac5ba</code></a> Move the code from <code>lib.rs</code> to separate files</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/17378a9ca4c1f8fc2dc668a5dfe2f5d6bd54cc82"><code>17378a9</code></a> Migrate to the 2018 edition of Rust</li> <li><a href="https://github.com/gentoo90/winreg-rs/commit/f4d45923abf53b1aee8f9f7e2f002c459a97b717"><code>f4d4592</code></a> Remove Appveyor. It's broken anyway</li> <li>Additional commits viewable in <a href="https://github.com/gentoo90/winreg-rs/compare/v0.10.1...v0.11.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=winreg&package-manager=cargo&previous-version=0.10.1&new-version=0.11.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-20 02:57:46 +00:00
winreg = "0.11.0"
[target.'cfg(unix)'.dependencies]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
libc = "0.2"
umask = "2.0.0"
2021-02-05 20:54:54 +00:00
users = "0.11.0"
[target.'cfg(not(any(target_os = "android", target_os = "ios")))'.dependencies.trash]
optional = true
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
version = "3.0.1"
[dependencies.polars]
features = [
"arg_where",
"checked_arithmetic",
"concat_str",
"cross_join",
"csv-file",
"cum_agg",
"default",
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
"dtype-categorical",
"dtype-datetime",
"dtype-struct",
"dynamic_groupby",
"ipc",
"is_in",
"json",
"lazy",
"object",
"parquet",
"random",
"rolling_window",
"rows",
"serde",
"serde-lazy",
"strings",
"strings",
"to_dummies",
]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
optional = true
version = "0.27.2"
[target.'cfg(windows)'.dependencies.windows]
features = ["Win32_Foundation", "Win32_Storage_FileSystem", "Win32_System_SystemServices"]
version = "0.46.0"
[features]
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
dataframe = ["num", "polars", "sqlparser"]
2021-11-02 20:56:00 +00:00
plugin = ["nu-parser/plugin"]
sqlite = ["rusqlite"] # TODO: given that rusqlite is included in reedline, should we just always include it?
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
trash-support = ["trash"]
which-support = ["which"]
[dev-dependencies]
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 10:40:49 +00:00
mockito = "1.0.0"
dirs-next = "2.0.0"
add a new inspect command for more debugging (#8028) # Description The purpose of this command is to help to debug pipelines. It works by allowing you to inject the `inspect` command into a pipeline at any point. Then it shows you what the input description is and what the input values are that are passed into `inspect`. With each step it prints this information out while also passing the value information on to the next step in the pipeline. ![image](https://user-images.githubusercontent.com/343840/218154064-e107859b-d0da-41c6-8e34-2d717639b81c.png) This command is kind of a "hack job" because it clones maybe too much and I had to get creative in order to output two different tables. I'm sure there are many ways this can be improved or combined into other commands but I wanted to start here. Note that the `inspect` output is written to stderr and the normal nushell output is written to stdout. If we were to output both to stdout, nushell would get confused. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date.
2023-02-11 18:59:11 +00:00
hamcrest2 = "0.3.0"
quickcheck = "1.0.3"
quickcheck_macros = "1.0.0"
rstest = { version = "0.17.0", default-features = false }