-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow passing the formatJavadoc flag to Google Java Formatter #614
Comments
Happy to take a PR for this (useful guide pr: #193). If you'd like to gradually unify the license headers, without ever having a history-clobbering "format-the-world" moment, maybe try |
Is there a workaround/hack for this? We can't adopt the Google formatter without this, as it unnecessarily changes the Javadoc in our entire codebase. |
The PR referenced above (#193) is a very similar situation. To my knowledge, no workaround besides a PR. |
Is it possible to support a generic way to pass options so that users aren't blocked every time a new option is added? |
Maybe! PR's welcome :) |
Closed by #1793. |
Back in November, the Google Java Formatter was updated to support turning off formatting of javadocs. This is particularly useful functionality with newer javadoc trends as well as older codebases that include heterogenous license headers.
Here is the PR that added the functionality: google/google-java-format#418
The text was updated successfully, but these errors were encountered: