Hey guys. I’m still looking for contributors :slig...

# opensource

[Marc Knaup]

Hey guys. I’m still looking for contributors 🙂 Anyone interested in pushing Kotlin libs forward?
• multiplatform GraphQL library
• multiplatform time library

[Miguel Hernández]

Hey @Marc Knaup I am interested 🙂

[Marc Knaup]

Hey @Miguel Hernández! Great 🙂 What topic are you interested in?

[Miguel Hernández]

Multiplatform time library sounds more interesting, but whatever needs more help it’s also fine 🙂

[Marc Knaup]

https://github.com/fluidsonic/fluid-time

This is what I currently have.
The idea is to stay close to the JVM 8 java.time API (which is good) but make it more Kotlin-like.
So far it’s focused on JVM and Darwin (iOS & macOS). Each implementation starts as a wrapper of the platform-specific date/time types and over time more and more functionality can be rewritten into common so that it’s consistent across platforms and can support more platforms.
The API is probably a bit verbose. It may make sense to get rid of the Nanosecond(s)/Milliscond(s)/Second(s)/etc. classes and to simplify. It should also integrate with Kotlin’s own Duration class and offer PreciseDuration as an alternative where floating-point values are not acceptable.

Let me know what you think about it 🙂

[Miguel Hernández]

Let’s work on it! Sounds amazing from my end 🙂

[Marc Knaup]

🙌 great :)

[Marc Knaup]

Do you have any current project where it would be useful to you?
I’ve used it in several projects so far (JVM & iOS) and always tweak and expand on-the-fly.
But I’d also love to set it up more properly (API, Unit Testing, documentation, etc.)

[Marc Knaup]

Given the release of kotlinx-datetime it makes sense to stop working on fluid-time and help migrating to the new library as it matures 😅