Use sexp node size for issue mass, not flay score #84
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change fixes a bug, and impacts both remediation points
calculation and the issue mass reported in UI.
Motivation: create parity with Classic, and present user more
meaningful mass number.
An important behavioral departure from Classic is that we are no longer penalizing
extra for identical (as opposed) to similar duplicated code: remediation points
reflect the amount of effort needed to repair an issue, and perfectly identical code
can actually be easier to fix than code that is similar.
For reference, flay score is:
Similar code
node_size * number_of_occurrences_of_duplicated_issue
Identical code
node_size * num_occurrences * num_occurrences
@codeclimate/review @pbrisbin
Step two of breaking apart #78