khiaxeng / ped Goto Github PK

Original state:

When deleting via tags with lower case, eg: 'delete -t friend' , all persons with the tag (case insensitive) gets deleted:

When removing tags with lower case, eg: 'edit --remove -t friend' , only the person with lower case tag has the tag removed: (Alex's tag is not removed in this case)

This behavior

for eedit : when TAB is pressed after an incorrect event index is provided:

when TAB is pressed after typing eedit 0 -n

Perhaps the first error message can be used in the case of the second error message.

The meaning of curly brackets { } is not explained in the UG, was not sure what the curly brackets meant. (Maybe I missed it)

Perhaps you can specify in the UG that at least one of the square bracket parameters must be included in eedit . Since square bracket parameters are optional, people may misunderstand and type eedit 1 for example.

Maybe rename the title of the Features section in the UG to reflect the content of the section.

I understand there are many things to note about the list command but upon first glance I was slightly lost, maybe start with the examples first..?

When birthday is an invalid date but correct format, displays this error:

Maybe have the error point out invalid date instead of stating that the date should not be a date in the future.

When date format is wrong, the error message relates to "Birthday should not be a date in the future" instead of addressing the incorrect birthday format.

Original state :

As specified in the UG:
delete -t colleague -t cs2103 deletes contacts that contain both tag “colleague” and “cs2103”.

Executing "delete -t Friend -t friend" will delete Barbara and Charles, even though they only have one tag.

[-n NAME] should contain alphanumeric and spaces only but is allowed in list command:

The Notes section under Features specifies a command 'clear' but it does not exist

Could include u under -s part of elist documentation

No details provided.

At the underlined part of the screenshot: square bracket instead of curly braces?

A invalid date with year is specified : "eadd -n Party -d 32 Jan 2021" , but the error message does not match the error since the year is specified:

In the UG this is specified:

When sorting birthdays by ascending order:

Birthday with year 1991 comes before birthday with year 1990.

This may be intended and I may have misunderstood from the UG. If so, perhaps you can rephrase the part in the UG that says :
b , birthday: day of the year of the birthday