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
4482862a40
nushell/crates/nu-test-support/Cargo.toml

25 lines
595 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"
Update to `0.76.1` version for development (#8161) # Description For tracking in `version` for bug reports during development. Might be used for an urgent hotfix if necessary.
2023-02-22 00:21:39 +01:00
version = "0.76.1"
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]
Update to `0.76.1` version for development (#8161) # Description For tracking in `version` for bug reports during development. Might be used for an urgent hotfix if necessary.
2023-02-22 00:21:39 +01:00
nu-path = { path="../nu-path", version = "0.76.1" }
nu-glob = { path = "../nu-glob", version = "0.76.1" }
nu-utils = { path="../nu-utils", version = "0.76.1" }
replace lazy_static with once_cell (#7502) replacing the dependence on `lazy_static` with `once_cell`, this will ensure that variables are initialized when needed instead of startup time.
2022-12-17 19:30:04 +01:00
once_cell = "1.16.0"
upgrade num-format (#6694)
2022-10-10 13:25:57 +02:00
num-format = "0.4.3"
Move some `from xxx` commands to plugin (#7942) # Description From nushell 0.8 philosophy: https://github.com/nushell/nushell.github.io/blob/main/contributor-book/philosophy_0_80.md#core-categories > The following categories should be moved to plugins: Uncommon format support So this pr is trying to move following commands to plugin: - [X] from eml - [x] from ics - [x] from ini - [x] from vcf And we can have a new plugin handles for these formatting, currently it's implemented here: https://github.com/WindSoilder/nu_plugin_format The command usage should be the same to original command. If it's ok, the plugin can support more formats like [parquet](https://github.com/fdncred/nu_plugin_from_parquet), or [EDN format](https://github.com/nushell/nushell/issues/6415), or something else. Just create a draft pr to show what's the blueprint looks like, and is it a good direction to move forward? # 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` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # 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-02-13 13:42:08 +01:00
which = "4.3.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
Bump some of our dependencies (#1809)
2020-05-17 00:34:10 +02:00
getset = "0.1.1"
Update some deps (#3011)
2021-02-05 21:54:54 +01:00
tempfile = "3.2.0"
Bump to 0.29 (#3230) * Bump to 0.29 * fix test
2021-03-30 11:35:21 +02:00
hamcrest2 = "0.3.0"
Reference in New Issue Copy Permalink