-> all classes in test.py will be activated at v2.3.4, except test_classC who will be flagged as missing for nextjs, and activated for all others (activation by default)
-> all classes in test.py will be flagged as bug for poc, and activated at v2.3.4 for other variants, except test_classC who will activated at v4.0 for all variants
Sometimes, an entire file is activated at the same version :
And if it's a map of variant, it become a little bit verbose.
The idea is to support a
_default
value :-> all classes in test.py will be activated at
v2.3.4
The
_default
value is used if, and only if nothing is specified for a class. If something is specified, the_default
value is ignored.The keywork
_default
is used, meaning we wont be able to name a file_default
.Examples
-> all classes in test.py will be activated at
v2.3.4
, excepttest_classC
who will be activated atv4.0
-> all classes in test.py will be activated at
v2.3.4
, excepttest_classC
who will be flagged as missing fornextjs
, and activated for all others (activation by default)-> all classes in test.py will be flagged as bug for
poc
, and activated atv2.3.4
for other variants, excepttest_classC
who will activated atv4.0
for all variants