gjmcn / to-vega Goto Github PK

this looks awesome. Do you want to add a link to to-vega at https://vega.github.io/vega-lite/applications.html? Just send us a PR.

So could write e.g.

tv.setPlot(sp => vegalite(sp))

I.e. no need to use this.spec and hence, can use arrow function.

I'd like to see whether to-vega could be a recommended way to write Vega-Lite in JS. To recommend it fully, we need to make sure that it is a) stable and b) feature complete. I was wondering what your thoughts on completeness are. Are there things expressible in Vega-Lite but not in to-vega? How do you plan to ensure feature compatibility in the future? Do you think it would make sense to generate the API automatically from our Typescript typings (like Altair is generated from the JSON schema).

See discussion in vega/vega-lite#2280

vegalite = require("vega-embed@3")

You get tooltips and action links this way.

Right now, marks (e.g. bar) and encodings (e.g. x) are in the same namespace. I think it would be good to separate them like in Altair.