For the Explicit Block Mapping,why yamlbeans implements the key length < 128 ?

[Czytx]

In the YAML Version 1.2 specification (http://yaml.org/spec/1.2/spec.html#id2798057),for the Explicit Block Mapping,having the following specifications: If the “?” indicator is omitted, parsing needs to see past the implicit key, in the same way as in the single key: value pair flow mapping. Hence, such keys are subject to the same restrictions; they are limited to a single line and must not span more than 1024 Unicode characters. why yamlbeans implements the key length < 128 ? return length < 128 && (event.type == ALIAS || event.type == SCALAR && !analysis.empty && !analysis.multiline || checkEmptySequence() || checkEmptyMapping());

[NathanSweet]

Looks like YamlBeans is wrong, a PR is welcome.

-Nate

On Wed, Sep 13, 2017 at 4:17 AM, Czytx [email protected] wrote:

In the YAML Version 1.2 specification (http://yaml.org/spec/1.2/ spec.html#id2798057),for the Explicit Block Mapping,having the following specifications: If the “?” indicator is omitted, parsing needs to see past the implicit key, in the same way as in the single key: value pair flow mapping. Hence, such keys are subject to the same restrictions; they are limited to a single line and must not span more than 1024 Unicode characters. why yamlbeans implements the key length < 128 ? return length < 128 && (event.type == ALIAS || event.type == SCALAR && !analysis.empty && !analysis.multiline || checkEmptySequence() || checkEmptyMapping());

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/EsotericSoftware/yamlbeans/issues/84, or mute the thread https://github.com/notifications/unsubscribe-auth/AAafWlvfv4EB_JUws9NYNFPc0j2juMcBks5shztVgaJpZM4PVfVd .