Command Line Interface
To use the package as a command-line tool, run:
$ dcm <command> lib
It will produce a result in one of the supported formats:
- Console
- GitHub
- Checkstyle
- Codeclimate
- HTML
- JSON
Available commands
The following table shows which commands you can use with the tool:
Command | Example of use | Short description |
---|---|---|
analyze | dcm analyze lib | Reports code metrics and rules violations. |
fix | dcm fix lib | Fixes issues produced by dcm analyze command. |
check-exports-completeness | dcm check-exports-completeness lib | Checks that an exported API exports all used types. |
check-unnecessary-nullable | dcm check-unnecessary-nullable lib | Checks unnecessary nullable parameters. |
check-unused-files | dcm check-unused-files lib | Checks unused *.dart files. |
check-unused-l10n | dcm check-unused-l10n lib | Checks unused localization in *.dart files. |
check-unused-code | dcm check-unused-code lib | Checks unused code in *.dart files. |
For additional help on any of the commands:
$ dcm <command> --help
Multi-package repositories usage
If you run a command from the root of a multi-package repository (a.k.a. monorepo), it'll pick up analysis_options.yaml
files correctly.
Additionally, if you use Melos, you can add custom command to the melos.yaml
.
melos.yaml
metrics:
run: |
melos exec -c 1 --ignore="*example*" -- \
dcm analyze lib
description: |
Run DCM in all packages.
- Note: you can also rely on your IDEs Dart Analysis / Issues window.