• Stars
    star
    1,429
  • Rank 32,929 (Top 0.7 %)
  • Language
    Kotlin
  • License
    MIT License
  • Created almost 8 years ago
  • Updated 5 months ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

A ktlint gradle plugin

Ktlint Gradle

Provides a convenient wrapper plugin over the ktlint project.

Latest plugin version: 11.5.0

Join the chat at https://kotlinlang.slack.com Build and Check ktlint Gradle Plugin Portal

This plugin creates convenient tasks in your Gradle project that run ktlint checks or do code auto format.

The plugin can be applied to any project, but only activates if that project has the kotlin plugin applied. The assumption being that you would not want to lint code you weren't compiling.

Table of content

Supported Kotlin plugins

This plugin supports the following kotlin plugins:

  • "kotlin"
  • "kotlin-android"
  • "kotlin-multiplatform"
  • project kotlin script files
  • "org.jetbrains.kotlin.js"

If you know any new Kotlin plugin that is not in this list - please, open a new issue.

How to use

Minimal supported versions

This plugin was written using the new API available for the Gradle script Kotlin builds. This API is available in new versions of Gradle.

Minimal supported Gradle version: 6.8

Minimal supported Kotlin version: 1.4

Minimal supported ktlint version: 0.34.0 (additionally excluding 0.37.0 on Windows OS and 0.38.0, 0.43.0, 0.43.1 on all OS types)

Ktlint plugin

Simple setup

Build script snippet for new plugin mechanism introduced in Gradle 2.1:

Groovy
plugins {
  id "org.jlleitschuh.gradle.ktlint" version "<current_version>"
}

repositories {
  // Required to download KtLint
  mavenCentral()
}
Kotlin
plugins {
  id("org.jlleitschuh.gradle.ktlint") version "<current_version>"
}

repositories {
  // Required to download KtLint
  mavenCentral()
}

Using legacy apply method

Build script snippet for use in all Gradle versions:

Groovy
buildscript {
  repositories {
    maven {
      url "https://plugins.gradle.org/m2/"
    }
  }
  dependencies {
    classpath "org.jlleitschuh.gradle:ktlint-gradle:<current_version>"
  }
}

repositories {
  // Required to download KtLint
  mavenCentral()
}

apply plugin: "org.jlleitschuh.gradle.ktlint"
Kotlin
buildscript {
  repositories {
    maven("https://plugins.gradle.org/m2/")
  }
  dependencies {
    classpath("org.jlleitschuh.gradle:ktlint-gradle:<current_version>")
  }
}

repositories {
  // Required to download KtLint
  mavenCentral()
}

apply(plugin = "org.jlleitschuh.gradle.ktlint")

Applying to subprojects

Optionally apply plugin to all project modules:

Groovy
subprojects {
    apply plugin: "org.jlleitschuh.gradle.ktlint" // Version should be inherited from parent

    repositories {
        // Required to download KtLint
        mavenCentral()
    }

    // Optionally configure plugin
    ktlint {
        debug = true
    }
}
Kotlin
subprojects {
    apply(plugin = "org.jlleitschuh.gradle.ktlint") // Version should be inherited from parent

    repositories {
        // Required to download KtLint
        mavenCentral()
    }

    // Optionally configure plugin
    configure<org.jlleitschuh.gradle.ktlint.KtlintExtension> {
        debug.set(true)
    }
}

Baseline support

Plugin supports KtLint baseline with following limitations:

  • Format tasks ignore baseline. See #1072 KtLint issue for more details.
  • One baseline file is generated per one Gradle project (module).

Run task ktlintGenerateBaseline to generate a new baseline.

Testing KtLint snapshots

To test KtLint snapshots add following configuration into project build script (latest KtLint snapshot version name you could find here):

Groovy
repositories {
    maven {
      url 'https://oss.sonatype.org/content/repositories/snapshots'
    }
}

ktlint {
  version = "0.41.0-SNAPSHOT"
}
Kotlin
repositories {
    maven("https://oss.sonatype.org/content/repositories/snapshots")
}

ktlint {
    version.set("0.41.0-SNAPSHOT")
}

IntelliJ Idea Only Plugin

Note: This plugin is automatically applied by the main ktlint plugin.

