irelephant 🍭 to Programmer [email protected]English • 1 month agolooks good to melemm.eeimagemessage-square49fedilinkarrow-up1751arrow-down18cross-posted to: [email protected]
arrow-up1743arrow-down1imagelooks good to melemm.eeirelephant 🍭 to Programmer [email protected]English • 1 month agomessage-square49fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink24•1 month agoMeanwhile in another universe one of my biggest win was to introduce this line in our PR validation pipeline. eslint . --max-warnings 0
minus-square@[email protected]linkfedilink3•1 month agoWorks so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.
minus-square@[email protected]linkfedilink3•1 month 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-square@[email protected]linkfedilink2•1 month 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 0Works so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.
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.