I have 6830 java files in my maven project (found with git ls-files "*.java" | wc -l) spread across 44 modules. When I have no changes (git diff --name-only origin/develop returns nothing) and I scan in ratchet mode, it takes nearly 10 minutes to do a no-op. When I removed ratchet mode because I wanted to see how many files were still misformatted, it took less than 20 seconds, even though it had to process every java file.
I was expecting it to be a lot slower because it had to actually read and format 6830 java files, rather than just look at git and see nothing has changed.
If you are submitting a bug, please include the following:
If you're just submitting a feature request or question, no need for the above.
I have 6830 java files in my maven project (found with
git ls-files "*.java" | wc -l) spread across 44 modules. When I have no changes (git diff --name-only origin/developreturns nothing) and I scan in ratchet mode, it takes nearly 10 minutes to do a no-op. When I removed ratchet mode because I wanted to see how many files were still misformatted, it took less than 20 seconds, even though it had to process every java file.I was expecting it to be a lot slower because it had to actually read and format 6830 java files, rather than just look at git and see nothing has changed.
If you are submitting a bug, please include the following:
gradlew spotless[Apply/Check] --stacktraceIf you're just submitting a feature request or question, no need for the above.