The next release of todocheck – the tool that helps you track & keep TODOs actionable is live!
First time you hear about it? – check this out first.
In version 0.2.0, the main focus was extending support to new programming languages & issue trackers.
Hence, there are now five new languages supported – R, PHP, Rust, Swift & Groovy.
Support has been also provided for two new issue trackers – Pivotal Tracker & Redmine.
Additionally, one useful new feature is that todocheck now supports passing in your issue tracker authentication token via an environment variable – this will make it a lot easier to integrate the tool in your CI environment!
Finally, you can now specify todocheck’s output to be in JSON format. This provides the opportunity to create IDE plugins or include support for todocheck into linter aggregators.
See the full changelog here & don’t forget to update your binary to the latest release!
Yesterday, I released todocheck – a new kind of static code analyser for annotated TODOs.
Way too often, we let leftover TODOs slip into our main branch, which leaves your coworkers puzzles, looking at it a year from now.
They’re thinking – what did I mean by “TODO: Move this to the users package”? What is the users package? It doesn’t seem to exist anymore.
todocheck helps you fix this by forcing you to mark all your TODOs against an existing, open issue in your issue tracker.
That way, if you, at some point, close the issue, thinking you’re done, the CI pipeline will sparkle in red as there is an open, unaddressed TODO in your main branch.
No longer can developers close a half-baked issue, rushing for the weekly sprint review to say “I’m done!”.