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
@remuslum 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.
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)
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.
/** * Iteration 1: * Creates a label with the specified text and adds it to the dialog container. * @param text String containing text to add * @return a label with the specified text that has word wrap enabled. */
/** * At the end of the session, the textfile is properly updated. * @param taskList the final task list before ending the session * @param filePath the path of the updated textfile * @throws DukeException if the filepath is incorrectly inputted */
Suggestion: Ensure method/class header comments follow the format specified in the coding standard, in particular, the phrasing of the overview statement.
Code currently violates several coding quality standards
This affects the readability of the code and cause possible confusion.
As such, thw code has been modified such that class names, variables names all provide meanings and if-else statements are modified such that the main body is obvious to the reader.
No blank line between subject and body
body not wrapped at 72 characters: e.g., As such, thw code has been modified such that class names, variables names all provide meanings and if-else statements are modified such that the main body is obvious to the reader.
ℹ️ 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:
@remuslum 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
Example from
src/main/java/duke/task/Task.java
lines9-9
: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
Example from
src/main/java/duke/Parser.java
lines122-123
:} else {
Example from
src/main/java/duke/command/FindCommand.java
lines35-36
:} else {
Example from
src/main/java/duke/command/MarkCommand.java
lines30-31
:} else {
Suggestion: As specified by the coding standard, use egyptian style braces.
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
Example from
src/main/java/duke/Duke.java
lines91-145
:Example from
src/main/java/duke/Parser.java
lines22-126
: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
lines147-152
:Example from
src/main/java/duke/Duke.java
lines176-179
:Example from
src/main/java/duke/Storage.java
lines43-48
: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
possible problems in commit
ed87d1b
:As such, thw code has been modified such that class names, variables names all provide meanings and if-else statements are modified such that the main body is obvious to the reader.
possible problems in commit
7f1b638
:possible problems in commit
72ea5d1
: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 👍
ℹ️ 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: