repowisemcuteangel/hesabyaar

mcuteangel / hesabyaar

kotlinmain2c2889888.0K linessynced 22h ago

Code health

7.8out of 10Good

Hotspots average 6.3, the place fixes pay off most.

Full health report
Documentation818pages
0 with model-written prose, 818 built from the indexScore validation17/204.9× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 4

4 things worth doing in the week to Oct 29, the last indexed commit.

Worth planning

  • Tidy the code shape this week's commits left: 6 findings in 6 files

    6 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with app/src/main/java/io/github/mojri/hesabyar/ui/screens/CategoryManagementScreen.kt (1 finding): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    6
    files
    6
    commits
    6

  • Review why fixes keep landing in app/src/main/java/io/github/mojri/hesabyar/data/LoanDelegate.kt: tests reach it

    Changed 34 times in 90 days, and 26 of those commits were bug fixes.

    commits in 90 days
    34
    bug-fix commits
    26
    line coverage
    Unknown, no report
    tests that reach it
    21 test files, call graph(inferred)
    worth a check

  • Review why fixes keep landing in app/src/main/java/io/github/mojri/hesabyar/ui/screens/PersonDetailSheet.kt: tests reach it

    Changed 20 times in 90 days, and 16 of those commits were bug fixes.

    commits in 90 days
    20
    bug-fix commits
    16
    line coverage
    Unknown, no report
    tests that reach it
    1 test file, call graph(inferred)
    worth a check

  • Review why fixes keep landing in app/src/main/java/io/github/mojri/hesabyar/ui/screens/account/AccountManagementScreen.kt: tests reach it

    Changed 22 times in 90 days, and 14 of those commits were bug fixes.

    commits in 90 days
    22
    bug-fix commits
    14
    line coverage
    Unknown, no report
    tests that reach it
    3 test files, call graph(inferred)
    worth a check

Improve what Repowise can see

  • Add a test coverage report

    Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.

    line coverage
    Unknown, no report

Everything we found

5 areas

Every detector's open count by area. The actions above are the part worth doing.