Someone is sharing a detekt configuration via dependencies on multiple projects instead of copy/past...

# detekt

[Javier]

Someone is sharing a detekt configuration via dependencies on multiple projects instead of copy/paste the yaml file?

[yousef shaaban]

you need YAMl file at my project

[Javier]

can it be empty at least?

[Javier]

and get the configurations from the dependency

[yousef shaaban]

detekt-config not empty

[simon.vergauwen]

I have written a Gradle plugin that does this, but it's hacky...

The Gradle plugin contained a yml file in its resources, and copied it to the downstream project 😕

[simon.vergauwen]

IMO Detekt should have a Gradle DSL for configuration, that can easily be configured in a shared buildSrc.

[Javier]

I was thinking about the @Brais Gabin feature but I haven't tried it

[Javier]

so I can just

dependencies {
    detekt(…)
}

[Javier]

where … can be any shared rule or group of rules

[Brais Gabin]

What's my feature? I think that I'm missing something

[Javier]

I think this

https://github.com/detekt/detekt/pull/4315

[Brais Gabin]

Oh! I see. No, I don't think you can use that. What that's does is to append some configuration to the base configuration of detekt. I'm not sure what would happen if a yaml has to style: keys at the same level.

[Davide Giuseppe Farella]

We download the yaml from our Core project on GitHub

[Brais Gabin]

With a gradle task?

[Davide Giuseppe Farella]

Yes