extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-11-22 08:23:24 +01:00
Code Issues Packages Projects Releases Wiki Activity
029c586717
nushell/crates/nu-table/Cargo.toml

27 lines
830 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 dev version 0.100.1 (#14328)
2024-11-14 10:04:39 +01:00
version = "0.100.1"
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
Setup global `cargo` lint configuration (#13691) # Description `cargo` somewhat recently gained the capability to store `lints` settings for the crate and workspace, that can override the defaults from `rustc` and `clippy` lints. This means we can enforce some lints without having to actively pass them to clippy via `cargo clippy -- -W ...`. So users just forking the repo have an easier time to follow similar requirements like our CI. ## Limitation An exception that remains is that those lints apply to both the primary code base and the tests. Thus we can't include e.g. `unwrap_used` without generating noise in the tests. Here the setup in the CI remains the most helpful. ## Included lints - Add `clippy::unchecked_duration_subtraction` (added by #12549) # User-Facing Changes Running `cargo clippy --workspace` should be closer to the CI. This has benefits for editor configured runs of clippy and saves you from having to use `toolkit` to be close to CI in more cases.
2024-08-28 23:37:17 +02:00
[lints]
workspace = true
Nu table (#2015) * WIP * Get ready to land nu-table * Remove unwrap
2020-06-20 05:41:53 +02:00
[dependencies]
Bump to dev version 0.100.1 (#14328)
2024-11-14 10:04:39 +01:00
nu-protocol = { path = "../nu-protocol", version = "0.100.1" }
nu-utils = { path = "../nu-utils", version = "0.100.1" }
nu-engine = { path = "../nu-engine", version = "0.100.1" }
nu-color-config = { path = "../nu-color-config", version = "0.100.1" }
Introduce workspace dependencies (#12043) # Description This PR introduces [workspaces dependencies](https://doc.rust-lang.org/cargo/reference/workspaces.html#the-dependencies-table). The advantages are: - a single place where dependency versions are declared - reduces the number of files to change when upgrading a dependency - reduces the risk of accidentally depending on 2 different versions of the same dependency I've only done a few so far. If this PR is accepted, I might continue and progressively do the rest. # User-Facing Changes N/A # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib` # After Submitting N/A
2024-03-07 23:40:31 +01:00
nu-ansi-term = { workspace = true }
fancy-regex = { workspace = true }
[DRAFT] Check fix for emojie, wrap issues (#13430) Hi there Here I am using latest tabled. My tests shows it does fixes panics, but I am wanna be sure. @fdncred could you verify that it does fixes those panics/errors? Closes #13405 Closes #12786
2024-08-24 00:35:42 +02:00
tabled = { workspace = true, features = ["ansi"], default-features = false }
make `FooterMode::Auto` work (#14063) # Description @Yethal discovered that `FooterMode::Auto` in the config as `$env.config.footer_mode = auto` did not work. This PR attempts to fix that problem by implementing the auto algorithm that was already supposed to work. # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use toolkit.nu; toolkit test stdlib"` 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. -->
2024-10-11 20:36:09 +02:00
terminal_size = { workspace = true }
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 dev version 0.100.1 (#14328)
2024-11-14 10:04:39 +01:00
# nu-test-support = { path="../nu-test-support", version = "0.100.1" }
Reference in New Issue Copy Permalink