David Anthoff

This is a bug somewhere in my stack. The ``DataFrame`` you get there should never have a ``DataValue`` in it, it should automatically use ``Missing``. Note that Queryverse in general,...

You need to call ``IteratorInterfaceExtensions.getiterator`` on ``t`` and then iterate over the thing that is returned by that (see [here](https://github.com/queryverse/IteratorInterfaceExtensions.jl#isiterable-and-getiterator)): ````julia t = load(filename, sheet) for row in getiterator(t) @show...

Yeah, that is probably not super consistent... But I use ``collect`` so often, that I just added a method to ``collect``. That in turn then calls ``getiterator`` and the normal...

Uh, that is weird... My best guess is that maybe the version of vega-lite that is used for the save case is somehow old? I should probably update to the...

New version is pending: https://github.com/JuliaRegistries/General/pull/16067. Could you try again once that is registered?

I'll leave this one open, I plan to write a proper user guide chapter on composite plots at some point. I'm just holding off for now because I'm still trying...

So the reason that I still haven't written the composition doc chapter is that I don't like what we have right now... My current thinking on how to clean this...

I think what we really need is a section in the "User Guide" named "composite plots" that just outlines all of the composite options.

No, so the idea would be that QuickVega.jl has a dependency on Vega.jl and VegaLite.jl, and the functions that are defined in QuickVega.jl return instances of either `VLSpec` or `VGSpec`.

So the reason this doesn't work is that I disabled it in https://github.com/queryverse/VegaLite.jl/commit/2e2dfced1edc8e76efb714736d6d23cfb5fc4644. I labeled that commit as "fixing some bug", but I don't remember what the bug was... But...