This plugin just adds special tasks that can generate IntelliJ IDEA codestyle rules using ktlint.

Idea plugin simple setup

Build script snippet for new plugin mechanism introduced in Gradle 2.1:

plugins {
  id("org.jlleitschuh.gradle.ktlint-idea") version "<current_version>"
}

Idea plugin setup using legacy apply method

For all Gradle versions:

Use the same buildscript logic as above, but with this instead of the above suggested apply line. If you also want the GIT pre-commit gradle tasks, keep both apply variations.

apply plugin: "org.jlleitschuh.gradle.ktlint-idea"

Configuration

The following configuration block is optional.

If you don't configure this the defaults defined in the KtlintExtension object will be used.

The version of ktlint used by default may change between patch versions of this plugin. If you don't want to inherit these changes then make sure you lock your version here.

Groovy
import org.jlleitschuh.gradle.ktlint.reporter.ReporterType

ktlint {
    version = "0.22.0"
    debug = true
    verbose = true
    android = false
    outputToConsole = true
    outputColorName = "RED"
    ignoreFailures = true
    enableExperimentalRules = true
    additionalEditorconfigFile = file("/some/additional/.editorconfig")  // not supported with ktlint 0.47+
    disabledRules = ["final-newline"] // not supported with ktlint 0.48+
    baseline = file("my-project-ktlint-baseline.xml")
    reporters {
        reporter "plain"
        reporter "checkstyle"
        reporter "sarif"

        customReporters {
            "csv" {
                fileExtension = "csv"
                dependency = project(":project-reporters:csv-reporter")
            }
            "yaml" {
                fileExtension = "yml"
                dependency = "com.example:ktlint-yaml-reporter:1.0.0"
            }
        }
    }
    kotlinScriptAdditionalPaths {
        include fileTree("scripts/")
    }
    filter {
        exclude("**/generated/**")
        include("**/kotlin/**")
    }
}

dependencies {
    ktlintRuleset "com.github.username:rulseset:main-SNAPSHOT"
    ktlintRuleset files("/path/to/custom/rulseset.jar")
    ktlintRuleset project(":chore:project-ruleset")
}

or in kotlin script:

Kotlin
import org.jlleitschuh.gradle.ktlint.reporter.ReporterType

configure<org.jlleitschuh.gradle.ktlint.KtlintExtension> {
    version.set("0.22.0")
    debug.set(true)
    verbose.set(true)
    android.set(false)
    outputToConsole.set(true)
    outputColorName.set("RED")
    ignoreFailures.set(true)
    enableExperimentalRules.set(true)
    additionalEditorconfigFile.set(file("/some/additional/.editorconfig")) // not supported with ktlint 0.47+
    disabledRules.set(setOf("final-newline")) // not supported with ktlint 0.48+
    baseline.set(file("my-project-ktlint-baseline.xml"))
    reporters {
        reporter(ReporterType.PLAIN)
        reporter(ReporterType.CHECKSTYLE)

        customReporters {
            register("csv") {
                fileExtension = "csv"
                dependency = project(":project-reporters:csv-reporter")
            }
            register("yaml") {
                fileExtension = "yml"
                dependency = "com.example:ktlint-yaml-reporter:1.0.0"
            }
        }
    }
    kotlinScriptAdditionalPaths {
        include(fileTree("scripts/"))
    }
    filter {
        exclude("**/generated/**")
        include("**/kotlin/**")
    }
}

dependencies {
    ktlintRuleset("com.github.username:rulseset:main-SNAPSHOT")
    ktlintRuleset(files("/path/to/custom/rulseset.jar"))
    ktlintRuleset(project(":chore:project-ruleset"))
}

Setting reports output directory

It is possible also to define different from default output directory for generated reports (by default it is "build/reports/ktlint"):

Groovy
tasks.withType(org.jlleitschuh.gradle.ktlint.tasks.GenerateReportsTask) {
    reportsOutputDirectory = project.layout.buildDirectory.dir("other/location/$name")
}
Kotlin script
tasks.withType<org.jlleitschuh.gradle.ktlint.tasks.GenerateReportsTask> {
    reportsOutputDirectory.set(
        project.layout.buildDirectory.dir("other/location/$name")
    )
}

