-
Notifications
You must be signed in to change notification settings - Fork 54
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
not understandable sevntu check #570
Comments
I would report an issue to sevntu if you think it is a bug in the check. |
I'm not sure. I don't know what it is expecting, even after reading documentation. I have a field mSomething, and a getter getSomething(). Not sure if it's confused by the "m" notation (which I don't like myself, but I try to stay consistent with existing code). If you know the check better, you may want to run one of my PRs and remove the disablement locally to see what happens. |
I think this is the issue. My understanding of the check, from just refreshing my memory, is (for example) a pure getter method (method that just returns a field) should be named exactly after the field it returns. It should be expecting |
In that case I would leave the disablement in my PRs and later check if we can do a mass refactoring of the field names to get rid of the m prefixes and to re-enable the check then. |
@Bananeweizen I apologize,
If you do remove prefix property, it does behave as I described before.
|
In 2 of my PRs I had to disable SimpleAccessorNameNotation. It's raising issues on perfectly valid names which I have checked multiple times. Also the error message and documentation don't really tell anything about how to fix it.
I suggest to completely disable it (which will happen anyway if one of those 2 PRs is merged).
The text was updated successfully, but these errors were encountered: