Hey :slightly_smiling_face: For my library, I want...
# library-development
c
Hey 🙂 For my library, I want to ensure that I don't accidently introduce source compatiblity AND binary compatibility changes. I know that there is binary-compat-validator. But are there any rules on what constitutes a source compatibiltiy break? I am willing to invest some time into this, but I would love to have a definite answer which changes break API.
m
I asked a related question some time ago there. The tldr; is that it's not easy to add. If you're JVM only, japicmp has some source compatibility checks but of course doesn't know much about Kotlin. Once the recording goes out, I strongly recommend watching Kotlin Multiplatform Conversions at Android Jetpack Scale from @dustin and @James Ward. They're talking how metalava, the tool google uses to check compatibility, could maybe help there in the future