Add configurable units for duration and time ago formatting

[barq-al-layl]

It would be useful to let callers choose the unit used by HumanReadable.duration() and HumanReadable.timeAgo() instead of always auto-scaling to the largest readable unit.

Example use cases:

HumanReadable.duration(3.days, unit = DurationUnit.Hours) // "72 hours"
HumanReadable.timeAgo(instant, unit = DurationUnit.Days) // "32 days ago"

This would help when apps need consistent units in reports or UI labels where automatic unit switching can be confusing.

[janexner]

Agreed.

For me, the use case is that I want to display when an expense has been created with a precision of DAY, so if I create one now, I would like the library to return "today" rather than "14 hours ago" (It's 14:12 here right now, and I create those with just the date, which means they are stored as 23.6.26 00:00)

[jacobras]

Thanks for these requests. I'm working on a version 2.0 release that'll incorporate both these features. I'll share a draft API soon for review.

[jacobras]

With version 2.0.0:

@barq-al-layl

HumanReadable.duration(3.days, units = setOf(TimeUnit.Hours) // "72 hours"
HumanReadable.timeAgo(now - 32.days, units = setOf(TimeUnit.Days)) // 32 days ago

and @janexner

val today = LocalDate.parse("2026-07-02")

HumanReadable.timeAgo(today.minus(1, DateTimeUnit.DAY)) // "yesterday"
HumanReadable.timeAgo(today) // "today
HumanReadable.timeAgo(today.plus(1, DateTimeUnit.DAY)) // "tomorrow"

See #197 for more info and a live demo