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
We are currently using the Java formatter provided by the VS Code extension Language Support for Java(TM) by Red Hat. VS Code is configured to format Java files when saving using the configuration file eclipse-java-google-style.xml.
There are two issues with this approach:
Google is moving away from eclipse-java-google-style.xml, which has not been updated in years (see this post).
The files generated by the OpenAPI generator should be formatted similarly to the non-generated files. The only viable approach is to run the formatter programmatically, which is not possible using the extension Language Support for Java(TM) by Red Hat.
Tasks:
Remove the file eclipse-java-google-style.xml from the workspace folder.
We are currently using the Java formatter provided by the VS Code extension
Language Support for Java(TM) by Red Hat
. VS Code is configured to format Java files when saving using the configuration fileeclipse-java-google-style.xml
.There are two issues with this approach:
eclipse-java-google-style.xml
, which has not been updated in years (see this post).Language Support for Java(TM) by Red Hat
.Tasks:
eclipse-java-google-style.xml
from the workspace folder.google-java-format
when saving Java files (see instructions).docs/linters-and-formatters.md
.Future tasks:
The text was updated successfully, but these errors were encountered: