Dominik Moritz

I think vg3 should be in master. The current master does not support Vega 3 or Vega-Lite 2. I'm happy to not do this if there is a good reason.

It would be great to collapse axes.

We could probably just pass the auth token to the editor frontend and make the backend stateless. This would mean that we could do the graphql queries from the frontend...

Switch to vega-lite-dev-config

2

See https://github.com/vega/vega-embed/blob/master/package.json#L50 for an example. The advantage would be that we can share the same dev config across all projects.

Semantic versioning is incorrect?

3

2.1 should link to 2.2.0 once it is released but it will instead point to the latest 2.1 release.

Another example

1

This example by @jamesbornholt looks like a nice test case for Vega-Label. Is it okay if we use it with attribution?  ```json { "$schema": "https://vega.github.io/schema/vega-lite/v3.json", "width": 500, "height": 300,...