Custom reporters

Note: If Ktlint custom reporter creates report output file internally, for example:

class CsvReporter(
    private val out: PrintStream
) : Reporter {
    override fun onLintError(file: String, err: LintError, corrected: Boolean) {
        val line = "$file;${err.line};${err.col};${err.ruleId};${err.detail};$corrected"
        out.println(line)
        File("some_other_file.txt").write(line) // <-- Here!!!
    }
}

"some_other_file.txt" won't be captured as task output. This may lead to the problem, that task will always be not "UP_TO_DATE" and caching will not work.

Changing workers memory usage

By default, KtLint Gradle workers will use at most 256mb of heap size. For some projects it may be not enough, but it is possible to change:

Groovy
tasks.withType(org.jlleitschuh.gradle.ktlint.tasks.BaseKtLintCheckTask).configureEach {
    it.workerMaxHeapSize.set("512m")
}
Kotlin script
tasks.withType<org.jlleitschuh.gradle.ktlint.tasks.BaseKtLintCheckTask> {
    workerMaxHeapSize.set("512m")
}

Samples

This repository provides the following examples of how to set up this plugin:

Tasks Added

Main tasks

This plugin adds following tasks to every project:

  • loadKtlintReporters - preloads KtLint Reporters
  • runKtlintCheckOverKotlinScripts - runs actual lint check over project Kotlin script files
  • ktlintKotlinScriptCheck - generates reports and prints issues into Gradle console based on lint check found errors. This task execution depends on loadKtlintReporters and runKtlintCheckOverKotlinScripts tasks execution outputs
  • runKtlintFormatOverKotlinScripts - tries to format according to the code style project Kotlin script files
  • ktlintKotlinScriptFormat - generate reports and prints issues into Gradle console based on found non-formattable errors. This task execution depends on loadKtlintReporters and runKtlintFormatOverKotlinScripts tasks execution outputs
  • ktlintCheck - checks all SourceSets and project Kotlin script files
  • ktlintFormat - tries to format according to the code style all SourceSets Kotlin files and project Kotlin script files

Then for each SourceSet plugin adds following tasks:

  • runKtlintCheckOver[source set name]SourceSet - runs actual lint check on every Kotlin file in given SourceSet
  • ktlint[source set name]SourceSetCheck - generates reports and prints issues into Gradle console based on lint check found errors. This task execution depends on loadKtlintReporters and runKtlintCheckOver[source set name]SourceSet tasks execution outputs
  • runKtlintFormatOver[source set name]SourceSet - tries to format according to the code style every Kotlin file in given SourceSet
  • ktlint[source set name]SourceSetCheck - generates reports and prints issues into Gradle console based on found non-formattable errors. This task execution depends on loadKtlintReporters and runKtlintFormatOver[source set name]SourceSet tasks execution outputs

Additional helper tasks

Following additional tasks are added:

  • ktlintApplyToIdea - The task generates IntelliJ IDEA (or Android Studio) Kotlin style files in the project .idea/ folder. Note that this task will overwrite the existing style file.
  • ktlintApplyToIdeaGlobally - The task generates IntelliJ IDEA (or Android Studio) Kotlin style files in the user home IDEA (or Android Studio) settings folder. Note that this task will overwrite the existing style file.
  • addKtlintCheckGitPreCommitHook - adds Git pre-commit hook, that runs ktlint check over staged files.
  • addKtlintFormatGitPreCommitHook - adds Git pre-commit hook, that runs ktlint format over staged files and adds fixed files back to commit.

All these additional tasks are always added only to the root project.

FAQ

  • Is it possible to not stop task execution if some of the subprojects tasks failed?

Yes. Just use gradle --continue option:

$ ./gradlew --continue ktlintCheck

No. These approaches are not equivalent to how they work. The problem that the plugin may not find some of the kotlin plugins if both approaches are used in the project configuration. Especially it is related to the Android plugin.

  • Does plugin check change files incrementally?

Yes, check tasks support it. On the first run, the task will check all files in the source set, on subsequent runs it will check only added/modified files.

Format tasks do not check files incrementally.

  • I could not filter dynamically attached sources that are located outside of the project dir.

