Hi, does anyone use the detekt step in bitrise? I’m not sure how long it would take to finish that step but is 10-15 minutes to complete normal? Thanks

anyone got detekt sample project in github?

"are now configured to exclude the

**/test/**,**/*Test.kt,**/*Spec.kt"

folder (this is valid only if you were using the default config file)" ahh...FWIW, it was nicer having the excludes in one place since now it means you need to duplicate the excludes glob match list in a bunch of places. We did it for comments and these: - 'NamingRules' - 'WildcardImport' - 'MagicNumber' - 'MaxLineLength' - 'LateinitUsage' - 'StringLiteralDuplication' - 'SpreadOperator' - 'TooManyFunctions' - 'ForEachOnRange' - 'FunctionMaxLength' Looks like the default only does comments and: StringLiteralDuplication and TooManyFunctions

Anybody use detekt with multiplatform? Specifically trying custom extensions. I can add my jar at the root level, but in the source set dependencies, the gradle build fails to see

detektPlugins

as a valid configuration

Does turning on debug mode also print out the baseline file? I don't see it in the debug output. I can't get detekt to take my baseline file which it definitely generates if I do "gradle detektBaseline"

Is there any rule that would allow enforcing a return value (from a function marked with an annotation) wasn't ignored?

Just found out that detekt is on "Trial" at the newest Thoughworks Technology Radar! - https://www.thoughtworks.com/radar/tools We've climbed from Assess to Trial in half a year and they have a nice text written about detekt too. Motivating!

I setup detekt a while back and am trying to update from

1.0.0-RC146

to

1.4.0

. Mostly working, but many of the rules simply aren't running. Looking through GH issues I see work was done around "type resolution" in v

1.1

. Is this working on multi-module Android projects yet? I see this comment from back in October with no corresponding PRs since: https://github.com/arturbosch/detekt/issues/2036#issuecomment-544105669

Is there a way in a detekt spec (for a rule I'm working on) to use

${...}

in the compiled test code? If I do:

val code = """
    fun foo() {
        println("The list is ${listOf(1, 2, 3)}"
    }
""".trimIndent()
assertThat(subject.compileAndLintWithContext(wrapper.env, code)).hasSize(0)

then the compiled

ktFile

has the list expanded, but if I do:

val code = """
    fun foo() {
        println("The list is \$\{listOf(1, 2, 3)\}"
    }
""".trimIndent()
assertThat(subject.compileAndLintWithContext(wrapper.env, code)).hasSize(0)

then the compiled

ktFile

maintains the escape characters, so the code isn't actually doing the expansion

Hello, I'm using https://github.com/JetBrains/intellij-community/tree/master/uast to parse some kotlin files. From what I understand detekt relies on this library as well? If not feel free to ignore my question. My problem is trying to figure out how I can resolve the value of a reference. In my case it's a `KtNameReferenceExpression`which simply points to a string declared in the same file.

BindingContextUtils

seems to provide the functionality I'm after, but I can't figure out how to get a

BindingContext.

You can refer to a very large amount of open source projects out there that are using Detekt, no need to make sample projects.

Is there a reasonable way to emit a warning from a custom detekt rule?

A related question, perhaps: Where is the best place to put a check on the user-specified configuration for a particular custom ruleset?

Is there a good way to reuse exclude patterns with detekt? I’ve found it’s a lot of copy/paste of

excludes: "**/*Test.kt"

https://arturbosch.github.io/detekt/howto-migratetestpattern.html

Are there plans to add android configurations to Lint rule sets outside of the formatting group? i.e. Empty blocks are valid in android https://developer.android.com/kotlin/style-guide#empty_blocks as long as they are on a new line. A global variable for this configuration option could be useful

If I use plugin for IDE and not gradle plugin, is there a way I can generate the detekt report of violations? Or the only way is to visit each file and correct the errors?

Does anyone know when detekt-intellij-plugin 1.0.0-RC1 is released? https://github.com/detekt/detekt-intellij-plugin/milestone/4

I would like some assistance integrating Detekt in my Android project. I successfully generated my config file, but that’s all that is working. Both tasks

detektBaseline

and

detekt

finish successfully in 1 second and nothing else happens, even though I know for a fact that the code contains errors. The only way I had it working was by creating my own Gradle tasks, but I don’t want to do this if I don’t have to. I have this in my project-level Gradle:

plugins {
    id "io.gitlab.arturbosch.detekt" version "1.6.0"
}

detekt {
    toolVersion = "1.6.0"

    config = files("$projectDir/config/detekt/detekt.yml")
    baseline = file("$projectDir/config/detekt/baseline.xml")
//    source = files("src/main/kotlin") // This does not work for some reasons (Could not set unknown property 'source' for object of type io.gitlab.arturbosch.detekt.extensions.DetektExtension.)

    buildUponDefaultConfig = true
    parallel = true
    ignoreFailures = true

    reports {
        txt.enabled = false
        xml.enabled = false
        html {
            enabled = true
            destination = file("$projectDir/reports/detekt/report.html")
        }
    }
}

Hey. I've looked through existing rules, seems that nothing covers number of parameters in contructors.

