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
Convert toLocalTime uses Java's LocalTime instead of Kotlinx's.
We should use kotlinx.datetime.LocalTime instead of java.time.LocalTime if we ever want to go multiplatform and just for general consistency.
parse uses even more java.time versions: LocalDate, LocalDateTime, LocalTime,
as well as java.time.format.DateTimeFormatter, but I'm not sure if that can be replaced.
The text was updated successfully, but these errors were encountered:
Jolanrensen
changed the title
Convert toLocalTime uses Java's LocalTime instead of Kotlinx's
Usage of Java's LocalTime instead of Kotlinx's
Feb 13, 2024
It’s hard for me to say now why java.time is used in parser
I assume that back then kotlinx-datetime was more limited in its capabilities
And so it is necessary to save java.time in the public api, since often use it anyway, but have a similar api for kotlinx-datetime. As for internal things, yea, it would be nice to have kotlinx-datetime
Convert
toLocalTime
uses Java'sLocalTime
instead of Kotlinx's.We should use
kotlinx.datetime.LocalTime
instead ofjava.time.LocalTime
if we ever want to go multiplatform and just for general consistency.parse
uses even morejava.time
versions:LocalDate
,LocalDateTime
,LocalTime
,as well as
java.time.format.DateTimeFormatter
, but I'm not sure if that can be replaced.The text was updated successfully, but these errors were encountered: