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

Some rules don't print their identifiers when reporting #180

Closed
ZevEisenberg opened this issue Nov 4, 2015 · 1 comment
Closed

Some rules don't print their identifiers when reporting #180

ZevEisenberg opened this issue Nov 4, 2015 · 1 comment

Comments

@ZevEisenberg
Copy link
Contributor

I have code like this:

if theta > π {
    value = twoPi - theta
}
else {
    value = theta
}

I'm getting this warning:

Statement Position Violation: Else and catch must be on the same line and one space after previous declaration ()

There is no rule indicated in the parentheses, which seems to indicate that there's no way to turn this off. Is that correct?

@jpsim
Copy link
Collaborator

jpsim commented Nov 4, 2015

It can be turned off. That rule's identifier is statement_position. I'll look into why the identifier isn't being printed.

@jpsim jpsim changed the title No configuration for else/catch same line rule? Some rules don't print their identifiers when reporting Nov 4, 2015
@jpsim jpsim closed this as completed in #181 Nov 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants