Liam Miller-Cushon

+1 to what @kevinb9n said :) FWIW we have an [Error Prone check for missing braces](http://errorprone.info/bugpattern/MissingBraces) that can be run as a refactoring, which we use internally to help enforce...

The diff in the assertion message is: ```diff - LOGGER.warning(String.format(" @Gauge is configured\"\n + \" on a bean %s that is neither ApplicationScoped nor \"\n + \" Singleton. This is...

This change causes the formatter to never break in these places, even if breaks are necessary to prevent >100 character lines, e.g.: ```java class T { { ffffffffffffffffffffffffffffffffffffffffffffffffff( xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ->...

> What I imagine is something higher-level, like attaching a "priority" to each break, where the higher-priority breaks are taken before the lower-priority ones This is roughly what `clang-format` does,...

The original formatting exceeds the column limit, and the formatter doesn't introduce block or grid-like layouts, but if you manually reformat that into a grid the formatter will preserve that...

I think it was only fixed for cases where the `//$NON-NLS-1$` comment appears on its own line.

```java class T { void f() { switch (reference.getReferenceTypeCase()) { case A -> foo(); case B, default -> throw new IllegalArgumentException("Unhandled"); } } } ``` ``` java -jar google-java-format-1.15.0-all-deps.jar T.java...

Thanks. This is the first release using a new GitHub actions workflow, and obviously something went wrong there. I think the `mvn tycho-versions:update-eclipse-metadata -pl eclipse_plugin` failed to update the version...

This is related to #51 - the formatter doesn't currently make non-whitespace changes, and there are some difficulties to doing that we haven't addressed yet. Fixing imports and modifier order...

The formatter doesn't try to fix all style errors, only ones what involve whitespace between tokens. Replacing literal whitespace with escapes inside string literals seems feasible but slightly outside its...