Mary McGrath

The raw types would need to be unified before generating the expressions, but that could also be achieved with a map/reduce approach. maybe something like: ```jl read_json_str(json_str) = read(length(json_str) <...

I tried playing with this as it surprised me a bit and I don't see Julia enforcing that behavior with the default constructor. Are we sure we want to do...

Panning and zooming doesn't make sense for all chart types, so my vote would be to keep it opt in. Maybe add a utility to make it easier to opt...

@logankilpatrick those warnings come from the underlying [vega-lite js package](https://github.com/vega/vega-lite/blob/37efa299ed0681c8a48c8e36ccecd69de02b2a2c/src/log/message.ts). I'm guessing this has to do with how IJulia imports/displays vega plots vs the version shipped with VegaLite.jl for the...

`vega-embed` handles the incorporation of the config already, so we'd just need to add the global default to the opts that are passed there. I'm not sure how that plays...

The [themes](https://github.com/vega/vega-themes) are basically pre-packaged config objects to make nice defaults, so they should fit easily into any of these solutions. I don't have an opinion on the api, but...

Just started a PR (#188) for the `spec_utils`

@davidanthoff would you be opposed to trying to replace that functionality on the julia side? We could read in the files and pass them to the `values` field instead of...

@domoritz could you point me to an example/package/project I could reference?

It's a bit clunky, but this may solve the issue: ``` using VegaLite #, VegaDatasets # using Queryverse africa_output= "africa_output.csv" africa = joinpath(".", "africa.topojson") @vlplot( width=800, height=600, projection={typ=:naturalEarth1}, data={ url=africa,...