You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the IntelliJ google-java-formatter 1.16.0.2 with the AOSP style, the "Optimize Imports" action results in empty lines between imports with different TLDs.
When using spotless:check with google-java-formatter 0.16.0 / 0.17.0 and AOSP, it complains that all but the first empty line have to be removed. The online documentation seems to agree with spotless.
The IntelliJ plugin does not break the Google Java Style Guide when executing "optimize imports".
Context
This being inconsistent between spotless and Intellij is very inconvenient. We use use spotless in the CI to enforce the codestyle and this necessitates running mvn spotless:apply for every commit or disabling "optimize imports" which itself results in manual cleanup of unused imports.
I have tried it with the default GOOGLE style and that does not seem to have this problem.
The text was updated successfully, but these errors were encountered:
This is happening for me as well when the "AOSP" style is selected, but not during "Optimize Imports", but with the basic "Reformat Code" action. This is really a downer, since the Gradle task verifyGoogleJavaFormat then disagrees and does not want to see blank lines, whereas the IJ plugin automatically creates new blank lines with the next reformat.
It also made no differences to clear out the import layout in IJ's code style settings (as expected), the blank lines are added by the plugin anyways.
I'm using GJF 1.19.1 and the IJ plugin 1.17.0.0. It also makes no difference if the Gradle plugin's GJF version is downgraded to 1.17.0, same results.
When using the IntelliJ google-java-formatter 1.16.0.2 with the AOSP style, the "Optimize Imports" action results in empty lines between imports with different TLDs.
Given:
Results in:
Expected:
When using
spotless:check
with google-java-formatter 0.16.0 / 0.17.0 and AOSP, it complains that all but the first empty line have to be removed. The online documentation seems to agree with spotless.The IntelliJ plugin does not break the Google Java Style Guide when executing "optimize imports".
Context
This being inconsistent between spotless and Intellij is very inconvenient. We use use spotless in the CI to enforce the codestyle and this necessitates running
mvn spotless:apply
for every commit or disabling "optimize imports" which itself results in manual cleanup of unused imports.I have tried it with the default
GOOGLE
style and that does not seem to have this problem.The text was updated successfully, but these errors were encountered: