Suspect a bug: Getting exceptions on parsing valid json with null/blank values.

[Ben Frando]

Exception thrown when parsing null/blank values:

executing: (parse-message “{\”status\”:{}}” “testMsg”)

exception: Caused by: nexj.core.scripting.ParserException: Unexpected token “}”. (err.parser.unexpectedToken)

testMsg.message: attached

=============================

The following parses fine:
executing: (parse-message “{\”status\”:{\”code\”:200,\”reason\”:\”ok\”}}” “testMsg”)

; #<TO<testMsg, @1757836584>(

status=TO<testMsg, @1026935509>(

reason=”ok”,

code=200

)

)>

0

[Ben Frando]

testMsg.message:

<Message aggregation=”random” format=”JSON” lax=”true”>
<Parts>
<Message aggregation=”random” lax=”true” name=”status”>
<Parts>
<Value name=”code” type=”integer”/>
<Value name=”reason” type=”string”/>
</Parts>
</Message>
</Parts>
</Message>

0

[Ed Shaw]

Ben, you are totally right. This is a bug. The good news is that is is already squashed. 🙂 What version are you running? I ran your tests on the latest and got the following results.

Scheme

; I created some tests for null non require parts to check it out (define m (message (: :class "testMsg") (: status (message)))) ; #<TO<testMsg, @1519941089>( ; status=TO<, @906137539>() ; )> (define fm (format-message m)) ; "{\"status\":{}}" (define pm (parse-message fm "testMsg")) ; #<TO<testMsg, @593285382>( ; status=TO<testMsg, @1566567300>() ; )> ; Now your examples (parse-message "{\"status\":{\"code\":200,\"reason\":\"ok\"}}" "testMsg") ; #<TO<testMsg, @1985421550>( ; status=TO<testMsg, @768626727>( ; reason="ok", ; code=200 ; ) ;)> (parse-message "{\"status\":{}}" "testMsg") ; #<TO<testMsg, @1757503610>( ; status=TO<testMsg, @1256240429>() ;)>

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

; I created some tests for null non require parts to check it out (define m (message (: :class "testMsg") (: status (message)))) ; #<TO<testMsg, @1519941089>( ;   status=TO<, @906137539>() ; )> (define fm (format-message m)) ; "{\"status\":{}}" (define pm (parse-message fm "testMsg")) ; #<TO<testMsg, @593285382>( ;   status=TO<testMsg, @1566567300>() ; )>   ; Now your examples (parse-message "{\"status\":{\"code\":200,\"reason\":\"ok\"}}" "testMsg") ; #<TO<testMsg, @1985421550>( ;   status=TO<testMsg, @768626727>( ;      reason="ok", ;      code=200 ;   ) ;)> (parse-message "{\"status\":{}}" "testMsg") ; #<TO<testMsg, @1757503610>( ;   status=TO<testMsg, @1256240429>() ;)>

0

[Ben Frando]

It’s 6.1.1.14 – Opal SP1 HF14

0

[Ed Shaw]

This was fixed, I believe, in Jade.  For sure in Ruby.

0

[Ben Frando]

Thanks!

0

[Author]

Posts