Serializing NaN results in non-JSON compliant text

[DrFriedParts]

When serializing numeric properties of classes that, for example, divide by zero, the result is NaN, breaking the JSON output.

{ "InvalidCalculatedProperty" : NaN }

I'd recommend switching to string type in this case:

{ "InvalidCalculatedProperty" : "NaN" }

...or, perhaps, throwing an exception.

Anything else, but the current output isn't valid.

Thank you for this amazing library. Keep up the great work. Cheers! -Jonathan

[JamesNK]

Write a JsonConverter for float/double to make NaN safe if this is important for you.

[brugidou]

The problem is that NaN (and infinity) values in float/double are not valid JSON values. Deserializing the JSON from any other application will simply not work... can we reopen this issue?

[warappa]

+1

@JamesNK: Shouldn't Newtonsoft.Json try to be fully compatible to http://tools.ietf.org/html/rfc4627 as defined by D. Crockford which means no "NaN" or "Infinite"?

"Write a JsonConverter for float/double to make NaN safe if this is important for you."
I would say it should (must?) be the other way round: Write a converter if you want to distinguish between null, NaN and Infinite.

[jonira]

+1 NaN-values really should comply with the rfc.

[collinsauve]

+1 when a json serializer outputs invalid json - definitely a bug

[collinsauve]

For posterity, here's a very simple example of a JsonConverter for doubles that JamesNK was referring to: https://gist.github.com/collinsauve/6122751

[JamesNK]

This issue was addressed a couple of months ago - http://james.newtonking.com/archive/2013/04/07/json-net-5-0-release-1-net-4-5-biginteger-read-only-collections.aspx