- πΏπ¦South Africa rudolfbyker South Africa
+1 (even though the issue description is not very clear)
There is a big difference between "time" (as in: time elapsed since an arbitrary starting point, e.g. the start of a video) and "the time" (as in: the time of day).
The latter is a more specific case of the former:
- It is the time elapsed since midnight.
- It is expressed in a specific way, e.g., in 12h format with AM/PM, or in 24h format.
- It can't be more than 86400 seconds.
The former is a more general case of the latter:
- It is the time elapsed since ANY starting point.
- It can be expressed in more different ways (where 12h format or 24h is not necessarily applicable, or does not necessarily make sense).
- It can be more than 86400 seconds.
This module is very close to catering for the more general use case, but not quite. Here are some blockers:
- Numbers 0 and 86401 should not get special treatment. See https://www.drupal.org/project/time_field/issues/3463912 π The integer 86401 should not be used to represent an "empty" time element Active
- We need a way to format the time like 69:34:23 for 69 hours, 34 minutes and 23 seconds into a video.
Also nice to have:
- For time ranges, it should be supported to set only a start time, only an end time, or both.
- Support for higher time resolutions: In this case, the field could be configured to store milliseconds or microseconds instead of seconds in the database. In these cases, a larger int type might be necessary.
- π§πͺBelgium BramDriesen Belgium π§πͺ
I guess some of this can be broken down into separate issues?
- πΏπ¦South Africa rudolfbyker South Africa
I guess some of this can be broken down into separate issues?
Of course. :) As you are the maintainer, I think you will know best how to subdivide the work. The bullet points in my previous comment are just my suggestions for how to subdivide the work.