Tarn W. Burton

The extension is for rendering the graph in a notebook output cell. I think it is still required if you want to do that. I haven't thought about wrapping the...

It can. It is in quicklisp, but probably not used by anyone yet. I haven't put much effort in to documentation yet, but you can see some of the configuration...

You don't need to serialize the JSON. You need to pass the JSOWN style json to `jupyter:inline-result`. ```lisp (jupyter:inline-result (jsown:new-js ("$schema" "https://vega.github.io/schema/vega-lite/v3.json") ("description" "A simple bar chart with embedded data.")...

The JSOWN objects are just alists with a `:obj` head. ```lisp '(:obj ("a" . "A") ("b" . 28)) ```

Its JSOWN style because common-lisp-jupyter is using JSOWN and `inline-result` just passes the contents directly to the message encoder which handles the serialization to JSON since the Jupyter protocol is...

Because of the switch to the shasht JSON library this has changed a bit. ``` (jupyter:inline-result '(:object-alist ("$schema" . "https://vega.github.io/schema/vega-lite/v4.json") ("description" . "A simple bar chart with embedded data.") ("data"...

I've switched to shasht so the jsown style encoding won't work anymore. In shasht JSON objects are represented by hashtables, `(:object-alist ("fu" . 1))` or `(:object-plist "fu" 1)`. JSON arrays...

shasht does have a way to do this (`shasht:*write-alist-as-object*`), but it is not going to work in this case because the JSON that you are passing to `inline-result` is just...

Well you could write a recursive function that looks for alists and does `(cons :object-alist my-alist)` on them. But more specifically, how are you generating the data?

alists are a fundamentally ambiguous, but convenient data structure in my opinion. My reading of your documentation and code seems to indicate thatt that you are supporting two different JSON...