hakkangin / ped Goto Github PK

I'm sorry that I didn't take a screenshot for this. But previously there was one task displayed in the task list and I added a new contact called John Doe by this command "add n/John Doe p/98765432 e/[email protected] a/John street, block 123, #1-01" -- so John Doe appears as the 7 the contact.

At this point in time, there was only one task left in the meeting cards (I've accidentally checked the other one previously, you can refer to my issue #1)

But when I input the command "delete 7", the new contact John Doe gets deleted, but the remaining one task gets deleted as well(???). I'm not too sure why the task gets deleted along with the contact.

I accidentally clicked on the white box and the task disappeared straight away and I need to re-create one -- Could be a possible shortfall for the UX.

I tried adding a new task using the command "task add 1". I was expecting to see a new task in the task list but nothing is shown in the task list UI, except for a feedback message in the CLI. Was wondering if this is the intended behaviour?

I tried adding multiple tasks of the same title, the first task does not have a deadline, the second task has the same title as the first task and has a deadline, but the programme feedbacked that the same task already exists. This may be not so user-friendly in cases where the user wants to perform recurring tasks (i.e. weekly daily).

Also the new tasks are not displayed in the UI (as mentioned in one of my previous issues)

Ah okay... now it seems that I can view all the tasks previous created by using the "task list" command. Am thinking if the instructions can be made clearer in the user guide, or new tasks should be displayed in the UI straight away upon creation.

I think it will be good if the contacts can be sorted (or there's a command to sort) by alphabetical order of their names, otherwise it may get messy when the user wants to find the contact they are looking for.

e.g. If I want to create a task with Alex Yeoh and Alex Doe (and a few more people), and if the names aren't in alphabetical order, it might be a bit confusing to find the right people.

When I try to add two people with the same name, the error message "This person already exists in the address book" gets displayed. This happens despite the person I want to add lives at a different address, or has a different phone number or email. It can be potentially troublesome if the user wants to add contacts with the same first name and the user doesn't know the full names of the contacts (i.e. multiple ppl with the name, Alex, David, John etc.)

It would be good to consider date formats for tasks deadlines as well.

I am somewhat confused about how I can use the "task unmark" command -- Since all tasks are unmarked upon creation (by default) and a task disappears when marked, how can I unmark a task by its index if I cannot see it from the UI?

When I try to include country codes (i.e. +65) in new contacts' phone numbers, I will always receive the error message "Phone numbers should only contain numbers, and it should be at least 3 digits long". Might be a good corner case to consider.

When I input the command "task add GIAOoo by/tomorrow #haiz @4 @ 3 @5 @6" when there are only 5 people in the contact list, my command just disappears without any error message.

The message displayed in the CLI is still the feedback from my previous command "list tasks"

It seems like the task card UI is only displayed after the task is assigned to at least one person in the address book. Perhaps you guys might want to consider other cases where the user uses the address book as a "notepad" to record tasks only for themselves, or in cases where the user hasn't decided to who to assign a task. In these cases the UI cards for the tasks won't get displayed, will there be a better way around this?

When I try to edit a contact's tags, it seems like tag names consisting of multiple words cannot be accepted, but the corresponding feedback message "Tags names should be alphanumeric" can be rather ambiguous and slightly misleading for users.