Quoted hexadecimal strings like "0x123" are parsed as floats when they should remain strings, violating YAML semantics where quoted strings are string literals.
Noticed the above issue while working on this pr blockblaz/zeam#373 when a YAML scalar is quoted but starts with 0x, zig-yaml parses it as a float rather than leaving it as a string. This violates YAML semantics (quoted values should remain literal strings) and breaks our use case: we need to store validator public keys like "0xaa2a6f…", and our downstream code expects .string but receives .float.
Quoted hexadecimal strings like "0x123" are parsed as floats when they should remain strings, violating YAML semantics where quoted strings are string literals.
Noticed the above issue while working on this pr blockblaz/zeam#373 when a YAML scalar is quoted but starts with 0x, zig-yaml parses it as a float rather than leaving it as a string. This violates YAML semantics (quoted values should remain literal strings) and breaks our use case: we need to store validator public keys like "0xaa2a6f…", and our downstream code expects .string but receives .float.