-
-
Notifications
You must be signed in to change notification settings - Fork 255
-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exclude C# auto-generated files #229
Comments
So this is already possible right now with the right command line options. Not quite the same as #206 because that was looking at the extension. So if you want this right now,
or if you have multiple
What I can do however is add
So its more natural. Note that if minified enabled by this is picking up things you want counted you can tweak the line length to something stupidly large.
For the moment I have added |
Thanks for the quick reply. Really appreciate it! I guess it's fine using Thank you very much 👍 |
Yep added to the list in master already. Building from there will give you this. Will be rolled out in the 3.0.0 release which should be sooner rather than later now that Go 1.16 is out. |
Closing as its done on master, but still waiting on the 3.0.0 release. |
Describe the bug
In C#/.NET Projects auto-generated files are marked on top of a file with a comment:
// <auto-generated />
This is especially the case if you use the OR-Mapper Entity Framework where a lot of this auto-generated files are created in larger projects (due to database-Migration files) resulting in a unrealistic LOC result (e.g. in one project >50% of the "total" LOC are actually auto-generated).
Files cannot be simply git-ignored because these files are necessary.
To Reproduce
scc
on a folder containing a C# sharp file with the<auto-generated />
commentExpected behavior
C# Files with the
<auto-generated />
header shouldn't be counted. Similar to the lock-files issue #206 but with C# files.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: