This message was deleted.

Before I go implementing it, are there any kotlin.js wrappers for github actions sdk out there?

I just got hit by

Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.16

and I'm wondering how safe it is to compile libs with Kotlin 1.5 if you expect consumers to use 1.3 or 1.4 for some reason. I was under the impression that it would work but this message seems to indicate otherwise. There are a few stack overflow github issue and everytime the solution seems to bump the Kotlin version in the consumer project, which might not always be possible easily. Has anyone more details about how safe it is?

👋 Hello everyone, JetBrains would like to better understand the experiences of those who author Kotlin libraries. If you’ve ever developed one and you’d like to tell us about it, please fill out this form and we’ll get back to you to learn more. Thank you and have a nice day!

I see libs prefixing their

alpha

versions with

"0"

but not doing it for their releases: •

3.2.1

•

3.3.0-alpha01

Is there a reason for this? If I read https://docs.gradle.org/current/userguide/single_versions.html#version_ordering correctly, it will also work without the leading

"0"

, Gradle should consider

alpha10 > alpha2

in all cases ?

I would like some advice. We developed some large libraries that we use for internal development - essentially a framework - at my current workplace. They're all open source, but we haven't really put a ton of effort into advertising them, and they need some more polish for public use. I'm one of the few who maintains the package, and I'm concerned that their lack of common use is going to cause great problems in the future. In this case, the library is a set of Kotlin compiler plugins that transpile Android Kotlin apps to human-readable Swift and Typescript apps due to our need to use each platform's native language as per client request. We have this working, and it is currently running several projects in production. This goes in combination with a set of libraries (including UI, network requests, etc) for app development that work across all of the languages, using Rx as a backbone because it exists across all the languages in question. Is anyone interested in this? Should I find a way to get our company to maintain it more, or should I get our company to abandon it? (At the moment, my boss has the libraries GPL'd with a separate license for commercial usage. I want to get it changed to something totally open like Apache, and I think I can convince him if we want to continue maintaining.) In addition, what have you guys found works for advertising a library? What helps keep a library nice?

Hi everyone! We would like to improve the experience of Kotlin library authors, and now are conducting research to decide which areas to prioritize. If you’ve worked on your own library or plan to create one, please share your feedback with us by taking this survey: https://surveys.jetbrains.com/s3/sl-kotlin-libraries-authors-survey

By the way, one of the questions, covered in the survey is the discoverability. Let me remind you about very nice tool https://kotlin.link/ by @irus

Jitpack allows to republish for 7 days, ideal to publish malware… Please, folks, use MavenCentral until we get something simpler to setup that still is serious about security.

Hi guys 👋 what is the expected difference between alpha / beta? Are APIs expected to not change after beta or can they still change? Where can I find good resources about versioning of Android/Kotlin libraries? Thanks in advance!

I want to build a library using Kotlin 1.6 but make sure that it’s still usable by consumers who are using Kotlin 1.3. (I know it’s deprecated, but I have some of those consumers still.) I’ve found some info in the Kotlin documentation, Stack Overflow, etc., but I’m still not certain, so I hope some of the great minds here can confirm or deny my suspicions. If I set

apiVersion = "1.3"

and force my tests to use a

1.3.n

version of

kotlin-stdlib-jdk

, that should both set and validate that my library will work for consumers using Kotlin 1.3, right? (The relevant excerpts from my

build.gradle

file are in the thread so I don’t spam the channel with a wall of build script.)

How bad is it to use

@OptIn(ExperimentalContracts::class)

in a library? Looks like

contracts {}

blocks do not generate any bytecode (besides metadata?) so as long as it's only used internally it should be fine?

Imagine you have a Compose library that is in beta and you want to start releasing two artifacts per version: one that also uses beta Compose dependencies and another that uses stable Compose dependencies internally. How would you name the two artifacts versions? I was using something like

0.9.0-beta

but now the idea would be something like (just to convey the point, not that I’d call them that, I guess?)

0.9.1-beta-stable

and

0.9.1-beta-beta

.

Hey everyone 👋 While working at different places on different projects its always been interesting how developers choose to go about creating models for unit tests. I've seen some projects redundantly create new models for each and every test, and some projects create factories, with static models that they then use everywhere. Long story short, at work we wanted to clean up some of these tests so two of us started working on a library that would automat this for us and generate random models with actual data. The fruits of our labor can be found below 🤓 We have been using it in production for about 6 months now 🚀 We would be eternally grateful for any feedback you might have 🙏 and to see wether it potentially fits your use cases as well. Please take a look, try it out and let us know what you think 🙌 Collaboration welcome 👩‍💻 👨‍💻 https://github.com/HelloCuriosity/model-forge

