[Feature Request]: Expand BuildCheck editorconfig allowable syntax

[baronfel]

Summary

EditorConfig settings for BuildChecks have rigid rules:

• casing matters for properties
• not all Roslyn severities are available, but the docs declare it to be so

Background and Motivation

Ease of use/things I banged my head against today

Proposed Feature

I'd like to see:

• the IsEnabled property should support enabled as well
• casing should be case-insensitive
• a severity of None (also, none) should be allowed to disable a rule (this is in line with the desire for case-insensitivity)

Alternative Designs

No response

[f-alizada]

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?

[baronfel]

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).