Dominik Moritz
Dominik Moritz
Switching to type module to support more modern js development. My hope is that this will help with the editor issues and let us update to newer versions of packages.
In ```json { "$schema": "https://vega.github.io/schema/vega-lite/v5.json", "data": {"url": "data/movies.json"}, "repeat": {"column": ["US Gross", "Worldwide Gross"]}, "spec": { "encoding": { "x": {"bin": true, "field": "IMDB Rating", "type": "quantitative"}, "y": { "aggregate": "mean",...
For example, when the user can create a brush, it would be nice to change the cursor accordingly. An interactive mark with a point selection should use a `"cursor": "pointer"`...
https://vega.github.io/editor/#/examples/vega-lite/errorband_tooltip 
fixes #7433 Merge after #7438
In layered specs, legends over the same field should be merged but sometimes are not. See https://github.com/vega/vega-lite/issues/5695, https://github.com/vega/vega-lite/issues/5543, https://github.com/vega/vega-lite/issues/1844#issuecomment-593138857, #6359, https://github.com/vega/vega-lite/issues/3797
Big thanks to @frankelavsky for doing the analysis and writing it up. ## Perceivable issues: * [Many encodings](https://vega.github.io/vega-lite/examples/stacked_area.html) across charts fail WCAG's 3:1 contrast rule. Consider adding borders (or dual...
https://github.com/vega/vega/pull/3686 introduces a new property `aggregate_params` but Vega usually uses camel case. Should we change the name? This was already released in https://github.com/vega/vega/releases/tag/v5.26.0, though.
The defaults are creating line charts with ugly (and potentially misleading) corners.  We should consider changing the defaults to `round` for both.
Consider adding https://github.com/google/tsec. Might need to add https://www.npmjs.com/package/safevalues to satisfy the checks.