Rulebook
Third-party rules for JVM and Python lint tools, meant to be used in conjunction with official ones. Most of the rules are opinionated personal code styles. However, some already exists in other linters, providing the same experience across multiple languages.
| Language | Linter | Variants |
|---|---|---|
| Kotlin | Ktlint | Ktlint Style |
| Java | Checkstyle | Sun Style or Google Java Style |
| Groovy | CodeNarc | Groovy Style |
| Python | Pylint | Pylint Style or Google Python Style |
Download
Maven
repositories {
mavenCentral()
}
dependencies {
ktlint "com.hanggrian.rulebook:rulebook-ktlint:$version"
checkstyle "com.hanggrian.rulebook:rulebook-checkstyle:$version"
codenarc "com.hanggrian.rulebook:rulebook-codenarc:$version"
}
PyPI
pip install pylint regex rulebook-pylint
Usage
Ktlint
- Apply Ktlint Integration to Gradle project.
- Using configuration
ktlint, add this project as dependency.
configurations {
ktlint
}
dependencies {
ktlint "com.hanggrian.rulebook:rulebook-ktlint:$libraryVersion"
}
// the rest of ktlint tasks' configuration
Checkstyle
- Apply Checkstyle Gradle Plugin.
- Using configuration
checkstyle, add this project as dependency. - Point to local config file or put in
/config/checkstyle/codenarc.xml.
plugins {
checkstyle
}
checkstyle {
toolVersion "$checkstyleVersion"
configFile "path/to/rulebook_checkstyle.xml"
}
dependencies {
checkstyle "com.hanggrian.rulebook:rulebook-checkstyle:$libraryVersion"
}
CodeNarc
- Apply CodeNarc Gradle Plugin.
- Using configuration
codenarc, add this project as dependency. - Point to local config file or put in
/config/codenarc/codenarc.xml.
plugins {
codenarc
}
codenarc {
toolVersion "$codenarcVersion"
configFile "path/to/rulebook_codenarc.xml"
}
dependencies {
codenarc "com.hanggrian.rulebook:rulebook-codenarc:$libraryVersion"
}
Pylint
- Point config file to local
pylintrc.
Metadata
Release files for rulebook-pylint 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulebook_pylint-0.2.tar.gz | 28.7 kB | Without provenance | Details for rulebook_pylint-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulebook_pylint-0.2-py3-none-any.whl | Python 3 | none | any | Details for rulebook_pylint-0.2-py3-none-any.whl |
Total release size: 77.4 kB
Release files / rulebook_pylint-0.2.tar.gz
| Download URL | rulebook_pylint-0.2.tar.gz |
|---|---|
| Size | 28.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f06b396261ffe6ebae08e617d335a307d102ff6b6aba09d8e7fde2f076e9eee8
|
|
BLAKE2b-256 checksum How to use checksums |
7a7d9e627cf0fb07b7d6ee14bf3e595107cb248415f784aac2a431797fc6cfe3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / rulebook_pylint-0.2-py3-none-any.whl
| Download URL | rulebook_pylint-0.2-py3-none-any.whl |
|---|---|
| Size | 48.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c6d14240eb4c56d19cac9f6a5eddb1c0326013f75f255b9da30999e1a5392df
|
|
BLAKE2b-256 checksum How to use checksums |
e99468f532b2c4c2e69822a2c669484d552f64e08ed8bd5bdb055e0c3179524a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Security for rulebook-pylint 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.