holm/nushell
1
1
Fork 0
forked from extern/nushell
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a33b5fe6ce
nushell/crates/nu-table/Cargo.toml

23 lines
718 B
TOML
Raw Normal View History

Nu table (#2015) * WIP * Get ready to land nu-table * Remove unwrap
2020-06-20 05:41:53 +02:00
[package]
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test
2022-03-13 19:30:27 +01:00
authors = ["The Nushell Project Developers"]
Nu table (#2015) * WIP * Get ready to land nu-table * Remove unwrap
2020-06-20 05:41:53 +02:00
description = "Nushell table printing"
Add repository info to all workspace crates (#6320) This helps people who find these crates on crates.io
2022-08-14 14:21:20 +02:00
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-table"
update all cargo crates to edition 2021 (#781)
2022-01-20 14:13:45 +01:00
edition = "2021"
Add a very silly table
2021-09-10 04:27:12 +02:00
license = "MIT"
name = "nu-table"
bump to 0.83 (#9802) # Description Bump 0.83 # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` 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. -->
2023-07-25 21:36:36 +02:00
version = "0.83.0"
Nu table (#2015) * WIP * Get ready to land nu-table * Remove unwrap
2020-06-20 05:41:53 +02:00
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
Nu table (#2015) * WIP * Get ready to land nu-table * Remove unwrap
2020-06-20 05:41:53 +02:00
[dependencies]
bump to 0.83 (#9802) # Description Bump 0.83 # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` 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. -->
2023-07-25 21:36:36 +02:00
nu-protocol = { path = "../nu-protocol", version = "0.83.0" }
nu-utils = { path = "../nu-utils", version = "0.83.0" }
nu-engine = { path = "../nu-engine", version = "0.83.0" }
nu-color-config = { path = "../nu-color-config", version = "0.83.0" }
Update `nu-ansi-term`, `lscolors`, and `reedline` (#9787) # Description Now use `nu-ansi-term` 0.49 Small adjustments to accommodate breaking changes. # User-Facing Changes None
2023-07-24 13:16:18 +02:00
nu-ansi-term = "0.49.0"
nu-table: Bump tabled to 0.12.1 (#9341) close #9335 I am not sure whether the fix was better to be delived as a minor bump but it is what is is. Could you @fdncred test it somehow? I did it by checking out back the the original commit before the PR refered in the issue. --------- Signed-off-by: Maxim Zhiburt <zhiburt@gmail.com> Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-06-12 00:33:54 +02:00
tabled = { version = "0.12.2", features = ["color"], default-features = false }
Remove unused deps or move to devdeps (#7537) # Description General tree shaking through `cargo +nightly udeps` and moving mentions of `nu-test-support` to the dev deps. Also since #7488 no separate import of `nu-path` necessary cc @webbedspace
2022-12-20 00:53:17 +01:00
[dev-dependencies]
bump to 0.83 (#9802) # Description Bump 0.83 # 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 -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` 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. -->
2023-07-25 21:36:36 +02:00
# nu-test-support = { path="../nu-test-support", version = "0.83.0" }
Reference in New Issue Copy Permalink