vgaltes/crystalgazer

crystalgazer's Issues

Limit the number of items displayed in couplings by parameter

Evolution of churn

For the whole project. Lines added vs lines removed evolution in time.

Knowledge by author

Set a threshold of the number of times a file has been committed in order to appear in the couplings list.

To avoid non-important couplings.

Main suspects

Create a list of the main suspects to be refactored. Figure out a formula that takes into account churn, revisions, authors and lines by file.

To be able to define the evolution of the teams in the project

By date.

Evolution of files added vs files modified

Map authors

People change their username in git from time to time. We need to be able to map one name to another in order to have the right results.

We'll need to create a filed inside the .cg folder. Something like authorsMap.config:
vgaltes, Vicenç García-Altés
Vicenc, Vicenç García-Altés

MRI

Study the changes in C# files by function.

Knowledge by team

Export results to csv

Add an option on every command to allow exporting the results to a csv.

-e file.csv

Files committed by different teams

Dates on init

Allow specifying a date range in the init command.

Filter files by extension

I'd like to be able to exclude files from the study given its extension.

A file will need to be created in the .cg folder. Something like extensionsExclusions.config:
.config
.csproj
.xml

Display errors gracefully

Catch any exception and print it.

Churn by file

Create a new hotspot analysis type with the number of lines modified (lines added + lines deleted) per file. Order by the files with more churn.

Travis -> publish to NPM on tag