Skip to content

Commit 6e3da26

Browse files
committed
Say on the Style page that 2.x fixes bugs
The trade-off still said that the output of the whole 2.x line is byte-for-byte that of palantir-java-format, which stopped being true with the fixes of 2.98.0.3. Like the home page, it now says the output is the same except where it fixes a bug, and points at the list on Migrate. The heading says "layout changes" instead of "layout fixes", because fixes are what 2.x does take.
1 parent cac888e commit 6e3da26

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

‎docs/style.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -157,6 +157,7 @@ class Comments {
157157
}
158158
```
159159

160-
- **Layout fixes of our own wait for 3.x.** For the whole 2.x line the output is byte-for-byte the
161-
same as the palantir-java-format release with the same version number. The
162-
[manifesto](manifesto.md) explains why output stability comes first.
160+
- **Layout changes of our own wait for 3.x.** For the whole 2.x line the output is the same as the
161+
palantir-java-format release with the same version number, except where it fixes a bug, such as a
162+
JBang script whose directives the formatter broke. [Migrate](migrate.md#from-palantir-java-format)
163+
lists those fixes, and the [manifesto](manifesto.md) explains why output stability comes first.

0 commit comments

Comments
 (0)