Replies: 2 comments
-
|
I'm fine building on a pre-alpha, the old libraries have become painful. We'll just have to be careful not releasing (or only releasing a |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This has been addressed via #156. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Krayon is currently stuck on an older Kotlin version (1.6.10 at the time of this writing) because of compose-jb.
This may become troublesome for consumers, as libraries such as kotlinx.datetime have specific Kotlin version compatibility. For example, starting with Kotlin 1.7.0, kotlinx.datetime 0.3.3+ is required. If there are breaking API changes in upcoming kotlinx.datetime releases, then Krayon could cause runtime issues for people if they are using a newer (incompatible) kotlinx.datetime to that which Krayon is compiled against.
In order to use Kotlin 1.7.0, Krayon would need to switch to using pre-alpha (snapshot) builds of compose-jb, such as mentioned in JetBrains/compose-multiplatform#2108 (comment).
1 vote ·
Beta Was this translation helpful? Give feedback.
All reactions