Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kotlin MPP #338

Open
JakeWharton opened this issue Oct 15, 2018 · 5 comments
Open

Kotlin MPP #338

JakeWharton opened this issue Oct 15, 2018 · 5 comments

Comments

@JakeWharton
Copy link
Owner

JakeWharton commented Oct 15, 2018

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.

@eygraber
Copy link
Contributor

@JakeWharton are you open to contributions, or are you going to handle this yourself?

@JakeWharton
Copy link
Owner Author

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.

@eygraber
Copy link
Contributor

I was thinking of moving the core functionality to common Kotlin to start. Would that break ABI compatibility?

@JakeWharton
Copy link
Owner Author

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.

@sonatard
Copy link

@JakeWharton Do you have plans to support KMM? With the release of Compose for iOS, demand is expected to increase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants