dev todos

Find TODO/LATER comments in configured scan roots

Command version
0.0.0
Command configuration
dev-tool:dev.todos@0.0.0

Arguments

ArgumentTypeRequiredDefaultDescription
--pathslist[string]No[]Optional explicit paths to scan instead of configured scan rootsRepeatable
--includelist[string]No[]File glob patterns to scan (defaults to common source/document types)Repeatable
--excludelist[string]No[]Repository-relative path patterns the scan does not read; repeatable. A repository that always excludes the same trees sets this under argDefaults in its cli.config.yml, at the todos command's scopeRepeatable
--patternstringNo"TODO|LATER"Regular expression matching the annotation token (placed in comment position)
--check, --no-checkbooleanNofalseExit non-zero when any matching comment is found
--sortstring one of path, tagNo"path"Sort matches by path or by tag

It also takes the global arguments.

Output

It answers with a todos.todoSummary.

Types

todos.todoSummary

FieldTypeRequiredDefaultDescription
matcheslist[todos.todoEntry]No[]Each annotation comment found, ordered by path and line, or by annotation first under --sort tag
matchCountintegerNo0How many comments matches holds
scannedFileCountintegerNo0How many files were read for annotations: the ones holding a comment, with excluded files left out
patternstringNo""The regular expression an annotation was matched by, as --pattern gave it
checkbooleanNofalseWhether the run was made with --check, under which any match fails it as TODOS_FOUND

todos.todoEntry

FieldTypeRequiredDefaultDescription
pathstringYesThe file the comment is in, relative to the repository root
lineintegerYesThe line of the file the comment is on, counted from 1
tagstringYesThe annotation that matched --pattern, such as TODO
messagestringNo""The comment's text after the annotation; empty where it says nothing more
ownerstringNo""What is written in parentheses directly after the annotation, as in TODO(name); empty where nothing is