-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Checkstyle #345
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
Checkstyle #345
Conversation
Codecov Report
@@ Coverage Diff @@
## trunk #345 +/- ##
============================================
- Coverage 58.35% 58.34% -0.01%
- Complexity 10204 10215 +11
============================================
Files 1159 1159
Lines 74384 74344 -40
Branches 7361 7339 -22
============================================
- Hits 43405 43375 -30
+ Misses 28483 28474 -9
+ Partials 2496 2495 -1
Continue to review full report at Codecov.
|
|
@ham1 , ReturnCount check is commented out. Please point me to place where you configure it. |
|
@romani it's commented out to stop this PR failing but where you see it commented out was where I had: |
|
Looks like a reason was in |
|
Yes, that's correct, I some how missed it in the docs. I've suggested on checkstyle/checkstyle#5305 that the error message is changed to something like: Thanks for your time in looking into an RTFM issue. |
|
@ham1 , if you enforce(ERROR level) more than half of Checks on this project, we can use jmeter project in each commit (in checkstyle) regression testing. |
|
@romani, sorry I'm not clear on what, if anything, you'd want me to do/change? |
Added more rules, e.g. max file length, max 2 blank lines, no empty catch blocks.
…fDepth and NestedTryDepth
OneStatementPerLine SimplifyBooleanExpression SimplifyBooleanReturn StringLiteralEquality SuperFinalize UnnecessaryParentheses
|
if master branch of this project (jmeter) start to use about 80 Checks in its config with ERROR severity and no violations reported, we can start to use jmeter in out CI for regression testing. just keep enforcing more and more rules, and pin me then you are done. |
|
Hi team, anybody wants to merge this one ? if not I’ll do it this week-end. Thanks |
Description
Motivation and Context
Automatically enforcing some of the coding standards/conventions helps improve readability and prevents commits like "Tab police" or commits which only change formatting thus cluttering the history (or leaving it in an inconsistent state to micro-annoy subsequent readers).
How Has This Been Tested?
ant clean checkstyle -Djava.awt.headless=true -Dskip.bug52310=true -Dskip.test_https=true testScreenshots (if appropriate):
Types of changes
Checklist: