Guide
The HOCON syntax hocon understands today, how object merging and fallback work, and where the library is headed.
The HOCON syntax hocon understands today, how object merging and fallback work, and where the library is headed.
Pages
- The HOCON format — HOCON is a superset of JSON: every JSON document is valid HOCON, but HOCON adds comments, optional quoting, optional commas, and a handful of conveniences that make hand-written config pleasant.…
- Merging and fallback — Real configuration is layered: a base with environment overrides, a default locale with per-language translations, library defaults beneath application settings. hocon expresses that with fallback — one config supplying defaults…
- Substitutions — A substitution lets one value reference another, so you write a setting once and reuse it. hocon resolves substitutions automatically when you call Hocon.parse — the config you get back…
- Roadmap — hocon is built in phases, smallest-useful-thing first. The goal of the early phases is a parser good enough to write and read i18n translation files; later phases close the gap…