nushell/crates/nu-glob/Cargo.toml

[package]
name = "nu-glob"
version = "0.95.1"
authors = ["The Nushell Project Developers", "The Rust Project Developers"]
license = "MIT/Apache-2.0"
description = """
Fork of glob. Support for matching file paths against Unix shell style patterns.
"""
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-glob"
edition = "2021"
categories = ["filesystem"]

[lib]
bench = false

[dev-dependencies]
doc-comment = "0.3"
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test 2022-03-13 19:30:27 +01:00			`[package]`
			`name = "nu-glob"`
Bumping version to 0.95.1 (#13231) Marks development for hotfix 2024-06-26 03:26:07 +02:00			`version = "0.95.1"`
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", "The Rust Project Developers"]`
			`license = "MIT/Apache-2.0"`
			`description = """`
			`Fork of glob. Support for matching file paths against Unix shell style patterns.`
			`"""`
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-glob"`
Nu glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test 2022-03-13 19:30:27 +01:00			`edition = "2021"`
			`categories = ["filesystem"]`

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 glob (#4818) * Fork glob. Normalise license holder * Fix more licenses * unwraps * bad doc test 2022-03-13 19:30:27 +01:00			`[dev-dependencies]`
Bump to 0.95.0 (#13221) <!-- 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-06-25 20:29:47 +02:00			`doc-comment = "0.3"`