Results 1611 comments of Roman Ivanov

>WriteTagCheck.java I don't see this check in list at issue description. But if it uses it, ok, we need to convert it to AST based by extension of AbstractJavadocCheck class...

https://github.com/checkstyle/checkstyle/blob/a3223634c34b592713d3fa9982b53e5f02f1d2a5/src/main/java/com/puppycrawl/tools/checkstyle/checks/imports/UnusedImportsCheck.java#L317-L320 Attention to this part. Check just needs javadoc. https://checkstyle.org/writingchecks.html#Comment_Tokens_in_AST Look around in other checks how `isCommentNodesRequired()` help Checks to get content of javadoc.

@ivamly, yes, all not fixed are available, I do not see PR also . But be aware that it might need usage of javadoc AST, please look around how others...

@ivamly, how you are doing? If you are stuck, let me know, you can take some simple Check. JavadocMethod is very complicated, better to do it after gaining more experience....

There is not such thing as default config already for 25 years. All plugins do not expect default config. Majority of Checks are verified opinionated , it is close to...

You need to open such issue on all our plugins and persuade them to have some rule set that is good to use. checkstyle/checkstyle repository is library, not a final...

Please go to maven checkstyle plugin with all such proposals, to "match" spotless-maven-plugin on execution behavior. You can create your own repository with config that you think all should use....

you can add IndentationCheckTest.java to suppression for this Check, yes, it is growing . example of suppression https://github.com/checkstyle/checkstyle/blob/18ffa91079b46d788bae8c849f5d77dce109c6fd/config/suppressions.xml#L44

Ok, you reproduced issue in Input. Good, please continue to debug Check and changing logic of Check to avoid violation

@Harsh-Agrawal96 , please resolve conflict and make single commit in PR.