@o3co/ts.hocon 1.9.0 → 1.11.0

package/dist/adapters/properties.d.cts

@@ -0,0 +1,32 @@
+import { C as Config } from '../config-Dlq6rF3w.cjs';
+
+/**
+ * Read a `java.util.Properties` file as HOCON config.
+ *
+ * The result is a fully resolved Config holding only strings, so it works as a
+ * fallback layer under your own document:
+ *
+ * ```ts
+ * const base = parsePropertiesConfig(readFileSync('service.properties', 'utf-8'))
+ * const cfg = parse(readFileSync('app.conf', 'utf-8'), { resolveSubstitutions: false })
+ * const merged = cfg.withFallback(base).resolve()
+ * ```
+ *
+ * Deferring resolution matters: the default `parse` resolves as it goes, so a
+ * `${...}` pointing into the Properties file would fail before the fallback is
+ * ever attached.
+ *
+ * A `${a.b}` in a value stays that literal text — the file belongs to another
+ * program that never agreed to HOCON's syntax (spec F0.2).
+ *
+ * Dotted keys nest (F2.1), and every key is preserved — `__proto__`,
+ * `constructor` and `prototype` included (F2.9). They arrive as ordinary keys:
+ * the tree is built on null-prototype objects and `toObject()` defines own
+ * properties, so nothing can reach `Object.prototype`.
+ *
+ * Shares its syntax layer with `include "x.properties"`, so the two cannot
+ * drift apart.
+ */
+declare function parsePropertiesConfig(input: string, originDescription?: string): Config;
+
+export { parsePropertiesConfig };

package/dist/adapters/properties.d.ts

@@ -0,0 +1,32 @@
+import { C as Config } from '../config-Dlq6rF3w.js';
+
+/**
+ * Read a `java.util.Properties` file as HOCON config.
+ *
+ * The result is a fully resolved Config holding only strings, so it works as a
+ * fallback layer under your own document:
+ *
+ * ```ts
+ * const base = parsePropertiesConfig(readFileSync('service.properties', 'utf-8'))
+ * const cfg = parse(readFileSync('app.conf', 'utf-8'), { resolveSubstitutions: false })
+ * const merged = cfg.withFallback(base).resolve()
+ * ```
+ *
+ * Deferring resolution matters: the default `parse` resolves as it goes, so a
+ * `${...}` pointing into the Properties file would fail before the fallback is
+ * ever attached.
+ *
+ * A `${a.b}` in a value stays that literal text — the file belongs to another
+ * program that never agreed to HOCON's syntax (spec F0.2).
+ *
+ * Dotted keys nest (F2.1), and every key is preserved — `__proto__`,
+ * `constructor` and `prototype` included (F2.9). They arrive as ordinary keys:
+ * the tree is built on null-prototype objects and `toObject()` defines own
+ * properties, so nothing can reach `Object.prototype`.
+ *
+ * Shares its syntax layer with `include "x.properties"`, so the two cannot
+ * drift apart.
+ */
+declare function parsePropertiesConfig(input: string, originDescription?: string): Config;
+
+export { parsePropertiesConfig };