Open shawnnlimm opened 5 months ago
This is a fair point, and there was a tradeoff between an excessively long UG (there are three permutations: AM-AM, AM-PM, PM-PM) and a shorter, but more intuitive UG. We chose the latter option because we hoped that it was intuitive enough that scheduling morning-only or afternoon-only appointments is possible.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Description
According to the UG, it seems that the
d/DATE_TIME
format only accepts[x]am-[y]pm
, implying that an appointment can only start in the morning and end in the afternoon/evening. However, doing[x]pm-[y]pm]
also works in the app.Steps to reproduce
Expected Behaviour
UG should be clearer on the
d/DATE_TIME
formatActual Behaviour
Missing details regarding
d/DATE_TIME
formatLabel elaboration
Severity: VeryLow, since it's unlikely to affect usage
BugType: DocumentationBug