I think missconfiguration should be rather fatal, as it can be hard to validate (especially on small projects with few dependencies) that the test that is running is actually correct. It may give false positives. It would be nice if, when passing a blueOak value of foo, it would throw an error saying that is not an existing category.
kemitchell
commented
5 years ago
I think missconfiguration should be rather fatal, as it can be hard to validate (especially on small projects with few dependencies) that the test that is running is actually correct. It may give false positives. It would be nice if, when passing a
blueOakvalue offoo, it would throw an error saying that is not an existing category.