Skip to content

Sharing iP code quality feedback [for @duyLeu] - Round 3 #4

@soc-se-script

Description

@soc-se-script

@duyLeu 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 👍

Aspect: Naming boolean variables/methods

Example from src/main/java/moon/models/Task.java lines 12-12:

    private boolean done;

Example from src/main/java/moon/parser/util/DateTimeChecker.java lines 45-45:

        boolean valid;

Suggestion: Follow the given naming convention for boolean variables/methods (e.g., use a boolean-sounding prefix).You may ignore the above if you think the name already follows the convention (the script can report false positives in some cases)

Aspect: Brace Style

No easy-to-detect issues 👍

Aspect: Package Name Style

No easy-to-detect issues 👍

Aspect: Class Name Style

No easy-to-detect issues 👍

Aspect: Dead Code

No easy-to-detect issues 👍

Aspect: Method Length

No easy-to-detect issues 👍

Aspect: Class size

No easy-to-detect issues 👍

Aspect: Header Comments

Example from src/main/java/moon/ui/DialogBox.java lines 80-82:

    /**
     * Factory for a user dialog bubble.
     */

Example from src/main/java/moon/ui/DialogBox.java lines 89-91:

    /**
     * Factory for a bot dialog bubble. The bubble is flipped so the avatar appears on the left.
     */

Example from src/main/java/moon/parser/util/ParseChecker.java lines 95-101:

    /**
     * Check if the given index is out of bounds for the task list.
     *
     * @param index the index to check
     * @param list  the task list being accessed
     * @throws InvalidIndexException if the index is negative or greater than/equal to the list size
     */

Suggestion: Ensure method/class header comments follow the format specified in the coding standard, in particular, the phrasing of the overview statement.

Aspect: Recent Git Commit Messages

No easy-to-detect issues 👍

Aspect: Binary files in repo

No easy-to-detect issues 👍


❗ 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.

ℹ️ 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions