9temare/ped

ped's Issues

Mismatch of command specified in UG and actuall application

It is obvious that the example command contradicts the actual command: r/ and rd/.

The simple fix would be to update the UG example commands accordingly, but even so, there lacks coherence between commands that are related to dates. More of this in a separate issue.

Phrasing of word in UG find command

As shown in the screenshot, I was confused when I saw "OR search", no glossary is provided for such a term in UG, I do not know what it means until I Google.

Possible fix: rephrase, or include "OR search" into the glossary.

Command keywords are different for the same Date attribute

Even though all these highlighted commands deal with the same DATE attribute, the command keywords are actually different (r/ and rd/), resulting in huge confusion for the user.

Language used in date presentation is defaulted to the user's computer language

As shown in the screenshot, my computer's default language is Chinese, therefore AIA presents "month" in Chinese as "月". This bug reduces the coherence of AIA since the app should present all text in English as intended.

Possible fix: Inside SimpleDateFormat, there is another parameter called Locale. You may want to set it to Local.ENGLISH.

Mismatch of DG and ResultDisplay description regarding the `within` command

Days can actually be 0, make sure to update UG accordingly.

If a tag does not include any person, it seems that the tag is automatically "deleted"

As the title suggested, if a tag is not being tagged to any person, it disappears when the user is trying to list all tags with the tags command.

This might not be the desired outcome since the user might simply want to see all the tags he/she has, instead of seeing what are the tags that are not empty. The user might falsely think that he/she forgot or did not add the tag last time, instead of knowing that he/she is actually "done" with everyone under the tag.

Mismatch of DG and ResultDisplay description regarding the `after` command

Same issue as the within issue.

Please update UG accordingly.

Regarding the birthday attribute when adding a new person

I personally do not think making the birthday attribute compulsory is a good idea, this does not tackle/seems unrelated to the problem AIA is intended to solve.

I do understand that sometimes insurance assistants need to "be friendly" and "be active", but it might be unlikely and inappropriate that the user knows or ask for the birthday information of the potential client the first time they meet.

This issue is just FYI, do ignore this if you can justify it reasonably.