json_ParseString handling of new line (\n)

[zgrose]

I believe the n case in json_ParseString should be changed to append a vbLf instead of a vbCrLf or there should be an option to override the default behavior (I copied the current code into this issue at the bottom).

I noticed this issue when assigning a value to a TextBox.

My JSON was (simplified): { "Prop" : "Foo \r\nBar" }

In the Immediate window this shows
Foo
Bar

But when I assign that value to a TextBox that is MultiLine=True and EnterKeyBehavior=True

Me.TextBox1.Value = jobject("Prop")

the form shows Foo Bar in the TextBox.

If I change the JSON text to be { "Prop" : "Foo \nBar" } it displays properly.
If I change your code from vbCrLf to vbLf it displays properly.

I believe this is also a "truer" conversion for \n

Current code from 4.1.1

            Case "n"
                json_BufferAppend json_buffer, vbCrLf, json_BufferPosition, json_BufferLength
                json_Index = json_Index + 1
            Case "r"
                json_BufferAppend json_buffer, vbCr, json_BufferPosition, json_BufferLength
                json_Index = json_Index + 1

[Sophist-UK]

I would suggest the following:

            Case "n"
                If VBA.Mid$(json_String, json_Index+1, 2) == "\r" Then
                    json_BufferAppend json_buffer, vbCrLf, json_BufferPosition, json_BufferLength
                    json_Index = json_Index + 3
                Else
                    json_BufferAppend json_buffer, vbLf, json_BufferPosition, json_BufferLength
                    json_Index = json_Index + 1
                End If
            Case "r"
                If VBA.Mid$(json_String, json_Index+1, 2) == "\n" Then
                    json_BufferAppend json_buffer, vbCrLf, json_BufferPosition, json_BufferLength
                    json_Index = json_Index + 3
                Else
                    json_BufferAppend json_buffer, vbCr, json_BufferPosition, json_BufferLength
                    json_Index = json_Index + 1
                End If

[timhall]

@zgrose Thanks for raising this issue, @Sophist-UK looks good to me, I'll make this change

[timhall]

(moved to VBA-JSON)

[Sophist-UK]

If the JSON fix was applied and then made it into VBA-WEB from there, then #272 should probably be closed.