Earlier quoted context omitted.
Yep, truly avoiding false positives and capturing all todos you would need to really parse the source code (perhaps creating an AST or lexical parsing). Even if you build that tool (which handles many languages) - it has an extra headache cost with the parsing time, which might be really slow for large projects. I actually started Leasot with Javascript AST checking which never misses TODOS but is very hard to extend…
Just out of interest, how often do you find yourself using "TODO" as a variable name or elsewhere in your code? This isn't a dig, it's just something I've genuinely never stumbled across in 2 decades of programming so wondered if there's a culture out there I've missed.
Show HN: Parse and output TODOs and FIXMEs from comments in your files
41–44 of 44 posts
Re: Show HN: Parse and output TODOs and FIXMEs from comments in your files
#42Earlier quoted context omitted.
If you have TODO outside of comments which are false positives, you need to see those, and weed them out along with the true TODO items. This TODO scanner project is completely, utterly, pointless.
There is no need for your second line. Your first line is a valid, relevant opinion. The second one has no use but to belittle the OP (or anyone else who has written a TODO scanner). You're being a dick, and missing the forest for the trees while you're at it. This project can be integrated into a larger gulp workflow, for example. It also has the ability to write the output to custom formats.
TODO comments could automatically be turned into action items, against the developer who introduced them (git blame!)
The software could be intelligent enough to uncover relationships among the TODO's, and schedule a meeting for specific subsets of TODO's, calling in all the relevant peo^H^H^H stake holders.
Re: Show HN: Parse and output TODOs and FIXMEs from comments in your files
#43Visual Studio does this automatically. 1. View -> Task List 2. At the top of the task list click the drop-down that is by default set to "User Tasks" and choose "Comments." You can also customize the trigger words[1]. I very rarely use the feature myself as failing unit tests are far superior when compared to TODOs. [1]: https://msdn.microsoft.com/en-us/library/zce12xx2.aspx
You can also configure the text for each tag (TODO, FIXME, etc.) as well as the priority.