Closed gergelykovacs closed 8 years ago
I've followed the JSCS model of naming rules, and that too allows you to essentially create a config that contradicts itself, but will look at implementing functionality to associate pairs with one another and ignore further config values if one of a pair is already set
e.g.
{ "disallowClassLiteralsBeforeAttributes": true
, "requireClassLiteralsBeforeAttributes": true
}
would result in requireClassLiteralsBeforeAttributes
being null
Ambiguity!
Contradiction in config options e.g.,
Could you clarify and clean up configuration options to avoid such scenarios?