-
Notifications
You must be signed in to change notification settings - Fork 14
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
Google Java format #115
Google Java format #115
Conversation
…heck/apply google java format
i'm all for the stable code formatting (thx!). My only concern is if we have any significant code change PRs, merging them would be a bit more difficult due to merge conflicts. Are there any PRs that should be merged first? |
Yes, I plan to hold on this until it's 100% certain everything in-flight is merged (will confirm with folks in slack). But, wanted to get this going for initial review. Will mark draft for now to indicate I don't plan to merge yet. |
Noting that this PR intended to check 2 things:
Now that 2 is confirmed, I'll revert 2 in order to make this PR mergable without merge conflicts against other in-flight PRs. Then we can circle back separately to decide when to apply the formatting overall. Sound good? |
Sounds good. Do you want to make #116 change (file paths in |
That feels like it could break in-flight PRs. So I'm thinking to merge this without additional/any breaking changes. Then followup with a formatting PR that changes the code in src/ and then yes, adding in #116 would be great. |
hope we can merge this soonish (and run the global reformat) |
We have prettier/ESLint for JS. This introduces consistent formatting tools for Java.
I don't personally have opinions about what formatter to use. Google's just seemed like a reasonable first place to start.
This uses https://github.com/diffplug/spotless/tree/main/plugin-gradle as a simple and efficient way to apply & enforce the Java format.