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
Indent with spaces rather than with tabs #4202
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4202 +/- ##
===============================================
- Coverage 57.996% 57.993% -0.003%
Complexity 2334 2334
===============================================
Files 645 645
Lines 34578 34578
Branches 5976 5976
===============================================
- Hits 20054 20053 -1
Misses 12366 12366
- Partials 2158 2159 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Hi @mernst, given this is so large of a change and impact it can have on existing pulls, maybe it can be approached in a separate way. Here are my thoughts on it.
Just my food for thought, and I agree tags in any files are bad. Not very cross platform nice and its getting mixed by contributors is pretty frequent. If you don't already you may want to make sure to have plugin do this automatically after done so it doesn't happen again. Spotless maven plugin is probably best candidate to cover the files in fast way. |
There are also some tricks, I've seen 'maven' team doing where they make git ignore the commits involved since they add little value and can be seen as a lot of noise. Not sure that is worth the effort or concern as one can ignore whitespace and this is same line stuff but worth noting that is possible with git. |
I agree that use of Spotless is better than trying to manually enforce the style. It can also "ratchet": enforce formatting only for lines that have changed, so there are no irrelevant changes in the version control history. I'll leave applying the |
The JavaParser codebase mainly uses spaces for indentation. However, in a few places it inconsistently uses tabs. This pull request changes tabs to spaces in
.java
files.