report-todo v1.0.1

report-todo

Generate reports of TODO, FIXME, BUG etc. comments across trees of text files.

Features:

• Easy setup, as report-todo does not try to understand the grammar of the used programming languages and detect comments, but it simply searches for the configured tags naively, i.e. without regard for the used programming language, and tries to detect the respective comments by looking at how lines start
• Support for multiline comments
• Support for comment labels/tags
• The Markdown report provides links to the files and lines where the comments are found, giving a quick way to open them when using code editors that can preview Markdown documents, for example Vim or Visual Studio Code
• Both CLI command and Node.js API
• Highly configurable

Quick installation and usage

$ npm install -g report-todo
$ report-todo my/project/directory/

...but I don't want to install it system-wide!

$ cd my/project/directory/
$ npm install report-todo
$ npx report-todo

I use Arch Linux, can I use pacman?

Install the report-todo package with your favorite AUR helper.

Otherwise follow the manual instructions.

Then just run the report-todo command.

I want JSON, not Markdown

$ report-todo -m json

Report examples

These are based on src/DEMO.js.

Markdown

$ report-todo aux/DEMO.js -m markdown

# Table of contents

1. [#45](#1-0)
2. [[NO LABEL]](#1-1)
3. [defect](#1-2)
4. [setup](#1-3)

# #45<a id="1-0"></a>

| file path | line # | tag | labels | comment
|:----------|:-------|:----|:-------|:-------
| [./aux/DEMO.js](./aux/DEMO.js#L11) | 11 | BUG | defect,#45 | Solve this problem<br>This second line adds more details<br>So does this third line

# [NO LABEL]<a id="1-1"></a>

| file path | line # | tag | labels | comment
|:----------|:-------|:----|:-------|:-------
| [./aux/DEMO.js](./aux/DEMO.js#L1) | 1 | TODO |  | Simple comment without labels

# defect<a id="1-2"></a>

| file path | line # | tag | labels | comment
|:----------|:-------|:----|:-------|:-------
| [./aux/DEMO.js](./aux/DEMO.js#L11) | 11 | BUG | defect,#45 | Solve this problem<br>This second line adds more details<br>So does this third line

# setup<a id="1-3"></a>

| file path | line # | tag | labels | comment
|:----------|:-------|:----|:-------|:-------
| [./aux/DEMO.js](./aux/DEMO.js#L6) | 6 | TODO | setup | I can make this do a lot more<br>It's all written here

JSON

$ report-todo aux/DEMO.js -m json

[
  {
    "type": "labels",
    "key": "#45",
    "matches": [
      {
        "filePath": "./aux/DEMO.js",
        "tag": "BUG",
        "startLineNo": 11,
        "lines": [
          "Solve this problem",
          "This second line adds more details",
          "So does this third line"
        ],
        "labels": [
          "defect",
          "#45"
        ]
      }
    ]
  },
  {
    "type": "labels",
    "key": "[NO LABEL]",
    "matches": [
      {
        "filePath": "./aux/DEMO.js",
        "tag": "TODO",
        "startLineNo": 1,
        "lines": [
          "Simple comment without labels"
        ],
        "labels": []
      }
    ]
  },
  {
    "type": "labels",
    "key": "defect",
    "matches": [
      {
        "filePath": "./aux/DEMO.js",
        "tag": "BUG",
        "startLineNo": 11,
        "lines": [
          "Solve this problem",
          "This second line adds more details",
          "So does this third line"
        ],
        "labels": [
          "defect",
          "#45"
        ]
      }
    ]
  },
  {
    "type": "labels",
    "key": "setup",
    "matches": [
      {
        "filePath": "./aux/DEMO.js",
        "tag": "TODO",
        "startLineNo": 6,
        "lines": [
          "I can make this do a lot more",
          "It's all written here"
        ],
        "labels": [
          "setup"
        ]
      }
    ]
  }
]

Command-line usage

Running the command without arguments will parse the files in and under the current working directory:

$ report-todo

The above command is equivalent to:

$ report-todo ./

Pass multiple arguments to parse files under various patterns. Patterns are processed with globby, which for example also supports negative (exclude) matches by prefixing them with an exclamation mark. Some patterns are also excluded by default, see also the --no-default-excludes option. For example:

$ report-todo ./src ./docs !./test

Use the --help option to print a quick usage guide and a list of all the available CLI options:

$ report-todo --help

Or, if locally installed in a directory:

$ npx report-todo --help

Options

Node.js API

Require the reportTodo() function from the report-todo module.

const {reportTodo} = require('report-todo')

The reportTodo() function accepts two arguments:

reportTodo(globs, options)

globs is a pattern or array of patterns that indicate the root paths under which files will be parsed. globs is processed by globby, which for example also supports negative (exclude) matches by prefixing them with an exclamation mark.

options is an object of key:value configuration pairs:

reportTodo(globs, {
  tags,
  labels,
  labelsDelimiters,
  labelsSeparator,
  labelsIsBlacklist,
  caseInsensitive,
  ignoreLineComment,
  reportMode,
  reportGroupBy,
  reportSortBy,
  reportLinksPrefix,
}

Options

Examples

Pre-grouped/sorted object:

const {reportTodo} = require('report-todo')

reportTodo(`./src/`, {reportMode: 'object'}).then((report) => {
  console.log(report)
})

Asynchronous generator:

const {reportTodo} = require('report-todo')

const generator = reportTodo(`./src/`, {reportMode: 'generator'})

for await (const todo of generator) {
  console.log(todo)
}

Todo match objects

Some report modes such as generator, object and json list results as objects with the following keys:

Similar projects

• Leasot: the goal is similar, however Leasot attempts to detect the comments according to the specific syntax of the programming languages used in the parsed files.

License

MIT, see LICENSE.