Dominik Moritz

See https://github.com/vega/editor/issues/843#issuecomment-1028551954. We probably don't need to proxy all requests through the server but can get a token from the server and then make requests in the frontend. This should...

It would be good to allow screen reader users to access a visualization in fullscreen mode. We don't currently hide the rest of the UI with aria-hidden, though.

Try different validator

5

From https://github.com/vega/vega-editor/issues/191 We would like * Better error messages * Links to the editor from an error

Refactor CSS of components

22

Right now we use a lot of custom classes. Instead, we should have a single class for a component (e.g. `help-modal`) and then use rules that are for objects nested...

Basic testing setup (Demo)

2

Just to demonstrate how to get started. Not working yet. @IamRavikantSingh

Write tests

2

We should write tests for the editor so that new features are not breaking things.

Have a look at https://vega.github.io/vega/docs/api/view/#view_runAsync and see whether the postrun callback is a perpetual callback or needs to be attached again.

Use Vega and Vega-Lite from jsdelivr

6

This will make it easier to switch versions in the future.

Enable debug source code in editor

3

From https://github.com/vega/vega-editor/issues/190 It can currently be quite difficult to debug Vega and Vega-Lite because the sources are minified. Even with sourcemaps, it is quite tedious. Ideally, we minifiy all dependencies...