You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue relates to the exclusion of particular files from analysis according to their filenames (see #836). It specifically covers the following patterns:
*.g.cs
*.g.i.cs
The filename-based exclusion is not necessary because the code generators which produce these files include <auto-generated> in a comment at the top of the file.
The text was updated successfully, but these errors were encountered:
It makes sense that we can remove these.
The only possible reason I can think of to remove them is that a filename check is faster than searching the document header for a substring inside it. But I think our design hinges on that header check being fast anyway, so it's probably a non-issue. I support your goal of reducing the list of filename patterns.
This change removes the automatic exclusion for all filenames where no
specific example of this requirement could be found. The code generators
for the files that are not eligible for analysis use <auto-generated>
(or <autogenerated>) in the generated code, which causes the exclusion
to occur by content instead.
FixesDotNetAnalyzers#848FixesDotNetAnalyzers#849FixesDotNetAnalyzers#850FixesDotNetAnalyzers#851FixesDotNetAnalyzers#854
For now, this exclusion has been removed. If it's reported as necessary in the future, we can easily add it back and we'll also have the advantage of having a record of the reasons each exclusion exists.
This issue relates to the exclusion of particular files from analysis according to their filenames (see #836). It specifically covers the following patterns:
The filename-based exclusion is not necessary because the code generators which produce these files include
<auto-generated>
in a comment at the top of the file.The text was updated successfully, but these errors were encountered: