You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We allow the user to enter freeform text for start time of a court hearing
There is no indication of what's a valid time in the hint, but we do provide examples when a validation error occurs.
The example shown 12:00 has led some users to enter strings such as 2:00. While the input is valid, it results in the start time being recorded as 2am. This is probably not what the user intends.
We should should probably:
stop accepting 24hr XX:XX as an allowable input format
show something like this as an example for example: 10am or 2.30pm
Alternatively we could spot and query the user when an ambiguous[0] time is entered
We allow the user to enter freeform text for start time of a court hearing
There is no indication of what's a valid time in the hint, but we do provide examples when a validation error occurs.
The example shown
12:00
has led some users to enter strings such as2:00
. While the input is valid, it results in the start time being recorded as2am
. This is probably not what the user intends.We should should probably:
for example: 10am or 2.30pm
Alternatively we could spot and query the user when an ambiguous[0] time is entered
[0] Currently we have the following behaviour
2pm -> 2pm
2:00 -> 2am
2 -> ?? -> Invalid
14:00 -> 2pm
14 -> 2pm
NB. a simple number is fine is greater than or equal to 10, but ambiguous if less than 10.
The text was updated successfully, but these errors were encountered: