jasterv/test-context
1
0
Fork 0
mirror of https://codeberg.org/JasterV/test-context.git synced 2026-04-26 18:10:06 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Forced futures to be imported through test_context crate.

Browse source 
By exporting the futures crate through the test_context crate, the code
generated by the macro can rely on `test_context` to access the future
crate. Otherwise, the code generated which requires access to the
"future" crate would end up residing in the code of a user of the
library, giving them `use of undeclared crate or module "future"`
error messages unless they added future as a dependency.
This commit is contained in:
Mark Hildreth 2021-02-06 23:38:44 -05:00
parent 0d78b70786
commit be1e4a9178
3 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Cargo.toml
View file

@ -13,10 +13,10 @@ categories = ["development-tools::testing"]
[dependencies]
test-context-macros = { version = "0.1.1", path = "macros" }
async-trait = "0.1.42"
futures = "0.3"
[dev-dependencies]
tokio = { version = "1.0", features = ["macros", "rt"]}
futures = "0.3.12"
[workspace]
members = [

2
macros/src/lib.rs
View file

@ -39,7 +39,7 @@ pub fn test_context(attr: TokenStream, item: TokenStream) -> TokenStream {
let outer_body = if is_async {
quote! {
{
use futures::FutureExt;
use test_context::futures::FutureExt;
let mut ctx = <#context_type as test_context::AsyncTestContext>::setup().await;
let wrapped_ctx = &mut ctx;
let result = async move {

3
src/lib.rs
View file

@ -53,6 +53,9 @@
//! }
//! ```
// Reimported to allow for use in the macro.
pub use futures;
pub use test_context_macros::test_context;
/// The trait to implement to get setup/teardown functionality for tests.