New line in string raises decode error about jason HOT 2 CLOSED

According to the JSON spec (RFC 8259) control characters (including newline character - U+000A) must be escaped.

The representation of strings is similar to conventions used in the C
family of programming languages. A string begins and ends with
quotation marks. All Unicode characters may be placed within the
quotation marks, except for the characters that MUST be escaped:
quotation mark, reverse solidus, and the control characters (U+0000
through U+001F).

The current implementation strictly follows the spec and does not allow unescaped newlines inside strings. It's up to debate if we should follow the spec here, I think we should. But we also should at least mention this in the "Differences to Poison" section of documentation.

There are also explicit tests to refuse such behaviour in the JSON Test Suite.

from jason.

Thanks for the explanation! Yes, I also think that we should follow the spec strictly.

from jason.