How do we feel about ditching autoscan completely?...
# kotest-contributors
s
How do we feel about ditching autoscan completely? I'm working on a PR to disable it, but I can't see why anyone would want to use this. It's error prone and there's easy and faster ways to do the same thing.
a
I think removing it completely makes sense
1
I'd actually prefer extending the Kotest Gradle Plugin so there was a DSL for setting the options in the build.gradle, and the plugin would pass them into the Kotest executors
s
That seems like a good idea
e
I think we still need to support having a config class or config properties, for Maven, Bazel, etc
But it would be really nice to have the DSL 🙂
s
We already support @ApplyExtension on a spec class
and via project config
and the dsl in gradle would be a great addition
a
yes, definitely. A Gradle DSL would just be a fancy wrapper over a config file (e.g. JSON )