Fix JavaParser 3.28.0 API compatibility: Use TraditionalJavadocComment #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JavaParser 3.28.0 changed
JavadocCommentfrom a concrete class to an abstract class, introducingTraditionalJavadocCommentas the concrete implementation.Changes
visit(JavadocComment n, Analyzer arg)tovisit(TraditionalJavadocComment n, Analyzer arg)and added@Overrideannotation to properly override the visitor method fromGenericListVisitorAdapternew JavadocComment(...)tonew TraditionalJavadocComment(...)JavadocComment(abstract parent) for compatibility with all subclassesThe visitor pattern in 3.28.0 exposes
visit(TraditionalJavadocComment, A)instead ofvisit(JavadocComment, A), requiring the method signature change to properly override the parent class method.💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.