-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to enable features in the configuration #1402
Comments
Hi @usagi-flow -- Thanks for the report. At the moment, this isn't supported -- nextest tries to customize the build process as little as possible. Though you make a compelling case, and I can definitely see how this may help. I think we can borrow the weak feature syntax from Cargo. So: [profile.default]
build.extra = [
"p1/f1",
"p2?/f2",
"p3",
"bin:b1",
] What this says is:
This can also be used in an additive fashion with overrides -- letting you say that: if e.g. |
Related (and possibly part of this enhancement) it would be great if there was a way to configure features for each crate within a workspace allowing something like run all tests with |
Despite looking through the documentation and issues, I couldn't find much besides #50 (which requests a bigger feature).
Is there a way - and if not, would it be possible - to define Cargo features which should be activated when building?
Basically, I'd like to specify features in the configuration which I would otherwise specify on the command line (
cargo nextext run --features somefeature
).The way I'd imagine writing this in the configuration would be as follows:
PS: Thank you for this absolutely amazing tool, it's so much nicer than
cargo test
!The text was updated successfully, but these errors were encountered: