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 frequently need to generate a string representation of a time of day in Good Eggs code.
We have a documented standard for the format to use for manipulating and storing such a string: HH:mm. This is e.g. 14:00.
However, we also frequently have a need to generate user-facing time of day string representations, which would usually be a different format, such as 2pm, 2:00 pm, or 2:00:00 pm. Since we do not have a standard for such a format (appropriately so, I think – this is a design concern, and we have disparate types of audiences... customers, employees, engineers, etc.), it seems difficult to design a convenient, expressive method for this that would not introduce bugs.
I'm not sure on this one. I would propose we start with just adding fake.timeOfDay() which generates our standard documented HH:mm format.
The text was updated successfully, but these errors were encountered:
We frequently need to generate a string representation of a time of day in Good Eggs code.
We have a documented standard for the format to use for manipulating and storing such a string:
HH:mm
. This is e.g.14:00
.However, we also frequently have a need to generate user-facing time of day string representations, which would usually be a different format, such as
2pm
,2:00 pm
, or2:00:00 pm
. Since we do not have a standard for such a format (appropriately so, I think – this is a design concern, and we have disparate types of audiences... customers, employees, engineers, etc.), it seems difficult to design a convenient, expressive method for this that would not introduce bugs.I'm not sure on this one. I would propose we start with just adding
fake.timeOfDay()
which generates our standard documentedHH:mm
format.The text was updated successfully, but these errors were encountered: