Joshua Clayton 2650e1f040 Improve likelihood calculation and include reasons for evaluation ... Why? ==== A simple calculation ("yes, this should be removed" or "no, this is probably fine") is frankly not enough information for someone evaluating their codebase to understand why we made the decision. This introduces a removal reason, so a user understands why we ranked it the way we did, and adds additional logic around a method and its tests to determine if a method exists and is only being used in the tests (if so, it should probably be deleted). This is done with an Occurrances record, which is created for total files, test code, and non-test code. The test code logic is somewhat naive but works in most cases. It doesn't ensure a particular directory, in the case that tests live alongside source code (e.g. Go), and captures RSpec cases as well.		2016-05-11 05:18:55 -04:00
..
Unused	Improve likelihood calculation and include reasons for evaluation	2016-05-11 05:18:55 -04:00
Spec.hs	Add Hspec and tests around parsing	2016-05-08 06:54:34 -04:00