Kotlin (.kt) files are correctly recognized. Kotlin Script files are essentially just Kotlin files and follow the exact same syntax. I believe that they should be added to the plugin as defaults. Do note that it is common for Kotlin Script files to have two extensions, like this: myfile.ext.kts. This is used for recognizing scripting templates, and they should also be recognized as just Kotlin files.
Gradle buildscripts that use the Kotlin DSL are also .kts files. They could probably be excluded by excluding anything that ends in .gradle.kts.
Hi, you might be able to use a custom task for this. I did this on another project to apply some licensing headers to things that weren't in regular sourcesets, see here
Kotlin (.kt) files are correctly recognized. Kotlin Script files are essentially just Kotlin files and follow the exact same syntax. I believe that they should be added to the plugin as defaults. Do note that it is common for Kotlin Script files to have two extensions, like this:
myfile.ext.kts
. This is used for recognizing scripting templates, and they should also be recognized as just Kotlin files.Gradle buildscripts that use the Kotlin DSL are also .kts files. They could probably be excluded by excluding anything that ends in
.gradle.kts
.