Currently, we do not handle auto-generated C# files. Someone reached out to us about violations appearing on autogenerated C# files when they shouldn't be.
What is your solution?
We should ignore autogenerated C# files like we do for several other languages. The heuristics used come from the C# Roslyn analyzer and compiler itself, and a summary of what these heuristics are can be found on this slack thread from 2020, which points to this file in Roslyn for handling autogenerated file detection.
The heuristics are:
if the file contains <autogenerated or <auto-generated
if the filename starts with TemporaryGeneratedFile_ (case insensitive)
if the filename without the extension ends with .designer, .generated, .g, or .g.i (case insensitive, e.g. foo.designer.cs)
Alternatives considered
What the reviewer should know
The failing CI for the regression checks w.r.t. C# repos is expected, there are some files we no longer process now as a result of the changes in this PR.
What problem are you trying to solve?
Currently, we do not handle auto-generated C# files. Someone reached out to us about violations appearing on autogenerated C# files when they shouldn't be.
What is your solution?
We should ignore autogenerated C# files like we do for several other languages. The heuristics used come from the C# Roslyn analyzer and compiler itself, and a summary of what these heuristics are can be found on this slack thread from 2020, which points to this file in Roslyn for handling autogenerated file detection.
The heuristics are:
<autogeneratedor<auto-generatedTemporaryGeneratedFile_(case insensitive).designer,.generated,.g, or.g.i(case insensitive, e.g.foo.designer.cs)Alternatives considered
What the reviewer should know
The failing CI for the regression checks w.r.t. C# repos is expected, there are some files we no longer process now as a result of the changes in this PR.