Sharing iP code quality feedback [for @Morninggloryyy] - Round 2

@Morninggloryyy We did an automated analysis of your code to detect potential areas to improve the code quality. We are sharing the results below, so that you can avoid similar problems in your tP code (which will be graded more strictly for code quality).

IMPORTANT: Note that the script looked for just a few easy-to-detect problems only, and at-most three example are given i.e., there can be other areas/places to improve.

Aspect: Tab Usage

No easy-to-detect issues :+1:

Aspect: Naming boolean variables/methods

No easy-to-detect issues :+1:

Aspect: Brace Style

No easy-to-detect issues :+1:

Aspect: Package Name Style

No easy-to-detect issues :+1:

Aspect: Class Name Style

No easy-to-detect issues :+1:

Aspect: Dead Code

Example from src/test/java/damon/parser/ParserTest.java lines 14-14:


        //String exitCommand = "bye";

Example from src/test/java/damon/parser/ParserTest.java lines 15-15:


        //String showListCommand = "list";

Example from src/test/java/damon/parser/ParserTest.java lines 16-16:


        //String markCommand = "mark 1";

Suggestion: Remove dead code from the codebase.

Aspect: Method Length

No easy-to-detect issues :+1:

Aspect: Class size

No easy-to-detect issues :+1:

Aspect: Header Comments

No easy-to-detect issues :+1:

Aspect: Recent Git Commit Message

No easy-to-detect issues :+1:

Aspect: Binary files in repo

No easy-to-detect issues :+1:

:exclamation: You are not required to (but you are welcome to) fix the above problems in your iP, unless you have been separately asked to resubmit the iP due to code quality issues.

:information_source: The bot account used to post this issue is un-manned. Do not reply to this post (as those replies will not be read). Instead, contact cs2103@comp.nus.edu.sg if you want to follow up on this post.

Morninggloryyy / ip