LongParameterList

is the nearest thing, but it covers only methods. I've tried to cover constructors there (https://github.com/r4zzz4k/detekt/commit/1cf853c), but

./gradlew check

finds issues with existing code after that (https://github.com/arturbosch/detekt/blob/521e968/detekt-api/src/main/kotlin/io/gitlab/arturbosch/detekt/api/CodeSmell.kt#L44-L51). So two questions: 1. Does this sound like a useful rule? In discussions over the Internet on argument count limit I mostly see costructors included. Checktyle, for example, also covers both methods and parameters (https://checkstyle.sourceforge.io/apidocs/com/puppycrawl/tools/checkstyle/checks/sizes/ParameterNumberCheck.html), PMD seems to agree on that (https://stackoverflow.com/q/56492868/2475207). 2. What's the flow for contributing rules which don't validate current code? Seems that

check

task completes successfully on the project itself. 3. Are there any general contribution guidelines described somewhere I've missed?

I'm also occasionally catching the following when trying to run

./gradlew check

on my local branch:

Execution failed for task ':detekt-api:detekt'.
> io.gitlab.arturbosch.detekt.api.RuleSetProvider: Error reading configuration file
...
Caused by: java.util.ServiceConfigurationError: io.gitlab.arturbosch.detekt.api.RuleSetProvider: Error reading configuration file
        at io.gitlab.arturbosch.detekt.core.RuleSetLocator.load(RuleSetLocator.kt:29)
        at io.gitlab.arturbosch.detekt.cli.config.DefaultPropertiesConfigValidator$validate$1.invoke(DefaultPropertiesConfigValidator.kt:20)
        at io.gitlab.arturbosch.detekt.cli.config.DefaultPropertiesConfigValidator.validate(DefaultPropertiesConfigValidator.kt:27)
        at io.gitlab.arturbosch.detekt.cli.config.ConfigValidatorsKt.checkConfiguration(ConfigValidators.kt:18)
        at io.gitlab.arturbosch.detekt.cli.runners.Runner.execute(Runner.kt:30)
        at io.gitlab.arturbosch.detekt.invoke.DefaultCliInvoker.invokeCli(DetektInvoker.kt:51)
        ... 93 more
Caused by: java.util.zip.ZipException: invalid distance too far back
        ... 99 more

Not sure if I'm doing something wrong or this is an issue to be reported. Just in case this helps: Ubuntu 19.10,

> java -version
openjdk version "1.8.0_242"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_242-b08)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.242-b08, mixed mode)

I guess the question is how to run the tests using intelliJ. I installed the Spek plugin already and still couldn’t find the spec

I just found a line on this page (https://arturbosch.github.io/detekt/howto-buildupondefaultconfig.html) that seems to have some more info:

Make sure to specify the 

input

 parameter or no sources are found and detekt won’t run!

This seems to be partially true. It does seem to run if you don't have a separate config YAML file. I updated the input as per that page and it works well enough for now. Still confusing that it can run without it in some scenarios.

Is it currently possible to extend a config that is not the base config? Would this be something we would be interested in in the library?

When i generate a baseline through gradle, I keep getting lines like

<ID>NoBlankLineBeforeRbrace:</ID>

without a reference to a part of the codebase. This seems to cause detekt to ignore the rule entirely in that module rather than just ignore existing instances of violations. Is this expected behavior and is there any way to prevent this from being generated?

I'm getting the following exception with detekt 1.7.0 when using

--config-resource detekt-config.yml

to read a config file out of a jar on the classpath. running detekt via maven antrun plugin. works fine in 1.6.0. anyone else seen anything like this?

java.nio.file.FileSystemNotFoundException
	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.getFileSystem(ZipFileSystemProvider.java:169)
	at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.getPath(ZipFileSystemProvider.java:155)
	at java.base/java.nio.file.Path.of(Path.java:208)
	at java.base/java.nio.file.Paths.get(Paths.java:97)
	at io.gitlab.arturbosch.detekt.rules.documentation.LicenceHeaderLoaderExtension.init(LicenceHeaderLoaderExtension.kt:27)
	at io.gitlab.arturbosch.detekt.core.FileProcessorLocator.load(FileProcessorLocator.kt:18)
	at io.gitlab.arturbosch.detekt.core.DetektFacade$Companion.create(DetektFacade.kt:90)
	at io.gitlab.arturbosch.detekt.cli.runners.Runner.execute(Runner.kt:33)
	at io.gitlab.arturbosch.detekt.cli.Main.main(Main.kt:20)

I’m looking for an easy way to report warnings in Detekt (that are not going to fail the build). I know there is a

Severity.Warning

on the

Issue

class that I can set for each issue that I report on a my rule. The problem is that those issues are counted towards the total number of issues used to let Detekt fail or not. Anyone faced a similar scenario?

Hello everyone, does the detekt cli have any advantage over the gradle plugin? Can you do top level task instead of 1 per module as well?

Looking at the CLI again I was wondering how do you download/generate the latest detekt-formatting jar? Would it be possible to include it in future releases?

Known issues or new ones? If they’re new ones, file them please 🙂