@o3co/ts.hocon 1.11.0 → 1.13.0

package/dist/adapters/jsonc.d.cts

@@ -1,4 +1,4 @@
-import { C as Config } from '../config-Dlq6rF3w.cjs';
+import { C as Config } from '../config-6sApTEMM.cjs';
 
 /**
  * Read JSON with comments and trailing commas — the dialect VS Code and
@@ -20,7 +20,18 @@ import { C as Config } from '../config-Dlq6rF3w.cjs';
  * the JS number model, as they do for HOCON's own literals, so read large
  * identifiers with `getString`.
  *
- * See docs/specs/format-ingestion-mapping.md items F3.x in the hocon scope.
+ * **An unpaired `\uXXXX` surrogate is accepted here and refused by go.hocon,
+ * py.hocon and rs.hocon** (F3.5). That is deliberate, and the same divergence
+ * the properties adapter already carries under F2.8: a JavaScript string is
+ * UTF-16, like Java's, so it holds a lone surrogate natively and round-trips it.
+ * A Go or Rust string cannot hold one at all — Go silently substituted U+FFFD
+ * until F3.5 — and a Python `str` can hold one but cannot encode it as UTF-8,
+ * so all three refuse rather than defer the failure. Refusing here would mean
+ * this spec overriding the host language rather than protecting the user; see
+ * S1.2.6 for the class.
+ *
+ * See the F3.x items in the format-ingestion mapping spec:
+ * https://github.com/o3co/xx.hocon/blob/main/docs/format-ingestion-mapping.md
  */
 declare function parseJsonc(input: string, originDescription?: string): Config;
 /**

package/dist/adapters/jsonc.d.ts

@@ -1,4 +1,4 @@
-import { C as Config } from '../config-Dlq6rF3w.js';
+import { C as Config } from '../config-6sApTEMM.js';
 
 /**
  * Read JSON with comments and trailing commas — the dialect VS Code and
@@ -20,7 +20,18 @@ import { C as Config } from '../config-Dlq6rF3w.js';
  * the JS number model, as they do for HOCON's own literals, so read large
  * identifiers with `getString`.
  *
- * See docs/specs/format-ingestion-mapping.md items F3.x in the hocon scope.
+ * **An unpaired `\uXXXX` surrogate is accepted here and refused by go.hocon,
+ * py.hocon and rs.hocon** (F3.5). That is deliberate, and the same divergence
+ * the properties adapter already carries under F2.8: a JavaScript string is
+ * UTF-16, like Java's, so it holds a lone surrogate natively and round-trips it.
+ * A Go or Rust string cannot hold one at all — Go silently substituted U+FFFD
+ * until F3.5 — and a Python `str` can hold one but cannot encode it as UTF-8,
+ * so all three refuse rather than defer the failure. Refusing here would mean
+ * this spec overriding the host language rather than protecting the user; see
+ * S1.2.6 for the class.
+ *
+ * See the F3.x items in the format-ingestion mapping spec:
+ * https://github.com/o3co/xx.hocon/blob/main/docs/format-ingestion-mapping.md
  */
 declare function parseJsonc(input: string, originDescription?: string): Config;
 /**