Mihaela Mihaljevic
bf069fad39
PureYAMLJSON is a separate library product layered on the core engine. JSON is a subset of YAML 1.2, so the existing parser already reads both into one value tree; this product adds the missing half and the value-level policy: - JSON.Writer: a pure-Swift RFC-8259 serializer (no Foundation; WASI-clean), pretty or compact, rejecting non-string keys and non-finite numbers. - JSON representability rules expressed in PureYAML's own Validation framework: mappingKeysAreStrings and numbersAreFinite join the core mappingKeysAreUnique. - JSON.Validator: the representability rule set plus issues(for:)/isRepresentable. - JSON.Convert: standalone convert(_:to:) with the round-trip law (parse -> validate representability -> emit -> re-parse must equal the source). To JSON rejects complex keys and non-finite numbers; to YAML rejects duplicate keys, which are legal in JSON but not in YAML. 19 tests cover the writer, the rules, and both conversion directions including the dual-rejection edges. Carved out of the catch-all Sources/Tests paths via exclude so the core PureYAML target is unchanged.
15 lines
697 B
Swift
15 lines
697 B
Swift
import PureYAML
|
|
|
|
public extension PureYAML {
|
|
/// Strict-JSON support layered on the shared YAML value tree: a pure-Swift
|
|
/// RFC-8259 emitter, JSON-representability rules expressed in PureYAML's own
|
|
/// validation framework, and a standalone YAML <-> JSON converter.
|
|
///
|
|
/// JSON is a subset of YAML 1.2, so the parser PureYAML already ships reads both
|
|
/// JSON and YAML sources into the same ``Model/Value`` tree. This module adds the
|
|
/// missing half (emitting that tree as JSON) plus the value-level checks that
|
|
/// decide whether a tree is representable as JSON at all. Anchor file; concrete
|
|
/// types live in the sibling `JSON.*` files.
|
|
enum JSON {}
|
|
}
|