Fix JavaTemplate expression replacement inside return statements#7096
Merged
Fix JavaTemplate expression replacement inside return statements#7096
Conversation
When a method invocation or new class expression is the direct expression of a J.Return (or other non-block expression context), coordinates.replace() produces STATEMENT_PREFIX but parseBlockStatements fails because the template is an expression. Detect expression context by checking if the parent tree is not a J.Block, and use parseExpression instead.
Member
Author
|
We already use the same pattern for field access, so I'd think this is fairly safe and fixes similar issues elsewhere: |
Member
Author
|
Since we already use the same pattern elsewhere I'm inclined to merge this with asynchronous review if needed.. It's specific enough and tested that I don't foresee any issues. |
Contributor
|
Nice! Surprised this never surfaced before... |
2 tasks
Member
Author
|
It needed a small tweak to fix an incorrect cursor in rewrite-testing-frameworks AssertThrowsOnLastStatement |
This file contains hidden or 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
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.
Summary
JavaTemplate.apply()withmi.getCoordinates().replace()throwingIllegalArgumentExceptionwhen the target method invocation is inside aJ.Return(or other non-block expression context)J.Block, useparseExpressioninstead ofparseBlockStatements— following the existing precedent invisitFieldAccessvisitNewClasswhich has the identical issueTest plan
replaceMethodInvocationInsideReturntest inJavaTemplateTest8TestJavaTemplate*tests pass