-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
How to indicate that a feature is only valid in combination with specific others #264
Comments
Perhaps it would work if split into the following two commands.
|
You'll get
|
You have to run two commands, not in the single command.
|
I'm wondering if I'm seeing a bug here... The docs for
But when I run this command, I get these executions:
Two of which (3 and 6) have neither of the Basically the only one the two separate commands actually removes from the original powerset is the one with |
There is no information about Footnotes
|
Ah, you're right. I failed to keep in mind that although If there's nothing actionable to do for you regarding "dependent features" as far as implementing anything goes, feel free to close this issue. The only thing I could think of would be to have a way to specify something like
all in a single invocation, but given how easy it is to just run the two invocations manually, I'm not sure it's even worth considering. |
Suppose we have three features:
feature_a
,feature_b
, andfeature_only_if_a_or_b
. The third feature,feature_only_if_a_or_b
, is meaningful only when at least one offeature_a
orfeature_b
is enabled. Otherwise, it does nothing and shouldn't be tested.In terms of combinations, I want to test the following setups:
feature_a
feature_b
feature_a
+feature_only_if_a_or_b
feature_b
+feature_only_if_a_or_b
feature_a
+feature_b
+feature_only_if_a_or_b
I understand
--group-features
can enforce specific groupings, like:However, this approach excludes
feature_a
andfeature_b
from running withoutfeature_only_if_a_or_b
. It doesn't allow single features to run independently.Likewise, no combination of
--exclude-features
or--include-features
achieves the desired behavior. For example,--exclude-features feature_only_if_a_or_b
prevents it from running solo but also removes it from any valid combination.When a feature is a strict sub-feature of another, there's an easy fix, you just make the sub-feature enable the parent feature. This is, however, not possible when a feature is orthogonally integrated with others, like in this case.
The text was updated successfully, but these errors were encountered: