Hi everyone, I'm new to Kotest (from a contributor...
# kotest-contributors
r
Hi everyone, I'm new to Kotest (from a contributor perspective) but would like to participate. I found this bug marked as good-first-issue: https://github.com/kotest/kotest/issues/2668 Additionally, KAML is now multiplatform ready: https://github.com/charleskorn/kaml/issues/232#issuecomment-2027350448 Therefore, I thought it might be a good start for me. What do you think?
👍 1
🏆 1
a
go for it, and good luck!
👍 1
r
As far as I can see KAML doesn't support these targets:
Copy code
tvosX64()
      tvosArm64()
      tvosSimulatorArm64()

      watchosArm32()
      watchosArm64()
      watchosX64()
      watchosSimulatorArm64()
which are part of the
kotlin-native-conventions
. Should I then limit the module to the jvm and js conventions? Or would it be okay if I directly declare the targets in the build.gradle.kts?
a
how about starting small, JVM only, and expanding later
r
Sounds good to me. I was just thinking, since most of the targets are supported, I'd go multiplatform right from the start.
Hi everyone, I have another question. As far as I can see the minimum JDK target for Kotest is Java 8. Now, SnakeYaml KMP has set Java 11 as target. Can I set a different JDK version for the new submodule? I cannot find an example where that has been done for another module.
Seems like I'm not the only one tracking this down 😄 https://github.com/ethauvin/urlencoder/issues/18 I'll see if I can pick up where my predecessors left and make the urlencoder Java 8 compatible
e
I wonder if it's not time to move baseline to at least java 11 soon.. Spring recently announced Spring Framework 7.0 would move to JDK17 baseline, arguing that a lot of other JVM projects seems to have already done so.
a
our greenfield projects are on 21
r
Well, I'm just the newbie here, but I was honestly surprised that you still support Java 8 😅 Nevertheless, checking here https://en.wikipedia.org/wiki/Java_version_history it's still being supported by some Java versions