• e

    eygraber

    5 months ago
    Was there an issue with the 1.13.0 artifacts? They don't seem to be in mavenCentral, but the compiler plugin is expecting them. I'm working around it now by explicitly depending on 1.13.1 artifacts. Also, is there a snapshot of the compiler plugin anywhere?
    e
    1 replies
    Copy to Clipboard
  • Curtis Kroetsch

    Curtis Kroetsch

    5 months ago
    Is there anyway to change the default severity to error for every check, without needing to explicitly set it for every ruleset?
    Curtis Kroetsch
    s
    4 replies
    Copy to Clipboard
  • d

    dix

    5 months ago
    has anyone noticed issues with
    jvmTarget
    when attempting to upgrade to
    1.20.0
    ? when I upgrade the version, now all my detekt tasks fail with
    Invalid value passed to --jvm-target
    I've tried adding
    tasks.withType(Detekt).configureEach {
        jvmTarget = "1.8"
    }
    and that fails with
    Could not get unknown property 'Detekt'
    d
    e
    6 replies
    Copy to Clipboard
  • Marcelo Hernandez

    Marcelo Hernandez

    5 months ago
    Anyone successfully using Kotlin's Explicit API Mode with Detekt in an Android project? Did you have to disable the
    RedundantVisibilityModifierRule
    rule?
    Marcelo Hernandez
    e
    3 replies
    Copy to Clipboard
  • e

    eygraber

    5 months ago
    Have you had any conversations with anyone at Google or Jetbrains about helping with that? I could contribute towards it, but I only have very basic experience with compiler plugins.
    e
    1 replies
    Copy to Clipboard
  • s

    Sam

    5 months ago
    Just spotted that entries in my baseline seem to be different (extra whitespace) depending on whether the function has a doc comment or not. Before I go digging in changelogs and/or file an issue, is this something that's already been spotted/fixed? I think I'm on a slightly old version of detekt.
    s
    marschwar
    2 replies
    Copy to Clipboard
  • gammax

    gammax

    5 months ago
    Just saw question about "running detekt on a single file" on my notifications. I came here to answer, but the message is gone 😅 Anyway, you can use the
    --input
    arg. More on this here https://detekt.dev/docs/gettingstarted/git-pre-commit-hook
    gammax
    Bruno Pérez Motter
    8 replies
    Copy to Clipboard
  • e

    eygraber

    5 months ago
    Any plans for a 1.20.1 release for https://github.com/detekt/detekt/pull/4723? It (hopefully) fixes what is blocking me from 1.20.0
    e
    gammax
    +1
    16 replies
    Copy to Clipboard
  • An Tran

    An Tran

    5 months ago
    Hello guys, do you know why this url is broken: https://detekt.dev/compose.html
    An Tran
    1 replies
    Copy to Clipboard
  • e

    eygraber

    4 months ago
    Not sure if this is a detekt or ksp issue, but when I run
    detektJvmMain
    I get the following warning:
    Execution optimizations have been disabled for task ':samples:kotlin-inject:detektJvmMain' to ensure correctness due to the following reasons:
      - Gradle detected a problem with the following location: '/home/eli/workspace/portal/samples/kotlin-inject/build/generated/ksp/jvm/jvmMain/kotlin'. Reason: Task ':samples:kotlin-inject:detektJvmMain' uses this output of task ':samples:kotlin-inject:kspKotlinJvm' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to <https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implicit_dependency> for more details about this problem.
    warning: classpath entry points to a non-existent location: /home/eli/workspace/portal/samples/kotlin-inject/build/generated/ksp/metadata/jvmMain/kotlin
    I exclude generated ksp files from detekt using:
    tasks.withType<Detekt>().configureEach {
      exclude {
        "/build/generated/ksp" in it.file.absolutePath
      }
    }
    e
    gammax
    6 replies
    Copy to Clipboard