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
@jacobkwan 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.
publicstaticCommandparse(StringfullCommand) throwsDukeException {
fullCommand = fullCommand.strip();
String[] fullCommandArr = fullCommand.split(" ", 2);
StringcommandName = fullCommandArr[0].toUpperCase();
StringrestOfCommand = fullCommandArr.length > 1 ? fullCommandArr[1].strip() : "";
Stringdescription;
switch (commandName) {
case"TODO":
description = restOfCommand;
if (description.isBlank()) {
thrownewDukeException("Description cannot be empty.");
}
returnnewAddCommand(TaskType.TODO, description, null);
case"DEADLINE":
try {
intindex = restOfCommand.lastIndexOf("/by");
if (index == -1) {
thrownewDukeException("To add a deadline, please specify '/by dd/mm/yy'.");
}
description = restOfCommand.substring(0, index);
if (description.isBlank()) {
thrownewDukeException("Description cannot be empty.");
}
StringdeadlineString = restOfCommand.substring(index + 3).strip();
LocalDatedeadline =
LocalDate.parse(deadlineString, DateTimeFormatter.ofPattern("dd/MM/yy"));
returnnewAddCommand(TaskType.DEADLINE, description, deadline);
} catch (DateTimeParseExceptione) {
thrownewDukeException("To add a deadline, please specify '/by dd/mm/yy'.");
}
case"EVENT":
try {
intindex = restOfCommand.lastIndexOf("/at");
if (index == -1) {
thrownewDukeException("To add an event, please specify '/at dd/mm/yy'.");
}
description = restOfCommand.substring(0, index);
if (description.isBlank()) {
thrownewDukeException("Description cannot be empty.");
}
StringeventDateString = restOfCommand.substring(index + 3).strip();
LocalDateeventDate =
LocalDate.parse(eventDateString, DateTimeFormatter.ofPattern("dd/MM/yy"));
returnnewAddCommand(TaskType.EVENT, description, eventDate);
} catch (DateTimeParseExceptione) {
thrownewDukeException("To add an event, please specify '/at dd/mm/yy'.");
}
case"FIND":
Stringkeyword = restOfCommand;
if (keyword.isBlank()) {
thrownewDukeException("Keyword cannot be empty.");
}
returnnewFindCommand(keyword);
case"DELETE":
try {
intindex = Integer.valueOf(restOfCommand) - 1;
returnnewDeleteCommand(index);
} catch (NumberFormatExceptione) {
thrownewDukeException("Task ID supplied is not a number.");
}
case"MARK":
try {
intindex = Integer.valueOf(restOfCommand) - 1;
returnnewMarkCommand(index);
} catch (NumberFormatExceptione) {
thrownewDukeException("Task ID supplied is not a number.");
}
case"UNMARK":
try {
intindex = Integer.valueOf(restOfCommand) - 1;
returnnewUnmarkCommand(index);
} catch (NumberFormatExceptione) {
thrownewDukeException("Task ID supplied is not a number.");
}
case"LIST":
returnnewListCommand();
case"BYE":
returnnewExitCommand();
default:
thrownewDukeException("Invalid command!");
}
}
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.
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 👍
ℹ️ 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:
@jacobkwan 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/duke/ui/Ui.java
lines50-50
:// String indentedInput = input.replaceAll("(?m)^", "\t");
Example from
src/main/java/duke/ui/Ui.java
lines51-51
:// System.out.println("\t----------------------------------");
Example from
src/main/java/duke/ui/Ui.java
lines53-53
:// System.out.println(indentedInput);
Suggestion: Remove dead code from the codebase.
Aspect: Method Length
Example from
src/main/java/duke/Parser.java
lines28-113
: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/Duke.java
lines62-64
: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 👍
ℹ️ 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: