A span of time, given in milliseconds, in the unit a reader counts it in.
Whole weeks read as weeks ("2 weeks"). Anything else reads in the coarsest
of days, hours, minutes and seconds it lasts at least one of, rounded as
every other number is ("1 day", "1.5 days", "6 hours"), and a span shorter
than a second in seconds. That is the rule the ApexCharts adapter picks a
datetime schedule's unit by, with weeks where they come out whole: ten days
read "10 days" rather than "1.43 weeks".
There is no plural engine, so the count chooses between two messages, the
one for a count that reads exactly "1" and the one for any other.
The unit is chosen on the count without its float noise, as the count is
read: a day a hair short from the subtraction of two timestamps is one day,
not 24 hours. A span taken from edges listed high first comes out negative
and is the same span, so it reads its size. One that is not a number reads
as missing, as an extent with no ends does.
A span of time, given in milliseconds, in the unit a reader counts it in.
Whole weeks read as weeks ("2 weeks"). Anything else reads in the coarsest of days, hours, minutes and seconds it lasts at least one of, rounded as every other number is ("1 day", "1.5 days", "6 hours"), and a span shorter than a second in seconds. That is the rule the ApexCharts adapter picks a datetime schedule's unit by, with weeks where they come out whole: ten days read "10 days" rather than "1.43 weeks".
There is no plural engine, so the count chooses between two messages, the one for a count that reads exactly "1" and the one for any other.
The unit is chosen on the count without its float noise, as the count is read: a day a hair short from the subtraction of two timestamps is one day, not 24 hours. A span taken from edges listed high first comes out negative and is the same span, so it reads its size. One that is not a number reads as missing, as an extent with no ends does.