Add annotation type to extractor #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…parsing annotation declarations
tainacaetano
force-pushed
the
add-annotation-type
branch
from
d631441 to
90613dc
Compare
dnfeitosa
force-pushed
the
master
branch
2 times, most recently
from
938b198 to
47f11b1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new Type in TypesExtractor, fixing an error[1] that would happen when parsing an annotation declaration (refer to
SomeAnnotationfor an example of a problematic class).[1]
> com.github.javaparser.ast.body.AnnotationDeclaration cannot be cast to com.github.javaparser.ast.body.ClassOrInterfaceDeclaration