Is conversion of "\n" to <CR><LF> intentional or a bug?

[onetalltree]

In json_ParseString, a \n is converted to vbCrLf, not vbLF ... this causes extra line break characters to be inserted when round-tripping deserialization and serialization. This seems like a bug.

            Case "n"
                json_BufferAppend json_Buffer, vbCrLf, json_BufferPosition, json_BufferLength

[houghtonap]

The JSON standard is agnostic about line terminators. It considers line terminators white space. Thus an implementation can output different white space and still produce a conforming document. Thus, it's probably not a good idea to depend on your line terminators or other extraneous whitespace staying intact, as you have found, during a round trip operation. Get Outlook for Android

…

________________________________ From: Eric Bell <notifications@github.com> Sent: Wednesday, October 16, 2019 11:50:01 PM To: VBA-tools/VBA-JSON <VBA-JSON@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [VBA-tools/VBA-JSON] Is conversion of "\n" to <CR><LF> intentional or a bug? (#150) Closed #150<#150>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#150?email_source=notifications&email_token=AIKTRA7XCKZJPMWESLJ5SV3QO7OGTA5CNFSM4JBTZF42YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUIOLYBA#event-2719792132>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIKTRA36BRZLC2TAOFPZFELQO7OGTANCNFSM4JBTZF4Q>.

[onetalltree]

Thanks Andrew. After I posted the issue, I saw that this has been discussed previously. I ended up modifying my version of the JSON Converter code to suit my needs.