Open JakeWharton opened 5 years ago
@JakeWharton are you open to contributions, or are you going to handle this yourself?
Contributions are fine, but I want to try to evolve the MPP API while keeping the Android one backwards/binary compatible.
So small, targeted PRs are a good start. For instance even just starting with a JVM artifact so we don't have to tweak anything with CI.
I was thinking of moving the core functionality to common Kotlin to start. Would that break ABI compatibility?
As a first step I would just put an empty Timber
and Tree
expect class into the common source set with empty actuals in the other platforms (maybe just JVM to start with) and the current class as an actual for Android.
@JakeWharton Do you have plans to support KMM? With the release of Compose for iOS, demand is expected to increase.
~Since we're only publishing SNAPSHOT this should be fine. And you can always fall back to the individual artifacts if your Gradle metadata version significantly skews.~
Tracking MPP version of Kotlin library.