@asdfghjkxd 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

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

No easy-to-detect issues 👍

Aspect: Method Length

No easy-to-detect issues 👍

Aspect: Class size

• src\test\java\juke\parsers\DateTimeParserTest.java (609 lines)

Suggestion: Consider breaking large classes into smaller ones, if appropriate. A long class is a sign that perhaps it is dong 'too much'.

Aspect: Header Comments

Example from src/main/java/juke/parsers/DateTimeParser.java lines 20-25:

    /**
     * Regex for recognising DateTime inputs. The regex pattern below are adapted from ChatGPT,
     * modified to better meet the requirements of Juke.
     * <p>
     * <a href="https://regex101.com/">This</a> was used to build and test the new regex patterns.
     */

Example from src/main/java/juke/parsers/DateTimeParser.java lines 29-34:

    /**
     * Regex for recognising Date inputs. The regex pattern below are adapted from ChatGPT,
     * modified to better meet the requirements of Juke.
     * <p>
     * <a href="https://regex101.com/">This</a> was used to build and test the new regex patterns.
     */

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 👍

❗ 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.

Issue: Bug report

Create a report to help us improve!

Describe the bug

Currently, when first launching the app, if the datafile and data folder are missing, the app will fail to initialise and throws an obscure error which states that the FXML files used for the GUI cannot be loaded.

To Reproduce

Steps to reproduce the behaviour:

• If the data folder or datafile is present, move it away to a separate location or rename the folder to something other than folder
• Run the app as per usual

Expected behavior

The app and GUI should be able to handle the missing datafile and recover from it by creating a new one.

Environment:

OS: MacOS Ventura 13.5.2
Java: Java openjdk 11.0.20

Additional context

None.

Issue: Bug report

Create a report to help us improve!

Describe the bug

Automatic line breaks done by counting characters are ugly and haphazardly break up words into different chunks on different lines, reducing user experience.

To Reproduce

Steps to reproduce the behaviour:

• Key in any long string without spaces
• Now, key in any long string with spaces
• Observe that the string may be haphazardly broken up across lines*

Environment:

• OS: MacOS Ventura 13.5.2
• Java: Java openjdk 11.0.20 Zulu Edition

Additional context

None.

@asdfghjkxd We did an automated analysis of your code to detect potential areas to improve the code quality. The script did not detect any issues in your code (nice!).

IMPORTANT: Note that the script looked for just a few easy-to-detect problems only 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

No easy-to-detect issues 👍

Aspect: Method Length

No easy-to-detect issues 👍

Aspect: Class size

No easy-to-detect issues 👍

Aspect: Header Comments

No easy-to-detect issues 👍

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 [email protected] if you want to follow up on this post.