-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Switch to Spotless Groovy formatter #843
Comments
If you like can provide you with a proposal (PR) next week. We would need to switch to spotless 3.3.2, since I will need the fix for diffplug/spotless#106. |
That would be great! 👍 |
Happy that you are interested in my work. |
Sure, no worries. |
@marcphilipp Sorry Marc, I am not familiar with the JUnit PR cycle. Is there anything your are waiting for regarding #860? I currently waiting for a feed back whether the proposal is as such acceptable before applying the changes agreed upon (like this finding). |
@marcphilipp I did not want to rush the things, was just not sure whether you guys waited for something I should do. Thanks for the review. There is something I want to check on the auto paddedCell feature applied by Spotless, before I answer your review comments. |
Sure, no worries. |
Last question: Are you (in a separated PR) interested to apply the formatter on the Gradle files as well? |
Apply the formatter? I thought that was what #860 is doing, isn't it? I'm sure I'm missing something. Please try to clarify. 🙂 |
Currently it only selects the groovy files. |
Sorry, I mixed up Gradle and Groovy... 🙈 A formatting check for Gradle files sounds like a good idea! Please open a new issue/PR for that if you have time! |
Ok. Will come back to you on #860 next week (no time this weekend). When this issue is solved to everybody's convenience, I'll provide you with another PR. The difference between groovy and gradle is just that the import sorter and license header check needs to be removed. |
@marcphilipp I am not so firm with the review process. Do you expect my changes as another commit so that you can see differences, or do you prefer a squashed PR to keep the history clean? |
Feel free to push additional commits to the existing branch. We can squash it when we merge it if we see fit. |
Overview
We currently use a custom formatting config for Groovy source files. Now that diffplug/spotless#13 is fixed, we should switch to use GrEclipse formatting for Groovy files.
Deliverables
The text was updated successfully, but these errors were encountered: