nushell/crates/nu-term-grid/Cargo.toml

[package]
authors = ["The Nushell Project Developers"]
description = "Nushell grid printing"
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-term-grid"
edition = "2021"
license = "MIT"
name = "nu-term-grid"
version = "0.100.1"

[lib]
bench = false

[lints]
workspace = true

[dependencies]
nu-utils = { path = "../nu-utils", version = "0.100.1" }

unicode-width = { workspace = true }
moved `grid` to it's own crate named `nu-term-grid` 2021-10-07 17:32:39 +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"]`
moved `grid` to it's own crate named `nu-term-grid` 2021-10-07 17:32:39 +02:00			`description = "Nushell grid 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-term-grid"`
update all cargo crates to edition 2021 (#781) 2022-01-20 14:13:45 +01:00			`edition = "2021"`
moved `grid` to it's own crate named `nu-term-grid` 2021-10-07 17:32:39 +02:00			`license = "MIT"`
			`name = "nu-term-grid"`
Bump to dev version 0.100.1 (#14328) 2024-11-14 10:04:39 +01:00			`version = "0.100.1"`
moved `grid` to it's own crate named `nu-term-grid` 2021-10-07 17:32:39 +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`

moved `grid` to it's own crate named `nu-term-grid` 2021-10-07 17:32:39 +02:00			`[dependencies]`
Bump to dev version 0.100.1 (#14328) 2024-11-14 10:04:39 +01:00			`nu-utils = { path = "../nu-utils", version = "0.100.1" }`
update most dependencies except where deeper code changes are needed (#9296) # Description This PR updates most dependencies and tries to get in sync with reedline. # 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 -- crates/nu-std/tests/run.nu` to run the tests for the standard library > Note > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> 2023-05-26 17:32:48 +02:00
Bump to version 0.99.0 (#14094) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [linking keywords](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. Provide examples and/or screenshots if your changes affect the user experience. --> # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` 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-15 21:01:08 +02:00			`unicode-width = { workspace = true }`