irelephant [he/him]🍭@lemm.ee to Programmer Humor@programming.devEnglish · 1 year agolooks good to melemm.eeimagemessage-square48linkfedilinkarrow-up1771arrow-down19cross-posted to: programmerhumor@lemmy.ml
arrow-up1762arrow-down1imagelooks good to melemm.eeirelephant [he/him]🍭@lemm.ee to Programmer Humor@programming.devEnglish · 1 year agomessage-square48linkfedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squarepscamodio@feddit.itlinkfedilinkarrow-up25·1 year agoMeanwhile in another universe one of my biggest win was to introduce this line in our PR validation pipeline. eslint . --max-warnings 0
minus-squarepscamodio@feddit.itlinkfedilinkarrow-up3·1 year agoIn a codebase with a lot of warnings is even better for me to add a disable comments for all the existing warning and then not allow any new one in. And then each time a part of the code needs to be touched the existing warning there should be solved too.
minus-squarejjjalljs@ttrpg.networklinkfedilinkarrow-up2·1 year agoSeveral times I’ve set the max warnings to whatever the current warning count is, and then decreased that over time.
Meanwhile in another universe one of my biggest win was to introduce this line in our PR validation pipeline.
eslint . --max-warnings 0deleted by creator
In a codebase with a lot of warnings is even better for me to add a disable comments for all the existing warning and then not allow any new one in.
And then each time a part of the code needs to be touched the existing warning there should be solved too.
Several times I’ve set the max warnings to whatever the current warning count is, and then decreased that over time.