Issue #4717: Added JavadocParserErrorStrategy which extends BailErrorStrategy#4825
Issue #4717: Added JavadocParserErrorStrategy which extends BailErrorStrategy#4825Vladlis merged 1 commit intocheckstyle:masterfrom
Conversation
|
@Vladlis Thank you for the solution. Please have a look. |
Codecov Report
@@ Coverage Diff @@
## master #4825 +/- ##
======================================
Coverage 100% 100%
======================================
Files 288 288
Lines 15435 15435
Branches 3501 3500 -1
======================================
Hits 15435 15435
Continue to review full report at Codecov.
|
|
@PS-SP TC failed. |
|
@rnveach Yes, I checked. One reason is throwing unchecked exception in code which can be taken care of but another is with the unused catch parameter here at JavadocDetailNodeParser.java#L129. Right now we don't need to do anything with that exception object. |
|
@PS-SP |
Resolved. |
| import static com.puppycrawl.tools.checkstyle.checks.javadoc.AbstractJavadocCheck.MSG_JAVADOC_MISSED_HTML_CLOSE; | ||
| import static com.puppycrawl.tools.checkstyle.checks.javadoc.AbstractJavadocCheck.MSG_JAVADOC_PARSE_RULE_ERROR; | ||
| import static com.puppycrawl.tools.checkstyle.checks.javadoc.AbstractJavadocCheck.MSG_JAVADOC_WRONG_SINGLETON_TAG; | ||
| import static com.puppycrawl.tools.checkstyle.checks.javadoc.AbstractJavadocCheck.MSG_KEY_UNRECOGNIZED_ANTLR_ERROR; |
There was a problem hiding this comment.
Is this message no longer possible to receive? If so, shouldn't we remove the field and properties message?
There was a problem hiding this comment.
Yes it shouldn't be possible any longer. This one at messages.properties#L1 also seems unutilized.
The reason I didn't remove unrecognized one is that right now it looks like that report should be called under all circumstances. But it might so happen that under some weird input or for some other reason ANTLR fails to report to listener and then we might again require it. So I thought that after some time of usage when we can be sure that never does ANTLR fail to report to listener, we can remove all the unutilized message keys together in one issue so that all other message.properties get cleaned.
There was a problem hiding this comment.
I still think it should be removed. We will still have it's code in history if we need it again.
@romani You agree?
There was a problem hiding this comment.
@Vladlis It is a public property, so it probably can't tell the difference between something we give to the users and something we just use for ourselves. Had it been private, it probably would have thrown up a flag.
There was a problem hiding this comment.
|
http://4717-diff.getforge.io/apache-ant/index.html#A26
Why does this fail recognition? Edit: It seems the line separation between |
|
@rnveach |
|
@PS-SP If you agree it should be acceptable, make a issue for it. Otherwise explain why it isn't valid javadoc. |
|
@PS-SP Since you already started that issue, unless your fix already includes the fix for the issue I pointed at, I think it should be a new issue. Placing too much into 1 issue over complicates the issue and will be harder to manage. |
|
@rnveach Can be done there itself. Please check my summary comment there I just made. |
|
@PS-SP And your long winded post proves to me that too much is going on there. |
|
@rnveach Rebased. That PR wasn't intended to drag on for so long and to be so big. But things kept coming one after the other and here we are. Just one little problem needs to be addressed now and hopefully I will be able to update PR finally. |
|
@romani Please review. |
|
@PS-SP , please rebase. I like more detailed messaged. As CI pass, we good to merge this PR. |
… BailErrorStrategy
|
@romani rebased |
#4717