Previous/next date and/or time with the given form

[dkhalanskyjb]

"I have a date or a time, and I want to round/adjust it."

Examples:

• Find the last time it was Monday (or Sunday) not later than the given date: Allow getting the week number of a LocalDate and a LocalDateTime #129 (comment)
• Given the local time, find the 1-hour slot it matches (13:45:12.513 -> 13:00:00.000): set hours of LocalDateTime #223 (comment)
• Discard the sub-minute components when formatting a Duration: Feature Request: truncateTo for LocalTime #225 (comment) (can also be solved by tweaking the formatter).
• Find the next time a given day of the week happens: Add an equivalent of TemporalAdjusters #235 (comment)
• Internally, we need functions like "find the last Sunday in the given month" to calculate the moments when timezone transitions happen.

[volkert-fastned]

One practical use case for such functionality: the OCPP specification. It mandates that ISO date/time strings don't have more than 3 decimal points:

number of decimal places SHALL NOT exceed the maximum of 3.

In other words: no more than millisecond precision.

While working with kotlinx-datetime, we actually ran into compatibility problems with vendors that will flat out reject the nanosecond-precise ISO date/time strings that kotlinx.datetime.Instant gets serialized to by kotlinx.serialization.

We could use JSR-310 (java.time) instead, so we could solve it with truncateTo, or we can write a helper function as suggested on StackOverflow, but I was kind of hoping that there would be an equally convenient built-in multiplatform solution for this.

[volkert-fastned]

Update:

I found a single-line workaround for forcibly reducing the precision to millisecond-level in serialized ISO date/time strings, at least for timestamps originating from the system clock:

import kotlinx.datetime.Clock
import kotlinx.datetime.Instant

// Will have 6 digits behind the decimal point on Kotlin/JVM, but 3 digits on Kotlin/JS and Kotlin/Native
println(Clock.System.now())

// Will have 3 digits behind the decimal point on Kotlin/JVM, Kotlin/JS and Kotlin/Native
println(Instant.fromEpochMilliseconds(Clock.System.now().toEpochMilliseconds()))

So Kotlin/JVM appears to appears to be the only Kotlin platform that creates Instants from the system clock at nanosecond precision, although I haven't tried it with Kotlin for Android yet.

[dkhalanskyjb]

@volkert-fastned, since your problem is with system interoperability, the upcoming API for parsing and formatting may solve it: #343