Dominik Moritz

Ahh, so the problem is that the scales are defined inside each cell (which makes sense since they should be independent) but the header is defined outside and references a...

Hmm, I wonder why Vega-Lite does not automatically also make the axes independent.

Something is wrong with layers inside facet. With just facet, it works. ```json { "data": { "url": "https://vega.github.io/vega-datasets/data/seattle-weather.csv" }, "facet": { "column": { "field": "weather", "type": "nominal" } }, "spec":...

As soon as we use a layer, it breaks: ```json { "data": { "url": "https://vega.github.io/vega-datasets/data/seattle-weather.csv" }, "facet": { "column": { "field": "weather", "type": "nominal" } }, "spec": { "layer": [{...

Ahh, what you want is this (move the resolve one up). ```json { "data": { "url": "https://vega.github.io/vega-datasets/data/seattle-weather.csv" }, "facet": { "column": { "field": "weather", "type": "nominal" } }, "spec": {...

I don't think I really want to support faceted dual-axis charts so I'm inclined to just add a warning and drop the resolve in the original spec. @kanitw @arvind what...

I see. Maybe it's not too hard to support it. It just wasn't one of the things I had tested when I wrote the resolve code.

> Will faceted dual axis charts be supported in the future? Yes, after the 4.0 release, I plan to spend some time on the dataflow code to fix issues like...

Yeah, I was both excited and horrified by the announcement. I'm not sure yet what kind of api they will provide but we use a lot of internal apis that...

Arthur > I know it's extremely early to ask questions about typescript-go, but doesn't porting it to Go basically kill type checker, LSPs and tsserver community integrations? Will it be...