We did an automated analysis of your code to detect potential areas to improve the code quality. We are sharing the results below, to help you improve the code further.
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
Example from src/main/java/duke/taskList/TaskList.java
lines 1-1
:
Suggestion: Follow the package naming convention specified by the coding standard.
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: Header Comments
Example from src/main/java/duke/command/ListCommand.java
lines 28-32
:
/**
* List out all tasks.
*
* @return String representation of the list of tasks.
*/
Example from src/main/java/duke/storage/Storage.java
lines 63-68
:
/**
* Initialize the old tasks into current list of Tasks.
*
* @return Array list of Task.
* @throws IOException If an input or output exception occurred.
*/
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 431e1ab
:
Resolved merge conflict
- Not in imperative mood (?)
possible problems in commit 8004442
:
Merged branch-A-CodeQuality
- Not in imperative mood (?)
possible problems in commit 570f1b0
:
Merged branch-A-Assertions
- Not in imperative mood (?)
Suggestion: Follow the given conventions for Git commit messages
โน๏ธ The bot account @cs2103-bot 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.