Handle parenthesized trees #733
Merged
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
| @@ -160,6 +161,9 @@ private Semanticdb.Tree annotationParameter(ExpressionTree expr) { | |||
| unaryOpTree( | |||
| semanticdbUnaryOperator(unaryExpr.getKind()), | |||
| annotationParameter(unaryExpr.getExpression()))); | |||
| } else if (expr instanceof ParenthesizedTree) { | |||
| ParenthesizedTree parenExpr = (ParenthesizedTree) expr; | |||
| return annotationParameter(parenExpr.getExpression()); | |||
There was a problem hiding this comment.
@olafurpg can you confirm it's fine to drill into subtree without creating intermediate semanticdb nodes?
There was a problem hiding this comment.
This is fine. No need to encode parentheses here, we can add it later if necessary
|
|
||
| @Nullable(("what")) |
There was a problem hiding this comment.
this is the new parenthesized node
olafurpg
approved these changes
Aug 6, 2024
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.
Yet another possible tree wasn't handled, so we add support for it.
This time we don't add anything to semanticdb as it's meaningless.
Test plan