-
Notifications
You must be signed in to change notification settings - Fork 111
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
Allow 'id' as a variable name #593
Comments
@yegor256 please take a look at this, are you good with the change? |
@krzyk make sense, I second this |
@davvd valid bug |
@mkordas thanks for the ticket, your account was topped for 15 mins, payment 56936d48d7717a6a38000067 |
@jrdalpra can you work on this? |
@krzyk there's any test case to prove the issue? |
@mkordas which tool is complaining about the attribute's name? Checkstyle? PMD? |
@jrdalpra you have to create a testcase to prove that it is no longer occurring after the changes |
@jrdalpra it's Checkstyle complaining |
@krzyk @mkordas the problem resides there https://github.com/teamed/qulice/blob/master/qulice-checkstyle/src/main/resources/com/qulice/checkstyle/checks.xml#L312-L315 Can I just pull the changes without a test case and create a puzzle for that test case? Thanks. |
@jrdalpra without a test case we won't know if it reallyw works |
@mkordas can you close this issue? Thanks. |
@jrdalpra you need to refer to pull request in at least one message |
@jrdalpra thanks! |
Currently Qulice prohibits variable named just 'id', e.g.
I don't see anything bad in using
id
as variable name, it is very common and widely accepted.To overcome it, people use a lot of creativity. I've seen variables named like:
ide
ident
identifier
attrid
attribute
name
xid
and so on, instead of simple
id
.I'd expect
id
to be allowed as final/non-final local variable names, method parameters, fields and constants (ID
). It should be prohibited for catch parameters.The text was updated successfully, but these errors were encountered: