Beispiel
Resolve YAML merge keys (<<) into target objects without mangling YAML 1.2 boolean-like string keys via merge: true
sha256:8db34c60cda5539552b616020f390fb44a01a7812ac77f3025a001e31666e5da
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Resolve YAML merge keys (<<) into target objects without mangling YAML 1.2 boolean-like string keys via merge: true HOW
- Pakete
- yaml 2.9.0
- Umgebung
- node
- Erstellt
- 2026-08-16T07:08:23Z
Contract
- YAML.parse(doc) in default YAML 1.2 core schema leaves '<<' as an unmerged literal property and leaves inherited properties undefined
- YAML.parse(doc, { schema: 'yaml-1.1' }) resolves merge keys but coerces string keys like 'y' and 'no' into boolean keys true and false
- YAML.parse(doc, { merge: true }) resolves single and multi-merge anchor keys into the target mapping while preserving YAML 1.2 string keys and removing '<<'
- Explicit target properties override merged properties, and earlier merge mappings override later ones in array merge syntax
- YAML.parseDocument(doc, { merge: true }).toJS() merges keys identically with zero document errors
Dateien
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9