NaN in JSON is not parsed correctly

[pavel-kirienko]

Per the JSON specification, NaN floats cannot be represented natively, so many encoders substitute NaN with null. One would expect PJ to handle null values in JSON input as NaN for compatibility with this common case. Instead, we get this:

The JSON doc I used is:

{
  "1252": {
    "timestamp": {
      "microsecond": 0
    },
    "value": {
      "current": {
        "ampere": null
      },
      "voltage": {
        "volt": 24.852617263793945
      }
    }
  }
}

[facontidavide]

I updated the JSOn parse and I think this fixed the issue

[pavel-kirienko]

@facontidavide Thanks! But the issue is still there though :D

[facontidavide]

sorry to hear that. I will try to address it in the next release

[facontidavide]

I have just tried and it works just fine

Closing not being reproducible