@tehw0lf/n8n-nodes-toon 1.3.3 → 1.4.0

package/README.md

@@ -318,11 +318,11 @@ Workflow: Fetch Data → JSON to TOON → Format Report → Send Email
 
 - **n8n version:** 0.200.0 or later
 - **Node.js:** 18.x or later
-- **TOON Specification:** v3.3
+- **TOON Specification:** v4.1
 
 ## Specification Compliance
 
-This node implements **TOON Specification v3.3** with comprehensive coverage of all core features and major optional features.
+This node implements **TOON Specification v4.1** in full: every normative requirement of Sections 1–16 for encoders and decoders, using the default options. Two additional convenience options fall outside the specification and are documented as [non-spec extensions](#non-spec-extensions) below.
 
 ### Implemented Features
 
@@ -331,17 +331,49 @@ This node implements **TOON Specification v3.3** with comprehensive coverage of
 - Indentation-based structure with configurable spacing
 - Array length declarations `[N]`
 - Tabular arrays for uniform objects `[N]{field1,field2}:`
+- Nested field groups for uniform nested-object columns (§9.3): `orders[2]{id,customer{name,country},total}:`
+- Keyed tabular form for objects of uniform objects (§9.5): `users[2:]{age,city}:`
+- Hyphen syntax for objects as list items, including headers carried on the hyphen line (§10)
+- Full-line comment lines, stripped by the decoder and never emitted by the encoder (§5.1)
 - All three delimiters: comma (default), tab, pipe
 - Deterministic string quoting and escaping
-- Strict mode validation with array count and width checking
+- CRLF input, byte-order-mark removal, and trailing-space handling (§12)
+- Strict mode validation per the §14 checklist (counts, row widths, header syntax, duplicate keys, indentation)
+
+### Non-Spec Extensions
+
+⚠️ These two options are **this node's own convenience features, not part of the TOON specification**. v4.1 treats dotted keys as ordinary literal keys with no structural meaning (§8), so output produced with key folding enabled decodes to dotted keys — not nested objects — in any conforming TOON implementation. Both default to `off`; leave them off for interoperable output.
 
-✅ **Optional Features**
 - **Key Folding** (`keyFolding: "safe"`) - Collapse nested single-key objects into dotted paths (e.g., `{a: {b: {c: 1}}}` → `a.b.c: 1`)
 - **Path Expansion** (`expandPaths: "safe"`) - Expand dotted keys back into nested objects during decoding
 
-### Not Implemented
+### Notes on Encoder Output
+
+The encoder selects a form from each value's shape and position, as §1.4 requires, rather than by preference:
+
+- Uniform arrays of objects use tabular form; objects of uniform objects use keyed tabular form.
+- Primitive arrays are always inline (§9.1 defines no line-length threshold).
+- Empty arrays are `key: []` in field position and `[]` at the root; the legacy `key[0]:` form is accepted on decode but never emitted.
+- Field order follows the first object's key encounter order, so decoded elements of tabular and keyed tabular forms carry the header's field order (§2).
+
+### Documented Implementation Behavior
+
+The specification requires implementations to document the following (§2, §3, §4, §13.2):
+
+**Host-type normalization (§3).** Values are normalized to the JSON data model before encoding:
+
+| Host value | Encoded as |
+|---|---|
+| `NaN`, `Infinity`, `-Infinity` | `null` |
+| `undefined`, functions, symbols | `null` |
+| Objects with a `toJSON()` method | the normalized result of `toJSON()`, applied recursively |
+| `Date` | ISO 8601 string via the built-in `toJSON()` (quoted, since it contains colons) |
+
+**Numeric domain and out-of-range policy (§4).** Numbers are IEEE-754 doubles, the JavaScript numeric domain. Decoded numeric tokens outside that domain return the nearest approximate double rather than erroring or returning a string; values beyond `Number.MAX_SAFE_INTEGER` may therefore lose precision on round-trip. Tokens are classified by the §4 number grammar, not by `Number()`, so `.5`, `1.`, `+5`, `0x10`, `Infinity`, and `NaN` all decode as strings.
+
+**Object key order (§2).** Key order is preserved as encountered, except that tabular and keyed tabular forms reorder to the header's field order. One deviation is inherent to the JavaScript object model: **integer-like keys are hoisted** and ordered numerically ahead of string keys, so a document with keys `b`, `1`, `a` decodes to an object ordered `1`, `b`, `a`. Array order is always preserved.
 
-❌ **Hyphen Syntax for List-Item Objects (§10)** - Optional YAML-style compact notation for objects in arrays. This is a purely cosmetic encoding optimization that doesn't affect functionality or data compatibility. Our implementation uses standard object indentation instead, which is equally spec-compliant and easier to maintain.
+**Prototype keys (§15).** Decoded keys are installed with `Object.defineProperty`, so `__proto__`, `constructor`, and `prototype` become ordinary own data properties and decoding never mutates a prototype chain.
 
 ### Round-Trip Guarantee
 
@@ -463,7 +495,7 @@ See [`.github/workflows/security-scan.yml`](.github/workflows/security-scan.yml)
 
 ## Resources
 
-- **TOON Specification v3.3:** Official spec at [github.com/toon-format/spec](https://github.com/toon-format/spec) or see [SPEC.md](SPEC.md) in this repository
+- **TOON Specification v4.1:** Official spec at [github.com/toon-format/spec](https://github.com/toon-format/spec) or see [SPEC.md](SPEC.md) in this repository
 - **n8n Documentation:** https://docs.n8n.io/
 - **Community Nodes Guide:** https://docs.n8n.io/integrations/community-nodes/
 - **GitHub Repository:** https://github.com/tehw0lf/n8n-nodes-toon
@@ -483,4 +515,4 @@ Contributions are welcome! Please open an issue or pull request on GitHub.
 
 ---
 
-**Note:** This node implements the [TOON Specification v3.3](https://github.com/toon-format/spec). See `SPEC.md` for complete format documentation or visit the official spec repository.
+**Note:** This node implements the [TOON Specification v4.1](https://github.com/toon-format/spec). See `SPEC.md` for complete format documentation or visit the official spec repository.

package/dist/nodes/Toon/Toon.node.json

@@ -1,5 +1,5 @@
 {
-    "node": "@tehw0lf/n8n-nodes-toon",
+    "node": "@tehw0lf/n8n-nodes-toon.toon",
     "nodeVersion": "1.0",
     "codexVersion": "1.0",
     "categories": ["Development", "Data & Storage"],

package/dist/nodes/Toon/ToonDecoder.d.ts

@@ -1,20 +1,39 @@
 import type { DecoderOptions } from './types';
 export declare class ToonDecoder {
     private options;
+    private lines;
+    private pos;
+    private inHeaderSpan;
     constructor(options: DecoderOptions);
     decode(toonText: string): unknown;
     private parseLines;
-    private determineRootForm;
-    private parseArrayHeader;
-    private parseDelimitedTokens;
-    private parseArray;
-    private parseTabularArray;
+    private withinHeaderSpan;
+    private checkBlankInSpan;
+    private depthOf;
+    private peek;
+    private parseRoot;
+    private checkNoTrailingContent;
+    private tryParseHeader;
     private parseObject;
-    private isValidArrayHeader;
-    private isInvalidArrayHeader;
-    private findUnquotedColon;
-    private findNextSiblingIndex;
-    private parseTokenValue;
+    private assignKey;
+    private parseFieldLine;
+    private parseNestedScope;
+    private parseArrayBodyAfterHeader;
+    private parseArrayBody;
+    private parseArrayContent;
+    private parseTabularRows;
+    private materializeRow;
+    private parseKeyedTabular;
+    private parseKeyedTabularBody;
+    private parseListItems;
+    private isListItemLine;
+    private parseListItem;
+    private parseListItemRestFields;
+    private checkCount;
+    private checkWidth;
+    private decodeKeyToken;
+    private parseValueToken;
+    private findClosingQuote;
     private expandPaths;
     private isExpandable;
     private deepSet;