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.
Before this PR
There was a hack in
Level#computeBreaks
to make StringWrapper and our "no newline after assignments heuristic" (802a186) work together.palantir-java-format/palantir-java-format/src/main/java/com/palantir/javaformat/doc/Level.java
Lines 210 to 220 in 16bb99f
However, this relies on leaving a string on the assignment line, and the StringWrapper actually being able to split it, which might not be the case (if it has no whitespace, for instance). Here's an example where it failed in this way (file view)
After this PR
==COMMIT_MSG==
Reflow long strings more thoroughly, taking into account that once a string is broken, its first chunk might fit on the starting line and thus it needs to be reflowed again.
==COMMIT_MSG==
Possible downsides?