Deploy different versions of the editor

[kanitw]

e.g., https://vega.github.io/editor/0.28/

or https://vega.github.io/editor-archive/0.28/

This would be extremely useful for trying a spec with multiple versions to isolate bugs.

[ganeshpatro321]

@domoritz

Do we have any lead on how to proceed with this?

[domoritz]

I don't think we want multiple versions of the editor. Instead, it would be nice if be able to choose the Vega and Vega-Lite versions dynamically, no?

[kanitw]

Instead, it would be nice if be able to choose the Vega and Vega-Lite versions dynamically, no?

That would be better UX. If it is not much more work, we should do it.

I just mention vega editor versions as it's a workaround if the ideal UX is too much work.

[domoritz]

I think it's easier to support multiple versions of Vega than it is to figure out which version of the editor corresponds to a particular Vega version.

[kanitw]

I think it's easier to support multiple versions of Vega than it is to figure out which version of the editor corresponds to a particular Vega version.

For sure! I've run binary search manually several times today to find the right version to revert to. 😐

[domoritz]

Wait, if you need to check vega versions, then you did binary search with a locally deployed editor, right?

[kanitw]

Yes, by checking out tags

[domoritz]

Why? You can just link to Vega and Vega-Lite and use the version you want that way, no?

[kanitw]

Well, it's the same thing if I want to find the newest version that doesn't break to revert to. Still have to do binary search and re-build multiple times. Running yarn to install the version is actually faster.

[domoritz]

I see. Either way, the use case is switching Vega and Vega-Lite versions so I think we should try to automatically load these libraries from jsdelivr (maybe based on the version in the schema?). That doesn't seem too hard and is easy to use.

[domoritz]

Instead, let's do #336