You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Eclipse-Dominator 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.
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)
publicvoiddataToCommandTest() {
ParsedDatadummy;
// new ParsedData(bye, "b", "c");for (CommandsEnumc : CommandsEnum.values()) {
dummy = newParsedData(c.toString(), "b", "c");
Commandcommand = DataParser.dataToCommand(dummy);
assertEquals(commandinstanceofCommand, true);
if (commandinstanceofByeCommand && c == CommandsEnum.BYE) {
continue;
}
if (commandinstanceofListCommand && c == CommandsEnum.LIST) {
continue;
}
if (commandinstanceofMarkCommand && c == CommandsEnum.MARK) {
continue;
}
if (commandinstanceofUnmarkCommand && c == CommandsEnum.UNMARK) {
continue;
}
if (commandinstanceofDeleteCommand && c == CommandsEnum.DELETE) {
continue;
}
if (commandinstanceofTodoCommand && c == CommandsEnum.TODO) {
continue;
}
if (commandinstanceofDeadlineCommand && c == CommandsEnum.DEADLINE) {
continue;
}
if (commandinstanceofEventCommand && c == CommandsEnum.EVENT) {
continue;
}
if (commandinstanceofByCommand && c == CommandsEnum.BY) {
continue;
}
if (commandinstanceofFindCommand && c == CommandsEnum.FIND) {
continue;
}
if (commandinstanceofAliasCommand && c == CommandsEnum.ADDCOMMAND) {
continue;
}
if (commandinstanceofDeleteAliasCommand && c == CommandsEnum.DELETECOMMAND) {
continue;
}
if (commandinstanceofSwapFaceCommand && c == CommandsEnum.SWAP) {
continue;
}
if (commandinstanceofResetAliasCommand && c == CommandsEnum.RESETALIAS) {
continue;
}
if (commandinstanceofInvalidCommand && c == CommandsEnum.INVALID) {
continue;
}
fail();
}
}
Suggestion: Consider applying SLAP (and other abstraction mechanisms) to shorten methods e.g., extract some code blocks into separate methods. You may ignore this suggestion if you think a longer method is justified in a particular case.
/** * Create a instance of the deadline command. * * @param d ParsedData from the command input */
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)
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 [email protected] if you want to follow up on this post.
The text was updated successfully, but these errors were encountered:
@Eclipse-Dominator 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/duke/command/NoParamCommand.java
lines11-11
: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
Example from
src/test/java/duke/util/DataParserTest.java
lines53-53
:// new ParsedData(bye, "b", "c");
Suggestion: Remove dead code from the codebase.
Aspect: Method Length
Example from
src/main/java/duke/main/Duke.java
lines139-183
:Example from
src/test/java/duke/util/DataParserTest.java
lines51-106
:Suggestion: Consider applying SLAP (and other abstraction mechanisms) to shorten methods e.g., extract some code blocks into separate methods. You may ignore this suggestion if you think a longer method is justified in a particular case.
Aspect: Class size
No easy-to-detect issues 👍
Aspect: Header Comments
Example from
src/main/java/duke/command/AliasCommand.java
lines20-24
:Example from
src/main/java/duke/command/CommandSelector.java
lines73-77
:Example from
src/main/java/duke/command/DeleteAliasCommand.java
lines18-22
: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)
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
[email protected]
if you want to follow up on this post.The text was updated successfully, but these errors were encountered: