kora-config-hoconlisted

# Kora Config HOCON > **Kora sub-skill — obey the [kora-v1 meta rules](../../SKILL.md) on every task:** **R0** ensure `.kora-agent/` docs+examples are cloned · **R1** read this sub-skill before writing code · **R2** Kora APIs only — no Spring/Micronaut/Quarkus, no invented annotations or config keys · **R3** journal any incorrect Kora usage. Add comments/Javadoc only if asked. **Artifact:** `ru.tinkoff.kora:config-hocon` | **Module:** `HoconConfigModule` | **Annotations package:** `ru.tinkoff.kora.config.common.annotation` HOCON is the recommended config format for Kora. The `config-hocon` module maps `application.conf` into type-safe interfaces at compile time. Define a config interface, annotate it, and inject it as an ordinary graph dependency through the constructor. There is no field injection and no runtime reflection — the annotation processor generates the extractor. ## Quick Start ### 1. Dependencies (`build.gradle`) ```groovy dependencies { koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19") // MANDATORY — without the annotation processor nothing is generated annotationProcessor "ru.tinkoff.kora:annotation-processors" implementation "ru.tinkoff.kora:config-hocon" implementation "ru.tinkoff.kora:logging-logback" } ``` Kotlin uses `ksp "ru.tinkoff.kora:symbol-processors"` instead of `annotationProcessor`. All `ru.tinkoff.kora:*` artifacts inherit their version from the `kora-parent` BOM — never version them individually. ### 2. Enable