[java] Update rule ConsecutiveLiteralAppends#3335
Merged
adangel merged 3 commits intoJun 25, 2021
Merged
Conversation
Fixes a false positive: intervening calls to toString() are no longer ignored, as the result of toString() would change if the consecutive append calls would be merged.
Generated by 🚫 Danger |
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.
Describe the PR
Note: This fixes a false positive: intervening calls to
toString()are no longer ignored, as the result of toString() wouldchange if the consecutive append calls would be merged. The same of
length().E.g.
This is no longer flagged since merging the two append calls into
sb.append("ab");will change the result of the program....Related issues
Ready?
./mvnw clean verifypasses (checked automatically by github actions)