extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-11-27 02:44:01 +01:00
Code Issues Packages Projects Releases Wiki Activity
51aa66fef7
nushell/crates/nu-test-support/Cargo.toml

22 lines
578 B
TOML
Raw Normal View History

This commit is the continuing phase of extracting functionality to subcrates. We extract test helpers and begin to change Nu shell's test organization along with it.
2019-12-15 17:15:06 +01: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"]
Fix typo in test support crate description (#2669)
2020-10-14 11:45:32 +02:00
description = "Support for writing Nushell tests"
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-test-support"
Upgrade all remaining crates to Rust 2021 (#7681) 2 crates were still using Rust 2018, including the base `nu` crate. This PR upgrades them to Rust 2021. If you're aware of any reason why this is a bad idea, please speak now or forever hold your peace. ## Context I was moving benchmarks from `nu-plugin` to the base crate and couldn't figure out why they wouldn't compile. Turns out the benchmarks rely on some Rust 2021 features. Would be nice to have everything on 2021.
2023-01-05 13:24:42 +01:00
edition = "2021"
This commit is the continuing phase of extracting functionality to subcrates. We extract test helpers and begin to change Nu shell's test organization along with it.
2019-12-15 17:15:06 +01:00
license = "MIT"
Bump to 0.16.1 (#2116)
2020-07-05 22:12:44 +02:00
name = "nu-test-support"
Bump version for `0.92.0` release (#12349) - [x] `cargo hack` feature flag compatibility run - [x] reedline released and pinned - [x] `nu-plugin-test-support` added to release script - [x] dependency tree checked - [x] release notes
2024-04-02 19:50:26 +02:00
version = "0.92.0"
This commit is the continuing phase of extracting functionality to subcrates. We extract test helpers and begin to change Nu shell's test organization along with it.
2019-12-15 17:15:06 +01:00
Inc refactoring, Value helper test method extractions, and more integration helpers. (#1135) * Manifests check. Ignore doctests for now. * We continue with refactorings towards the separation of concerns between crates. `nu_plugin_inc` and `nu_plugin_str` common test helpers usage has been refactored into `nu-plugin` value test helpers. Inc also uses the new API for integration tests.
2019-12-29 06:17:24 +01:00
[lib]
doctest = false
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
bench = false
This commit is the continuing phase of extracting functionality to subcrates. We extract test helpers and begin to change Nu shell's test organization along with it.
2019-12-15 17:15:06 +01:00
[dependencies]
Bump version for `0.92.0` release (#12349) - [x] `cargo hack` feature flag compatibility run - [x] reedline released and pinned - [x] `nu-plugin-test-support` added to release script - [x] dependency tree checked - [x] release notes
2024-04-02 19:50:26 +02:00
nu-path = { path = "../nu-path", version = "0.92.0" }
nu-glob = { path = "../nu-glob", version = "0.92.0" }
nu-utils = { path = "../nu-utils", version = "0.92.0" }
Externals now spawn independently. (#1230) This commit changes the way we shell out externals when using the `"$it"` argument. Also pipes per row to an external's stdin if no `"$it"` argument is present for external commands. Further separation of logic (preparing the external's command arguments, getting the data for piping, emitting values, spawning processes) will give us a better idea for lower level details regarding external commands until we can find the right abstractions for making them more generic and unify within the pipeline calling logic of Nu internal's and external's.
2020-01-16 10:05:53 +01:00
Move more dependencies to workspace level (#12270) # Description This is a followup to #12043 that moves more dependency versions to workspace dependencies. # User-Facing Changes N/A # Tests + Formatting - :green_circle: `toolkit fmt` - :green_circle: `toolkit clippy` - :green_circle: `toolkit test` - :green_circle: `toolkit test stdlib`
2024-03-24 00:46:02 +01:00
num-format = { workspace = true }
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
which = { workspace = true }
tempfile = { workspace = true }
Reference in New Issue Copy Permalink