When a function takes a

Closeable

as a parameter, is there a nice way to indicate whether the function actually closes the

Closeable

or if it's the caller responsibility? Ideally looking at the signature only?

Are there any plans to add source compatibility checks to https://github.com/Kotlin/binary-compatibility-validator ? As of now it's super easy to change a parameter name and not notice it until calling code breaks

I’m trying to figure out whether Kotlin 1.6 brings any new binary incompatibility with older language versions. In other words, if a project moves to Kotlin 1.6 and it has library dependencies that are some older 1.X version, could it break (more than if it used Kotlin 1.5)? I found the following in the 1.6 release notes, but I’m not sure if this means source compat, binary compat, all of the above, or something else entirely.

Starting with Kotlin 1.6.0, we will support development for three previous API versions instead of two, along with the current stable one. Currently, we support versions 1.3, 1.4, 1.5, and 1.6.

Is creating new objects for received requests a discouraged practice?

Hi, I hope this is the right channel to ask this: I am building a sdk for use by our customers. They will embed the sdk in their apps. The sdk takes a picture and then sends to our backend for analysis and returns a result. My questions are: 1. best way to hand control to the sdk. I am currently having the host app start an activity. Other options are StartActivityForResult and the new version of it. Another is a global singleton object initialised by the host and methods called on it. 2. how to distribute the sdk without supplying source code?

Hey all, I hope this is the right place for this, but I'm curious if anyone has written a library like this for Kotlin. If not, I might try my hand at porting it at some point. I'd love to have something like this at work (where we use several DSLs written in Kotlin). https://github.com/zesterer/ariadne

Does anyone have an example of how they incorporate the binary compatibility validator plugin in a CI workflow? I get how to run it, but I'm not sure when it should be run. Pre-release? Every build? Something else? What has worked for you?

Hey guys, I am learning library development. So I completed the mavenLocal chapter. Now I want to publish library in github packages with private repository . So now I tried some piece of code but it's not working and I cannot understand, so someone guide me. I am adding my build.gradle.kts in thread.

Hey I tried to use

./gradlew publish

I am getting error. My build.gradle.kts. I am getting error on this

* What went wrong:
Execution failed for task ':publishKotlinMultiplatformPublicationToKotlinMultiplatfromProjectRepository'.
> Failed to publish publication 'kotlinMultiplatform' to repository 'KotlinMultiplatfromProject'
   > Could not PUT '<https://maven.pkg.github.com/vivek-modi/KotlinMultiplatfromProject/me/vmodi/KotlinMultiplatfromProject-kotlinMultiplatform/1.0.0/KotlinMultiplatfromProject-kotlinMultiplatform-1.0.0.jar>'. Received status code 422 from server: Unprocessable Entity

What's everyone planning to do with 1.7 around the corner? 1️⃣ Upgrade my lib asap, moving the ecosystem faster 🚀 2️⃣ Wait a bit for consumers to update first so that they have less compatibility issues 🧘

Hey guys, I am experiencing a big delay on for the new published artifact to be available in maven central. I usually see it there after like 30min - 1hour. This time I left it over night and it is still not there. Have you guys ever experienced this? Is there something I can do? Btw this is where I usually check if it is available: (I was hoping to see 1.5.8-beta) https://repo1.maven.org/maven2/io/github/raamcosta/compose-destinations/core/

Is the kotlin libs publisher plugin still maintained? I want to use it in my project but it doesn't support sonatype s01. https://github.com/Kotlin/kotlin-libs-publisher

Hey how do you all, protect against Binary Compatibility issues in your libs. Let's say your working with DataClasses in a library module which is a known culprit of this . But you know that data class may grow in properties over time, what would be the best course of action to prevent binary compatibility?

I'm not sure if this goes here, but whenever I try and publish a multiplatform library, gradle fails at the task

:generateMetadataFileForKotlinMultiplatformPublication

with the error

Invalid publication "kotlinMultiplatform"

while using the

maven-publish

plugin. Is this something that there's a fix for or should I be doing something else to publish my library?

What warning do you have to suppress to still use a deprecated symbol with level

HIDDEN

? for

WARNING

and

ERROR

you can do this:

@Deprecated("w", level = DeprecationLevel.WARNING)
val w = "w"

@Deprecated("e", level = DeprecationLevel.ERROR)
val e = "e"

@Deprecated("h", level = DeprecationLevel.HIDDEN)
val h = "h"

println(@Suppress("DEPRECATION") w)
println(@Suppress("DEPRECATION_ERROR") e)
println(@Suppress("?? what goes here ??") h)