3 ms·
Frankly, I saw this in a few projects and it feels like the responsible is one of those people that can't actually code but wants to convince management of thei
by dmichulke 8y ago
Frankly, I saw this in a few projects and it feels like the responsible is one of those people that can't actually code but wants to convince management of their impact with their huge commit stats.
I also hate whitespace but it's just a symptom (the other developers' editors / git config probably don't show the trailing whitespace).
Given this, it's a mere symptomatic remedy, the problem will reappear, and the only person benefiting from this is you. I'd hate to pay you for that.
- klibertp 8y agoFor what? 30 seconds of writing a sed command in the shell? I can donate that kind of time to the project for free, really.
- steve_adams_86 8y agoI think the process would include having the team become aware of the situation and improving their editor configuration to stop littering whitespace everywhere. Otherwise I agree, that seems like a waste of time to do in isolation. I'd probably address it more completely if so many files are going to be touched, and whitespace is only one symptom of bad formatting connections. Perhaps everyone should employ the same formatter on save, for example. There is far more value in that. Getting rid of only superfluous whitespace is a bit of a time sink for what you get in return (as much as it drives me nuts).