Java: Replace usage of toString() for Javadoc queries; add more Javadoc tags #5815
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
Marcono1234
force-pushed
the
marcono1234/javadoc
branch
from
6b86a91 to
dc1f563
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.
toString()for checking Javadoc textgetATag(string)fromJavadocParenttoJavadocsinceJavadocTag(which also extendsJavadocParent) cannot have nested Javadoc block tags (as far as I know)Note that due to #3696 the added predicate for
JavadocParenthas to begetATextElement()since multi-line comments are separateJavadocTextelements.Additionally in the future the added CodeQL classes for
@returnand@deprecatedmight need proper predicates for handling multi-line text, but that is blocked by #3825.