Emil Kantis

@myuwono @sksamuel I think the correct thing to do would be to add a wrapper around the [edgecase function's](https://github.com/kotest/kotest/blob/19ce4d3b4712ed04c23d9aad7ce56c064caaa503/kotest-property/src/commonMain/kotlin/io/kotest/property/Gen.kt#L103) result. E.g. it should return either `Edgecase?` or simply a `Sample?`.That...

Could you please ensure that the failure message is tested as well? E.g. ```kotlin shouldFail { Throwable() shouldHaveStackTraceContaining "foobar" }.message shouldBe """ exact message here """ ```

Also, exceptions spell it as "stackTrace", so IMO we should also capitalize the T.

Won't using Java 21 classes require us to use jvmTarget = 21? Basically meaning that anyone that uses Kotest needs to use Java 21?

You can define `kotest.properties` (details [here](https://kotest.io/docs/intellij/intellij-properties.html)) with the following content: ``` kotest.framework.classpath.scanning.config.disable=true kotest.framework.classpath.scanning.autoscan.disable=true kotest.framework.config.fqn=com.myproject.KotestConfig ``` Where `com.myproject.KotestConfig` is ```kotlin object KotestConfig : AbstractProjectConfig() { override fun extensions() = listOf( PrepareSpecTestListener()...

@dondod sorry for taking so long.. It's because the [SpringAutowireConstructorExtensions](https://github.com/kotest/kotest-extensions-spring/blob/master/src/main/kotlin/io/kotest/extensions/spring/SpringAutowireConstructorExtension.kt) from kotest-extensions-spring relies on `@AutoScan` to be discovered. When you disable scanning, you need to also register this extension manually...

Feel free to post a small example repo 🙂

I feel it's kind of ambiguous what we're looking at in the failure messages. Was it the wrong key or value? Perhaps we should produce a similarity-score for each Map.Entry...

I re-opened the discussions feature and added a category for 6.0.. https://github.com/kotest/kotest/discussions/categories/6-0-changes I think the discussions will be easier to follow/participate in if it's 1 thread per change.. what do...

WDYT about just making this always enabled? I'm having a hard time seeing in what scenario someone might want to both define private `Spec`s _and_ disable this setting