Releases: palantir/palantir-java-format
Releases · palantir/palantir-java-format
0.3.11
Type |
Description |
Link |
Fix |
Nested method chains now also adhere to column limit. |
#123 |
0.3.10
Type |
Description |
Link |
Improvement |
When importing a gradle project with com.palantir.java-format-idea from IntelliJ, eagerly configure the necessary XML files in .idea rather than relying on unwieldy IntelliJ task triggers. |
#120 |
0.3.9
Type |
Description |
Link |
Improvement |
A new plugin com.palantir.java-format-spotless configures gradle-spotless (if applied) to format java files using palantir-java-format. The main com.palantir.java-format plugin now applies both the spotless and idea plugins too. |
#107 |
0.3.8
Type |
Description |
Link |
Fix |
No longer break string concats unless they are a method's only argument on the line so far. |
#104 |
0.3.7
Type |
Description |
Link |
Fix |
Partially inlined levels are now also limited such that the last dot in method call chains can't exceed 80 characters. |
#101 |
0.3.6
Type |
Description |
Link |
Improvement |
Never put field annotations on the same line as the field declaration. |
#102 |
0.3.5
Type |
Description |
Link |
Fix |
Bring back inlining the prefix of method calls iff the levels inlined so far have all been simple. This fixes the regression introduced in 0.3.4 where long nested method calls would end up with too many indents. |
#99 |
0.3.4
Type |
Description |
Link |
Fix |
Stop indiscriminately stopping an inlining at method calls like SafeArg.of . |
#94 |
0.3.3
Type |
Description |
Link |
Fix |
Get rid of constant error in new Intellij 193 by replacing CodeStyleManager programmatically. |
#51 |
Fix |
"Before commit -> Reformat code" now correctly uses the PJF formatter if it is enabled, rather than the IntelliJ default formatter. |
#80 |
Fix |
When inlining a level's leading docs, check that no breaks were introduced more robustly. |
#85 |
0.3.2
Type |
Description |
Link |
Fix |
Limit dotted chains for expressions starting with constructor. |
#71 |