Edit: The description below referred to themember-naming rule, which has since been replaced by the newnaming-convention rule. This issue is still relevant.

Repro

{"rules": {"@typescript-eslint/member-naming": ["error", {"private":"^(?!_)" }]  }}

classExample{private_var1;// Not a backing field, shouldn't start with an underscore.private_var2;// Allowed, as it's a backing field for the `var2` property.publicgetvar2(){returnthis._var2;}}

Expected Result

Error for_var1, but not for_var2 (because it's a backing field).

Actual Result

Error for both fields.

Additional Info

SimilarTSLint issue with 33 👍.

Since this rule is different to the one in TSLint, the implementation would be different. Maybe anignoreBackingFields: boolean option, or a way to set the naming for backing fields separately.

Versions