@o3co/ts.hocon 1.9.0 → 1.10.0

package/dist/adapters/toml.d.cts

@@ -0,0 +1,18 @@
+import { C as Config } from '../config-PdhVgeLS.cjs';
+
+/**
+ * Read a TOML document as HOCON config, via `smol-toml`.
+ *
+ * TOML's types line up with HOCON's apart from dates: HOCON has no datetime, so
+ * all four TOML date-time types become their RFC 3339 string forms, which is
+ * the honest representation rather than a lossy number (spec F4.2).
+ *
+ * `smol-toml` refuses an integer it cannot represent losslessly, so a value past
+ * the safe-integer range is an error here rather than silently rounded — go's
+ * adapter accepts those, its int64 being wide enough (spec F0.5).
+ *
+ * See docs/specs/format-ingestion-mapping.md items F4.x in the hocon scope.
+ */
+declare function parseTomlConfig(input: string, originDescription?: string): Config;
+
+export { parseTomlConfig };

package/dist/adapters/toml.d.ts

@@ -0,0 +1,18 @@
+import { C as Config } from '../config-PdhVgeLS.js';
+
+/**
+ * Read a TOML document as HOCON config, via `smol-toml`.
+ *
+ * TOML's types line up with HOCON's apart from dates: HOCON has no datetime, so
+ * all four TOML date-time types become their RFC 3339 string forms, which is
+ * the honest representation rather than a lossy number (spec F4.2).
+ *
+ * `smol-toml` refuses an integer it cannot represent losslessly, so a value past
+ * the safe-integer range is an error here rather than silently rounded — go's
+ * adapter accepts those, its int64 being wide enough (spec F0.5).
+ *
+ * See docs/specs/format-ingestion-mapping.md items F4.x in the hocon scope.
+ */
+declare function parseTomlConfig(input: string, originDescription?: string): Config;
+
+export { parseTomlConfig };