@o3co/ts.hocon 1.11.0 → 1.13.0

package/dist/{config-Dlq6rF3w.d.cts → config-6sApTEMM.d.cts}

@@ -363,6 +363,28 @@ declare class Config {
     toObject(opts?: {
         nullPrototype?: boolean;
     }): unknown;
+    /**
+     * Renders this resolved Config as HOCON text (E18; lockstep with go.hocon's
+     * `Config.RenderHOCON`, v1.11.0).
+     *
+     * The output round-trips: parsing it back yields the same value tree. That
+     * is the correctness contract, not byte-for-byte formatting — a scalar is
+     * quoted whenever leaving it bare would re-parse as a different type (a
+     * string `"8080"` becomes `"8080"`, not `8080`), and left bare only when it
+     * provably cannot.
+     *
+     * The Config must be resolved and hold only data (objects, arrays, string /
+     * number / boolean / null scalars) — exactly what {@link fromMap} and the
+     * format adapters produce. An unresolved placeholder throws
+     * {@link ConfigError}; substitutions have no textual round trip through a
+     * value tree.
+     *
+     * The root object's fields are emitted without enclosing braces, nested
+     * objects as `key { … }`, arrays as newline-separated `[ … ]`, indented two
+     * spaces. Source comments are not represented — a value tree does not carry
+     * them.
+     */
+    renderHocon(): string;
     /**
      * @internal Test-only: renders this resolved Config's value tree as canonical
      * JSON (sorted keys, no whitespace). Used by Layer-2 fixture tests to compare

package/dist/{config-Dlq6rF3w.d.ts → config-6sApTEMM.d.ts}

@@ -363,6 +363,28 @@ declare class Config {
     toObject(opts?: {
         nullPrototype?: boolean;
     }): unknown;
+    /**
+     * Renders this resolved Config as HOCON text (E18; lockstep with go.hocon's
+     * `Config.RenderHOCON`, v1.11.0).
+     *
+     * The output round-trips: parsing it back yields the same value tree. That
+     * is the correctness contract, not byte-for-byte formatting — a scalar is
+     * quoted whenever leaving it bare would re-parse as a different type (a
+     * string `"8080"` becomes `"8080"`, not `8080`), and left bare only when it
+     * provably cannot.
+     *
+     * The Config must be resolved and hold only data (objects, arrays, string /
+     * number / boolean / null scalars) — exactly what {@link fromMap} and the
+     * format adapters produce. An unresolved placeholder throws
+     * {@link ConfigError}; substitutions have no textual round trip through a
+     * value tree.
+     *
+     * The root object's fields are emitted without enclosing braces, nested
+     * objects as `key { … }`, arrays as newline-separated `[ … ]`, indented two
+     * spaces. Source comments are not represented — a value tree does not carry
+     * them.
+     */
+    renderHocon(): string;
     /**
      * @internal Test-only: renders this resolved Config's value tree as canonical
      * JSON (sorted keys, no whitespace). Used by Layer-2 fixture tests to compare