Would appreciate any feedback on <https://github.c...

# kotest

[sam]

Would appreciate any feedback on https://github.com/kotest/kotest/issues/2065

[wasyl]

I personally dislike 2., mostly because it’d introduce overhead when configuring just one test

[wasyl]

How about two variants: .config(timeout = …, enabled = …) and also .config(config: TestConfigBuilder.() -> Unit so that the first one can delegate to the second one

[wasyl]

And then you can share configs by doing val config: TestConfigBuilder.() -> Unit = configBuilder { … }

[wasyl]

I guess I’m mostly advocating for the current postfix function-style. But be aware I don’t use configs often so I might biased.

The last version rubs me the wrong way somehow. Something about adding a global method that’s not spec-specific.

[sam]

I think your idea of having the original version delegate to the builder version could work well.