During code review, I noticed many nits could be caught by static analysis.
I also noticed many bugs I've run into could also be caught by static analysis.
I looked into writing custom ESLint rules, but often they required more ceremony and boilerplate than I had time for.
A friend who worked on a mobile project at Google said he had written dozens of regex checks to ensure code quality and catch various bugs.
I was incredulous and asked why he wouldn't use a more "proper" AST static analyzer.
The fact was, he had bigger fish to fry and sometimes a simple regex check is all you need.
I tried writing some regex checks like this, and found it to be quick, yet yielding good returns.
Thus I wrote checkr, a VS Code extension that allows devs to plugin simple regex checks right away.
3 comments
[ 4.3 ms ] story [ 12.9 ms ] threadA friend who worked on a mobile project at Google said he had written dozens of regex checks to ensure code quality and catch various bugs. I was incredulous and asked why he wouldn't use a more "proper" AST static analyzer. The fact was, he had bigger fish to fry and sometimes a simple regex check is all you need. I tried writing some regex checks like this, and found it to be quick, yet yielding good returns.
Thus I wrote checkr, a VS Code extension that allows devs to plugin simple regex checks right away.