Congrats on 6.0.0 release! Was this deleted in err...
# kotest
s
was what deleted, that's a big PR 😉
n
Oh doesn’t it land on a line?
Image from iOS.jpg
s
it was removed because it's a duplicate of kotlin's own
error("foo")
I was surprised it was ever "public"
could add it back with a deprecation warning if needed
n
no that's fine! maybe just add it into the release notes or create a migration guide
I had to look in github to figure out what happened to io.kotest.data.*
also changelog has been broken for quite some time https://kotest.io/docs/changelog.html it's the first link of the first page
s
we started relying on "ai" changelogs lol
which was a mistake
I'll get that updated
n
haha. thanks!
👍🏻 1
s
any other feedback please let us know
n
not sure if it's worth considering but maybe running a binary compatibility checker would yield all the public api changes that later can be documented in the Breaking changes section. Openrewrite module for doing the migration will probably be a bigger ask but would be nice if the changes are too intrusive. I remember migration to io.kotest package was a massive change!
s
we do have an api checker
but it's used mostly to avoid accidental changes vs docs
kotest 6 was a big change because it was a major release version so we took the opportunity to "fix" or "improve" a lot of things
n
I am particularly thankful for the removal of AutoScan 😄 I had to disable it in every single one of our projects 😄
🎉 1
😂 1
k
I always regarded Kotest's
fail
and Kotlin's
error
functions as serving two different purposes. The former signifies a test assertion failure, while the latter signifies an illegal state (which would typically mean a logic error in the test itself).