DarkPlayer@lemmy.world to Programming@programming.dev · 11 months agoUnicode tricks in pull requests: Do review tools warn us?semanticdiff.comexternal-linkmessage-square5fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1external-linkUnicode tricks in pull requests: Do review tools warn us?semanticdiff.comDarkPlayer@lemmy.world to Programming@programming.dev · 11 months agomessage-square5fedilink
minus-squaremonk@lemmy.unboiled.infolinkfedilinkarrow-up0·11 months agoHomoglyphs? Invisible text? Bidirectional text? Just highlight every line that goes beyond ASCII with yellow warning colors and require to vet it. Maybe make localization data an exception.
minus-squarearthur@lemmy.ziplinkfedilinkEnglisharrow-up0·11 months agoOr the non-ascii character itself.
minus-squaremonk@lemmy.unboiled.infolinkfedilinkarrow-up0·11 months agoDoesn’t work if it’s invisible.
minus-squareGurfaild@feddit.delinkfedilinkarrow-up0·11 months agoHow would you draw a box around U+202C?
Homoglyphs? Invisible text? Bidirectional text? Just highlight every line that goes beyond ASCII with yellow warning colors and require to vet it. Maybe make localization data an exception.
Or the non-ascii character itself.
Doesn’t work if it’s invisible.
what about a box around it?
How would you draw a box around U+202C?