Gradle based filtering are only working for files located inside project (subproject) folder, see gradle/gradle#3417 To filter files outside project dir, use:

exclude { element -> element.file.path.contains("generated/") }
  • Running KtLint fails with strange exception (for example, check #383)

Ensure you are not pinning Kotlin version for "ktlint*" configurations added by plugin.

KtLint relies on Kotlin compiler to parse source files. Each version of KtLint are build using specific Kotlin version.

To exclude "ktlint*" Gradle configurations from Kotlin version pinning - use following approach:

configurations.all {
    if (!name.startsWith("ktlint")) {
        resolutionStrategy {
            eachDependency {
                // Force Kotlin to our version
                if (requested.group == "org.jetbrains.kotlin") {
                    useVersion("1.3.72")
                }
            }
        }
    }
}

Developers

Importing

Import the settings.gradle.kts file into your IDE.

To enable the Android sample either define the ANDROID_HOME environmental variable or add a local.properties file to the project root folder with the following content:

sdk.dir=<android-sdk-location>

Building

Building the plugin: ./plugin/gradlew build

On how to run the current plugin snapshot check on sample projects: ./gradlew ktlintCheck

Running tests from IDEA IDE

To run tests in IDEA IDE, firstly you need to run following gradle task (or after any dependency change):

$ ./plugin/gradlew -p ./plugin pluginUnderTestMetadata

Optionally you can add this step test run configuration.

Links

Ktlint Gradle Plugin on the Gradle Plugin Registry

More Repositories

1

zoom_vulnerability_poc

HTML
132
star
2

bulk-security-pr-generator

Generate thousands of pull requests to fix widespread security vulnerabilities across GitHub.
Python
29
star
3

security-checklist-transformer

Sqreen Security Checklist Transformer & Uploader
HTML
26
star
4

lgtm_hack_scripts

Collection of python helper API's for interacting with LGTM.com in ways the official API doesn't support.
Python
23
star
5

kotlin-guiced

Convenience Kotlin API over the Google Guice DI Library
Kotlin
17
star
6

gradle-kotlin-aspectj-weaver

A Gradle plugin that allows you to weave your compiled Java and Kotlin files with AspectJ
Kotlin
16
star
7

security-research

Public disclosure channel for security vulnerabilities
Python
15
star
8

kwava

A faithful port of the Guava Standard Library to Kotlin
Java
5
star
9

vulnerability-disclosure-best-practices

4
star
10

pmd-kotlin

PMD Ruleset for Kotlin, in particular CPD support for Kotlin
Kotlin
3
star
11

github_codesearch_hack_scripts

Collection of python helper API's for interacting with cs.github.com since no official API exists.
Python
3
star
12

Dynamic-Decorator

A simplistic java decorator that uses reflection to decorate all methods on an interface.
Java
3
star
13

gradle-testing

Basic repository for testing various bugs/features of the Gradle ecosystem in a small sandbox environment.
Kotlin
2
star
14

refactoring-interview-question

An interview question to test applicants refactoring and software design skills.
Java
2
star
15

BetterCKConsoleViewer

JavaScript
2
star
16

endoflife-matrix-action

TypeScript
1
star
17

subdomain-takeover

Demo project for proving subdomain-takeover with Github
HTML
1
star
18

CS4341_Team10

Java
1
star
19

WPI-CS3043-Imitation-Game

HTML
1
star
20

bad-random-examples

Java
1
star
21

vexAPP

Making the VEX alliance selection process easier is our priority!
Java
1
star
22

kotlin-data-class-builder-compiler-plugin

Compiler plugin for kotlin that automatically creates the builder pattern on data classes
Kotlin
1
star
23

security-checklist-testing

1
star
24

automated-disclosure

Automating the tedious parts of the vulnerability disclosure process.
Kotlin
1
star
25

MissingVenice-MissingTreasuresCollage

JavaScript
1
star
26

dwf-request

Tools used for processing CVE requests
Python
1
star
27

kotlin-jdk9-javadoc-bug-demo

Demonstrates a bug with JDK 9 parsing java bytecode to generate javadocs
Java
1
star
28

springBootTesting

Testbed for gradle spring boot stuff
Kotlin
1
star
29

CS3013

C
1
star