Convert between CBOR, CDN (CBOR-EDN), and JavaScript values — with CDDL validation

indent 2 spaces 4 spaces Tab Compact Pretty-print indentation; Compact emits single-line output and ignores the comment / split / inline / concatenation options inlineLeafContainers Keep arrays, maps, and (_ ...) chunks on one line when they contain no nested array/map and every entry fits on a single line commas comma trailing none Separators between array/map elements: commas, commas with a trailing comma after the last element, or spaces only comments strip c-style cdn-style Style to normalize comments to — emit none (strip), // line / block comments (c-style), or # and / … / (cdn-style). Only consulted when preserveComments (right) isn't true encodingIndicators auto always never When to append encoding-width indicators (_0…_7, _i): only for non-canonical encodings (auto), on every item (always), or never intFormat decimal hex octal binary Numeric notation for integers: decimal (42), hex (0x2a), octal (0o52), or binary (0b101010) floatFormat decimal hex app-extension Notation for floating-point values: decimal (1.5), C99-style hex (0x1.8p+0), or the float'...' app-extension bit pattern (float'3e00') bstrEncoding hex base64 base64url Encoding for byte string literals: h'…' hex, b64'…' base64, or b64'…' with the base64url alphabet sqstr printable-string string none Whether to prefer single-quoted '…' form for byte strings: when the bytes are valid UTF-8 with no control characters (printable-string), whenever they're valid UTF-8 (string), or never — always fall back to bstrEncoding above (none) splitNewline Split text strings at newline characters using string concatenation ("line1\n" + "line2") splitCdn Re-format text strings whose content parses as CDN (a JSON superset) by splitting them with concatenation and structure-aware indentation appPrefix Use app-prefix notation (app-string, e.g. DT'2023-01-01T12:00:00Z', ip'192.0.2.42'; or app-sequence) for known tags instead of raw tag notation like 1(1672574400) modernConcat Render preserved + concatenation as t1<<"a", "b">> / b1<<…>> app-sequence notation (draft-ietf-cbor-edn-literals-27 §3.5) instead of "a" + "b". No effect unless preserveConcatenation (right) is on modernStreamSyntax Render indefinite-length strings as ilts<<"a", "b">> / ilbs<<…>> app-sequence notation (draft-ietf-cbor-edn-literals-27 §3.6) instead of the legacy (_ "a", "b") streamstring form

preserveAll Turn every option below on or off at once preserveBlankLines Keep a blank line between array/map entries (or (_ ...) chunks) that had one in the input preserveComments Keep comments from the input and emit them in the formatted output preserveNumberFormat Keep integer/float literals in their original source spelling (0xff, 0o377, 1.50, 1.5_1) instead of normalizing them via encodingIndicators/intFormat/floatFormat (left) preserveByteString Keep non-concatenated byte string literals (h'…', b64'…', b32'…', h32'…', '…') in their original source form instead of re-encoding them via bstrEncoding (left) preserveRawString Keep raw backtick text strings in their original source form instead of converting them to double-quoted strings preserveConcatenation Keep + string concatenation boundaries from the input ("a" + "b") instead of joining the parts into one literal preserveAppPrefix For values written as prefix`...` or prefix<<...>> (e.g. DT`...` or DT<<'...'>>), or a non-canonically spelled prefix'...', keep that exact notation instead of normalizing it. No effect when appPrefix (left) is off