@skyl3-r 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 iP 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
No easy-to-detect issues 👍
Aspect: Class Name Style
No easy-to-detect issues 👍
Aspect: Dead Code
Example from src/main/java/barcus/command/DeleteCommand.java lines 32-32:
//tasks.get(pos - 1).markDone();
Example from src/main/java/barcus/command/DeleteCommand.java lines 33-33:
//talk("Good job! Have marked as done: " + tasks.get(pos - 1));
Example from src/main/java/barcus/command/DeleteCommand.java lines 34-34:
//Task temp = tasks.deleteTask(pos - 1);
Suggestion: Remove dead code from the codebase.
Aspect: Method Length
No easy-to-detect issues 👍
Aspect: Class size
No easy-to-detect issues 👍
Aspect: Header Comments
Example from src/main/java/barcus/Barcus.java lines 76-80:
/**
* Main code that runs when barcus file runs
* Creates a barcus instance
* @param args
*/
Example from src/main/java/barcus/display/Launcher.java lines 9-12:
/**
* Main class to launch the application
* @param args
*/
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
No easy-to-detect issues 👍
Aspect: Binary files in repo
No easy-to-detect 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.
@skyl3-r 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 iP 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
No easy-to-detect issues 👍
Aspect: Class Name Style
No easy-to-detect issues 👍
Aspect: Dead Code
Example from
src/main/java/barcus/command/DeleteCommand.javalines32-32://tasks.get(pos - 1).markDone();Example from
src/main/java/barcus/command/DeleteCommand.javalines33-33://talk("Good job! Have marked as done: " + tasks.get(pos - 1));Example from
src/main/java/barcus/command/DeleteCommand.javalines34-34://Task temp = tasks.deleteTask(pos - 1);Suggestion: Remove dead code from the codebase.
Aspect: Method Length
No easy-to-detect issues 👍
Aspect: Class size
No easy-to-detect issues 👍
Aspect: Header Comments
Example from
src/main/java/barcus/Barcus.javalines76-80:Example from
src/main/java/barcus/display/Launcher.javalines9-12: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
No easy-to-detect issues 👍
Aspect: Binary files in repo
No easy-to-detect 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.sgif you want to follow up on this post.