11# code-complexity
22
3- > Measure the churn/complexity score. Higher values mean hotspots where
3+ > Measure the churn/complexity score. Higher values mean hotspots where
44> refactorings should happen.
55
66[ ![ Build Status] [ travis-image ]] [ travis-url ]
1010
1111Quoting Michael Feathers (source [ here] [ michael-feathers-source ] ):
1212
13- * Often when we refactor, we look at local areas of code. If we take a wider
14- view, using information from our version control systems, we can get a better
13+ * Often when we refactor, we look at local areas of code. If we take a wider
14+ view, using information from our version control systems, we can get a better
1515sense of the effects of our refactoring efforts.*
1616
1717
18- Note: ` code-complexity ` currently measures complexity using lines of code count.
19- While imperfect, this measure gives a good enough idea of what's going on.
18+ Note: ` code-complexity ` currently measures complexity using lines of code count.
19+ While imperfect, this measure gives a good enough idea of what's going on.
2020
2121## Usage
2222
@@ -28,21 +28,21 @@ $ npx code-complexity <path-to-git-directory or URL>
2828
2929``` text
3030 Usage: code-complexity <target> [options]
31-
31+
3232 Measure the churn/complexity score. Higher values mean hotspots where refactorings should happen.
33-
33+
3434 Options:
3535 -V, --version output the version number
3636 --filter <strings> list of globs (comma separated) to filter
37- -f, --format [format] format results using table or json
37+ -f, --format [format] format results using table, json or csv
3838 -l, --limit [limit] limit the number of files to output
3939 -i, --since [since] limit the age of the commit analyzed
4040 -s, --sort [sort] sort results (allowed valued: score,
4141 churn, complexity or file)
4242 -h, --help display help for command
43-
43+
4444 Examples:
45-
45+
4646 $ code-complexity .
4747 $ code-complexity https://github.com/simonrenoult/code-complexity
4848 $ code-complexity foo --limit 3
0 commit comments