You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An interesting edge case, I discovered that explorer will discard trailing zeroes from number tokens in the JSON document.
For example, the object { "value": 12345.0000 } will be shown as 12345 in explorer.
This appears to be an issue with the front-end code that renders out the JSON document with syntax highlighting.
Chrome/Edge devtools show that the Cosmos endpoint is returning the extra digits in the raw payload.
As you may be aware, the decimal type in C#/.Net will preserve trailing zeroes like these - and using the Cosmos SDK will correctly roundtrip these values (it's just explorer which is misleading).
The text was updated successfully, but these errors were encountered:
Hi Cosmos Team,
This relates to a Core/SQL cosmos instance.
An interesting edge case, I discovered that explorer will discard trailing zeroes from number tokens in the JSON document.
For example, the object
{ "value": 12345.0000 }
will be shown as 12345 in explorer.This appears to be an issue with the front-end code that renders out the JSON document with syntax highlighting.
Chrome/Edge devtools show that the Cosmos endpoint is returning the extra digits in the raw payload.
As you may be aware, the
decimal
type in C#/.Net will preserve trailing zeroes like these - and using the Cosmos SDK will correctly roundtrip these values (it's just explorer which is misleading).The text was updated successfully, but these errors were encountered: