ndru@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 10 months agoThe color blurplelemmy.worldimagemessage-square24fedilinkarrow-up1184arrow-down110file-text
arrow-up1174arrow-down1imageThe color blurplelemmy.worldndru@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 10 months agomessage-square24fedilinkfile-text
From a site I’ve inherited which is full of things like this (and lots of other very !important things). Send help.
minus-squareEager Eagle@lemmy.worldlinkfedilinkEnglisharrow-up39·10 months agosed -i 's/.purple/.not-purple/g' *.css done, boss
minus-squaregregorum@lemm.eelinkfedilinkEnglisharrow-up11arrow-down1·10 months agoThis just gave me a panic attack
minus-squareactiv8r@sh.itjust.workslinkfedilinkEnglisharrow-up4·10 months agoIt’s fine as long as you have proper source control. Run it and check the diff before committing.
minus-squarelars@lemmy.sdf.orglinkfedilinkEnglisharrow-up1·edit-210 months agoBut I set my .git directories to have .css filename extensions!!?! It shouldn’t be my job to educate you.
minus-squareFoxBJK@midwest.sociallinkfedilinkEnglisharrow-up3·10 months agoGotta do it on the HTML files and JS files too. Then you gotta re-test every page that uses those files. Then the boss looks over your code and asks why you didn’t just change the actual color because that’s easier to QC.
sed -i 's/.purple/.not-purple/g' *.cssdone, boss
This just gave me a panic attack
It’s fine as long as you have proper source control. Run it and check the diff before committing.
But I set my
.gitdirectories to have.cssfilename extensions!!?! It shouldn’t be my job to educate you.Gotta do it on the HTML files and JS files too. Then you gotta re-test every page that uses those files.
Then the boss looks over your code and asks why you didn’t just change the actual color because that’s easier to QC.