clement0010 / pe

Hello, I'm Clement 👋

I'm a Student !

• 🏫 I’m a Year 2 Computer Science Student at NUS.
• 🌱 Constantly looking for project based learning opportunity and internship opportunity.
• ❓ Area of interests: Fullstack Web Development, Machine Learning, Data Analytics and Algorithm.
• ⚡ Fun fact: I love to travel ✈ and go hiking 🌳.

Connect with me:

Languages and Tools:

---

pe's Issues

Resizing help column causes UI bug

To replicate:

1. Resize the help column Command Title to go beyond the window size (See screenshot below)
2. I am unable to resize back the column back to the original column width as the Help Window resizing feature is locked.

Outcome:

Expected:

1. There should be a horizontal scroll bar to handle the overflow
2. Alternatively, the Help Window resizing feature should not be locked to allow users to resize the column tab.

I think this is a severity.Medium bug as users might accidentally drag the column size to go beyond the Help Window size. Users need to restart the app in order to reset the size again and causes inconvenience to the user.

Default value for show rating is not specified

The default value for show rating is not mentioned anywhere else in the User Guide.

To replicate

1. Add a new show add n/All of us are dead s/plan-to-watch t/Horror c/Nice show
2. The rating value is shown as 0

Outcome

Expected

1. The user guide should mention to the reader the default rating value when inserting a new show.
2. This causes inconvenience to the user when the user wants to leave the rating blank/NIL instead of giving it a zero star rating.

Unclear usage for sorting sequence parameter

The usage of the parameter so/SEQUENCE is not elaborated clearly in the Sorting the shows sort section. There's no proper clarification on using so/SEQUENCE

Given that this parameter is part of the core functionality of sorting, most of the use cases elaboration is placed under the Notes section here:

It is not clear to the readers how to use the parameter so/SEQUENCE. Even after navigating to Parameter Conditions, there's no clear example given on how to use so/SEQUENCE.

The readers have to figure out the proper usage and examples of how to use the parameter so/SEQUENCE correctly.

Grammar error for import and export show

This should be importing shows rather than importing a show since we are technically importing multiple shows

Inaccurate result display when adding a new show

To replicate

1. Insert command add n/All of us are dead s/plan-to-watch t/Horror
2. The display response shows New show added: All of us are dead; Status: plan-to-watch; Rating: 0; Comment: ; Tags: [Horror];

Outcome

Expected

• The optional COMMENT, RATING field shows up in the result display when the user did not specify any of these values.
• This might cause confusion to users when unused parameters show up in the display result.

Multiple prefix name used in sorting sequence parameter

There is no clarification in the User Guide on the effect of using multiple prefix names in so/SEQUENCE. For example: using sort t/asc n/asc so/ratingtagname would still sort the tag and name in ascending order.

The only warning readers get is to use all prefix names in so/SEQUENCE as shown in the image below:

There's no elaboration on what would happen if we specify additional prefix names in so/SEQUENCE

Unclear instructions on the usage of parameter tables

There are two parameter tables shown in the User Guide:

1. Table after Command Structure
2. Table under Parameter Conditions

I find it difficult for the readers to differentiate the use of these two tables given the similarities of the first two columns and there is no description for Parameter Conditions to explain the purpose of the section. See diagram below:

It is only until the Adding a show: add feature that tells the reader about the usage of Parameter Conditions.

This causes minor inconvenience to beginner users in figuring out the use of both tables.

Inaccurate input validation when adding a new show

Replicate

1. Add a new show with add n/All of us are dead s/plan_to_watch t/Horror. New show gets added successfully.
2. plan_to_watch is clearly not part of the status list mentioned in the user guide

Outcome

Expected

1. While it is unlikely to cause major inconvenience to the user, it would be better to warn the user that the input is not part of the accepted format.
2. Alternatively, clarify in the user guide that other formats (replacing - with _) are acceptable.