nushell/crates/nu-test-support/Cargo.toml

25 lines
595 B
TOML
Raw Normal View History

[package]
authors = ["The Nushell Project Developers"]
description = "Support for writing Nushell tests"
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-test-support"
edition = "2021"
license = "MIT"
2020-07-05 22:12:44 +02:00
name = "nu-test-support"
version = "0.77.1"
[lib]
doctest = false
bench = false
[dependencies]
nu-path = { path="../nu-path", version = "0.77.1" }
nu-glob = { path = "../nu-glob", version = "0.77.1" }
nu-utils = { path="../nu-utils", version = "0.77.1" }
once_cell = "1.16.0"
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"
2020-05-17 00:34:10 +02:00
getset = "0.1.1"
2021-02-05 21:54:54 +01:00
tempfile = "3.2.0"
hamcrest2 = "0.3.0"