Fix cargo b -p nu-command --tests (#11939)

The feature `sqlite` is not active by default on `nu-command`.
Only when building `cargo b --all --tests` would the feature be
activated via `nu`'s feature requirements.

Make the tests conditional

Saw this when double checking the removals from #11938.
Making sure each crate still compiles individually, ensures both that
you can run subcrate tests independently and that the `cargo publish`
run will succeed to build the crate with the default feature set (see
the problems occurring for the `0.90.0` release.
This commit is contained in:
Stefan Holderbach 2024-02-25 00:01:29 +01:00 committed by GitHub
parent 4372d00ea9
commit 96744e3155
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -13,6 +13,7 @@ mod config_nu_default;
mod continue_;
mod conversions;
mod cp;
#[cfg(feature = "sqlite")]
mod database;
mod date;
mod debug_info;