disabledRules broken in 2.3.0?

After upgrading from 2.2.0 to 2.3.0 formatKotlin complains about wildcards: Format could not fix > [no-wildcard-imports] Wildcard import, and it tries to order my imports. This is explicitly disabled in my kotlin dsl config:

apply(plugin: "org.jmailen.kotlinter")
kotlinter {
    disabledRules = ["no-wildcard-imports", "import-ordering"]
}

Any ideas which change could have triggered this?

[lwasyl]

When you say the tasks were configured eagerly in this project, I guess I’m not spotting the code that indicates that – can you point it out?

There’s nothing in the snippet posted, but since OP indicates it’s a pretty complex multiproject build, it’s not uncommon to have a plugin or other piece of common script do something like project.tasks.all { } or tasks.whenTaskAdded { }, which makes all tasks get realized as soon as they’re registered. Even Kotlin plugin had a bug that caused this. In any case it seems like the only possible scenario of this bug happening, as in fact task getting created immediately would make it unaware of configuration provided in extension

[mateuszkwiecinski]

Thanks for all the valuable information 🙏 The ktLintParams should be already filled in, in the configuration phase, so the disabledRules=[] shouldn’t ever happen with your config. Thanks again, and I’ll try to narrow down possible scenarios why that could be happening 🤔