91ca0e03d8
## Motivation There has been interest around publishing tracing-mock to crates.io for some time. In order to make this possible, it needs to be cleaned up. ## Solution There are some test utils in the `tracing-mock` crate which wouldn't make sense to publish. They provide test futures that are needed in multiple `tracing-*` crates, but would likely not be needed outside that context. This change moves that functionality into a separate `tracing-test` crate, which should never be published to crates.io. Refs: #539 Co-authored-by: David Barsky <me@davidbarsky.com>
26 lines
669 B
TOML
26 lines
669 B
TOML
## BIG SCARY NOTE
|
|
# This crate is internal and to be used for testing only. It should not
|
|
# be published to crates.io ever. If the functionality is needed outside
|
|
# the tracing project, it should be moved back to tracing-mock.
|
|
|
|
[package]
|
|
name = "tracing-test"
|
|
version = "0.1.0"
|
|
authors = [
|
|
"Eliza Weisman <eliza@buoyant.io>",
|
|
"Tokio Contributors <team@tokio.rs>",
|
|
]
|
|
license = "MIT"
|
|
readme = "README.md"
|
|
repository = "https://github.com/tokio-rs/tracing"
|
|
homepage = "https://tokio.rs"
|
|
edition = "2018"
|
|
rust-version = "1.49.0"
|
|
publish = false
|
|
|
|
[dependencies]
|
|
tokio-test = "0.4.2"
|
|
|
|
[package.metadata.docs.rs]
|
|
all-features = true
|
|
rustdoc-args = ["--cfg", "docsrs"]
|