This one should be fun and relatively small!!
Your mission, should you choose to accept it, would be to come up with and implement
tink lint aka the default, built-in linter for tink! The idea is to come up with a baseline linting strategy and apply it across the board. Eventually, users will be able to provide their own scripts on top of this, but I’d like to start with a zero-config, reasonable-enough linting rule setup.
Most likely, this looks like
eslint:recommended rules for
eslint, which are meant to be relatively unopinionated but catch potential bugs and major readability issues.
We would be incorporating
eslint directly into the project, and users will be able to call
tink lint themselves to run it on their project. The end result should be a widespread increase in code quality (or at least in random persons getting annoyed at us). Either way, it’s a win, so let’s do this!
If you’re interested in picking this one up, just reply below and claim it and it’ll be yours as long as you don’t take several weeks to get around to it. Thank you in advance, and as always, I’m here to answer questions and provide support to anyone who’s kind enough to be donating their time to help me with this. Have a good one!