ncduy0303 / pe Goto Github PK

Description

The User Guide specifies some commands with SLOT and some commands with TUTORIAL but I am not sure whether they are refers to the same entity in the real world.

It seems like they should be the same.

Reason for severity

Confusion and minor inconvenience for readers

Description

Trying to add a new person

Steps to reproduce

1. Launch the application for the first time to load initial data.
2. Run add n/La Niña 2 m/Computer Science y/2 e/[email protected] d/I’m a Frontend Developer t/06 t/19 sm/https://www.linkedin.com/in/john-doe-123456789 sm/https://www.linkedin.com/in/john-doe-123456789 nt/local g/m.

Expected behaviour

The person should be added successfully as this is sample valid input from the User Guide (same issue for name Élise DuPont)

Actual behaviour

An error is raised Names should only contain alphabetical characters and spaces, and it should not be blank. It should also not exceed 30 characters.

Reason for severity

Likely documentation issue (wrong valid inputs) since it is stated "Character Restrictions: Only alphabetical characters (A-Z, a-z) and spaces are allowed"

Description

Using group-related commands such as deleteGroup, findGroup, etc.

Expected behaviour

It should be short and not in capital-case

Actual behaviour

It is long and has a capital G which causes more time to type

Reason for severity

Small inconvenience for users

It is more likely that Person and Group is a container-contained relationship rather than whole-part, so it should be aggregation instead of composition.

Cosmetic issue due to typo. Should be [GROUP_NUMBER] instead of [GROUP_NUMBER} for leaveGroup and deleteGroup commands

Description

No validation for adding a student's from another tutorial group to a different group (of a different tutorial group)

Steps to reproduce

1. Launch the application for the first time to load initial data.
2. Run join gr/1 e/[email protected].

Expected behaviour

This should be blocked before the need to use checkGroup command

Actual behaviour

User can still add and there is no UI telling which students in the Group panel belongs to which Tutorial Group to check by eyes immediately

Reason for severity

Slight inconveinece for users

Description

There are some usages of the format [MORE_...] such as [MORE_SLOTS]... and [MORE_KEYWORDS] without explanation.

It is expected that it should simply be [SLOT]... and [KEYWORD]... as mentioned in the Notes at the start

Reason for severity

Cosmetic issue and confusion for readers due to inconsistent command format.

It is quite important to signal a multiplicity of 1 for those member fields of Person class.

Description

Names of the additional files for using the application

Expected behaviour

Expecting it to be similar to your application name.

Actual behaviour

Still refers to AB3 name

Reason for severity

Comestic issue.

Description

Try to edit and delete students in the application takes a lot of time

Reason for severity

It is a common use case and it cause slight inconvenience for a CLI user (especially when editting). Users need to type out the entire email of the student (why not skip the domain if everyone's email ends with @u.nus.edu)?

Description

Cannot click the 9. Listing All Tasks: tasks in the ToC to move the respective section

Reason for severity

Quite a cosmetic issue. Cause slight incovenience for reader.