% JsonNode operator cast true and false literal value to 1 and 0

[cn-care]

import karax / [jjson, kajax, karax]

var option* = %*{
    "backgroundColor": "#404a59",
    "title": {
        "text": "",
        "left": "center",
        "textStyle": {
            "color": "#fff"
        }
    },
    "tooltip": {
        "trigger": "item",
        "formatter": formatter,
        "textStyle": {
            "color": "#fff",
            "fontSize": 12,
            "fontWeight": "normal"
        },
        "padding": [10, 15],
    },
    "geo": {
        "map": "world",
        "label": {
            "emphasis": {
                "show": true,
                "color": "#fff"
            }
        },
        "roam": defaults["roam"],
        "zoom": defaults["zoom"],
        "center": defaults["center"],
        "itemStyle": {
            "normal": {
                "areaColor": "#323c48",
                "borderColor": "#404a59"
            },
            "emphasis": {
                "areaColor": "#2a333d"
            }
        }
    },
    "series": []
}

In many scenes, bool literal value is expected rather than 1 or 0.
Have to set bool value manually as
option["geo"]["label"]["emphasis"]["show"] = true

[moigagoo]

Is it related to nim-lang/Nim#7375?

[ajusa]

I think that this is a solution:

import karax / [jjson, kajax, karax]
import jsffi
var option* = %*{
  "test": true
}
var option2* = js{
  "test": true
}
include karax/prelude
proc render(): VNode =
  buildHtml(tdiv):
    kout option
    kout option2
    kout option2["test"]
setRenderer render

And the output in the console looks like:

{test: 1} //from jjson
{test: true} //from jsffi
true //getting value by key from jsffi

So, use jsffi instead of jjson. Both of them should have similar performance characteristics, but jsffi is part of stdlib now (not sure if existed back when this issue was created) so I would recommend it over jjson. I've successfully used jsffi to create a similar options js object for an external library.

One thing to be careful of though when using it with karax is that

var option2* = js{
  "test": true,
  "test2": "hey now"
} # bad

var option2* = js{
  "test": true,
  "test2": kstring"hey now"
} # good

If you use the first one, then the string is interpreted as a nim string which means it becomes an array of numbers, whereas with the second one it is treated correctly on both the js and the c backends.