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
Right now we use kotlinx-datetime as multiplatform solution.
However, sometimes it make sense to use other DateTime provider.
Possible Solution
We have to extract any work with LocalDateTime into injected abstract DateTimeProvider.
We also must extract the functionality without the kotlinx-datetime library into kcron-common-core library.
As default implementation we must keep kcron-common package which will use kotlinx-datetime as DateTime implementation.
The text was updated successfully, but these errors were encountered:
After some investigation, I found that there is no better KMP date-time library than kotlinx-datetime.
So, maybe add the possibility to use different date-time provider is good but it should not reduce the current platforms amount.
Hi, in my case I would use your dependency in a JVM context, but without an other dependency like kotlinx-datetime as DateTime implementation. The JDK give already the java.time and I prefer to avoid to multiply dependency to do the same things.
General Information
Right now we use kotlinx-datetime as multiplatform solution.
However, sometimes it make sense to use other DateTime provider.
Possible Solution
We have to extract any work with LocalDateTime into injected abstract DateTimeProvider.
We also must extract the functionality without the kotlinx-datetime library into
kcron-common-core
library.As default implementation we must keep
kcron-common
package which will use kotlinx-datetime as DateTime implementation.The text was updated successfully, but these errors were encountered: