Pankraz76
Pankraz76
spotless: 100% CONFIGURING [3m 23s] > Storing configuration cache state > :
im wondering why gradle cache takes so much more on spotless goal compared to checkstyle. > Our answer was no. It's unreasonable to expect that somebody will review a PR...
> you conduct it in your fork. Yes, kind of — that’s definitely the better place for this sort of change. But in my opinion, my fork somehow isn’t running...
> will review a PR with 5000+ changed files. explizit reply here and apoligoy this was a little too off.. dont want to get banned. just want to increment. next...
> this particular question what about rewrite? this was actually the goal spotless is just a sidekick for whitespaced its no big deal just for this project somehow. It did...
kindly asking, if this is any good?
yes this recipe is quite questionable therefore disabled in gradle as well. But the counterpart is quite impressive. Is this something to reconsider, please? - https://github.com/gradle/gradle/pull/35878
yes but having easy code access helps to read the code better to then prevent or quicker fix some issues or create new (features or course).
of course i dont demand any style but for me its overwelaming to read and avoid all the nonsens overhead i dont need and want to conider when dealing with...
with: without: test working assuming version issue.