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

SA1513 Fired when old StyleCop did not complain #2041

Closed
froufrou121 opened this issue Jan 11, 2016 · 2 comments
Closed

SA1513 Fired when old StyleCop did not complain #2041

froufrou121 opened this issue Jan 11, 2016 · 2 comments
Assignees
Milestone

Comments

@froufrou121
Copy link

I like that in the old StyleCop (4.7) you could put //// comments anywhere in the code and no warning would be raised. With StyleCop.Analyzers rc3 I get a SA1513 with the following code

            public int Do(int i)
            {
                if (i > 2)
                {
                    return 1;
                }
                //// else if (i == 2)
                //// {
                ////     return 2;
                //// }

                return 0;
            }

whereas I did not get any warning from StyleCop 4.7. I preferred the old way.

@sharwell
Copy link
Member

I think it makes sense to update our code to work the same way as StyleCop Classic.

@sharwell sharwell added this to the 1.1.0 milestone Jan 11, 2016
@vweijsters
Copy link
Contributor

Grabbing this

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

No branches or pull requests

3 participants