Skip to content
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

<autogenerated/> not accepted as indicator for auto generated files #833

Closed
vweijsters opened this issue May 14, 2015 · 2 comments · Fixed by #834
Closed

<autogenerated/> not accepted as indicator for auto generated files #833

vweijsters opened this issue May 14, 2015 · 2 comments · Fixed by #834
Assignees
Milestone

Comments

@vweijsters
Copy link
Contributor

A file starting with // <autogenerated/> is not accepted as an auto generated file by the '...HonorExclusions' extension methods.

Stylecop was accepting both <autogenerated/> and <auto-generated/>.

@sharwell
Copy link
Member

@AArnott @vweijsters Do we need this?

@AArnott
Copy link
Contributor

AArnott commented May 15, 2015

Yes, it's true. I'll send a pull request.

AArnott added a commit to AArnott/StyleCopAnalyzers that referenced this issue May 15, 2015
We already recognized <auto-generated />. The original StyleCop also recognized <autogenerated />. So this brings us up to parity with that.

Fixes DotNetAnalyzers#833
vweijsters pushed a commit to vweijsters/StyleCopAnalyzers that referenced this issue May 15, 2015
We already recognized <auto-generated />. The original StyleCop also recognized <autogenerated />. So this brings us up to parity with that.

Fixes DotNetAnalyzers#833
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants