Open baronfel opened 3 weeks ago
Thank you! I'm going to update the usage, however would like clarify: which values were case sensitive? Trying to reproduce:
[*.csproj]
build_check.BC0101.IsEnabled=TRUE
build_check.BC0101.SEVERITY=ERROR
And the configuration applied correctly, am I missing something?
For case sensitivity I agree that the values are fine, it was the case sensitivity of the property keys that was frustrating - convention elsewhere seems to be lowercase property keys (meaning don't let .NET's Pascal case obsession leak to the editor config file).
Possibly related: https://github.com/dotnet/msbuild/issues/10315
Btw. - the:
Are tracked as https://github.com/dotnet/msbuild/issues/10097
Let's handle in either of those tickets, let's just prevent any possible duplication of efforts
Comment from @baronfel
Do we need IsEnabled overall in editorconfig if we are going to have support of
severity=none
which is equal to theIsEnabled=false
With this I do agree, and since we are in development mode I would remove the key from the infrastructure recognized keys :)
Summary
EditorConfig settings for BuildChecks have rigid rules:
Background and Motivation
Ease of use/things I banged my head against today
Proposed Feature
I'd like to see:
IsEnabled
property should supportenabled
as wellNone
(also,none
) should be allowed to disable a rule (this is in line with the desire for case-insensitivity)Alternative Designs
No response