1ab8109892
Before this, if the user were to divide by 0.0, "Infinity" would be returned in the result and the user would get an error: "unexpected type, expected json.Number but got string". Now these values are properly set as Inf values (and also made sure to handle NaN as well).
(cherry picked from commit 590702c497)
29 lines
472 B
JSON
29 lines
472 B
JSON
{
|
|
"tables": [
|
|
{
|
|
"name": "PrimaryResult",
|
|
"columns": [
|
|
{
|
|
"name": "XInf",
|
|
"type": "real"
|
|
},
|
|
{
|
|
"name": "XInfNeg",
|
|
"type": "real"
|
|
},
|
|
{
|
|
"name": "XNan",
|
|
"type": "real"
|
|
}
|
|
],
|
|
"rows": [
|
|
[
|
|
"Infinity",
|
|
"-Infinity",
|
|
"NaN"
|
|
]
|
|
]
|
|
}
|
|
]
|
|
}
|
|
|