Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Sharing iP code quality feedback [for @salty-flower] - Round 2 #4

Open
nus-se-script opened this issue Mar 14, 2023 · 0 comments
Open

Comments

@nus-se-script
Copy link

@salty-flower 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

No easy-to-detect issues 👍

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/Tach.java lines 25-28:

    /**
     * The main method to launch the program.
     * @param args Command line arguments.
     */

Example from src/main/java/services/Dispatcher.java lines 62-65:

    /**
     * The lambda expression from driver class to indicate exit of the entire program.
     * @param toExit The lambda to trigger program exit.
     */

Example from src/main/java/services/SpeakerRegistry.java lines 13-16:

    /**
     * Add a new speaker.
     * @param s Speaker to add.
     */

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 Message (Subject Only)

possible problems in commit 54659d4:

:children_crossing:Improve GUI

  • Not in imperative mood (?)

possible problems in commit a6ca6c8:

:children_crossing:Fix ellipsis

  • Not in imperative mood (?)

possible problems in commit a8fb7ea:

:children_crossing:Improve GUI

  • Not in imperative mood (?)

Suggestion: Follow the given conventions for Git commit messages for future commits (no need to modify past commit messages).

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 [email protected] if you want to follow up on this post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant