Skip to content

Smell cost explanation? #426

@markadrianagbuya

Description

@markadrianagbuya

Recently I modified the reek configuration to ignore some smells in some directories. I noticed that while the number of code smells for the files changed, the overall score didn't change. This was unexpected for me.

After diving deeper, I see that the cost of a Reek smell is 0. If I understand correctly, this means that smells found by Reek, don't have an impact on the cost, rating or overall score. If this is the case, this was unintuitive as our team have been trying to improve the score by address a lot of the reek smells.

Is there an explanation or documentation that summarises the idea behind the scoring? I have read the Core Metrics, Score and Rating and Code Climate Score Doc however, I feel it would be good to explicitly describe how the cost is determined and explicitly describe the intentions behind the cost and weights (i.e., why reek smells are 0 and why flog and flay costs are X).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions