Dominik Moritz
Dominik Moritz
@starry97 Could you have a look at this?
@DhananjayPurohit Awesome. Essentially, the idea is that we want to share the dev config among projects. This means that we don't check in the configs but instead they get pulled...
world-110m.json looks like it could be from https://www.jsdelivr.com/package/npm/world-atlas?version=1.1.4&path=world (https://github.com/topojson/world-atlas).
This is just a color palette/scheme, no?
Ahh, I was looking at it on my phone. This would be a great addition, indeed.
Wouldn't the light theme just need to set the background color to white instead of transparent?
Huh, the renderer must be adding a config in dark mode then.
I think this is an issue with vscode. They just import a package from nteract, though, iirc. So you'll probably have more success with the source.
Imagine we have the following versions ``` 1.3.0 1.3.1 1.3.2 2.0.0 2.1.0 2.1.1 2.1.2 2.1.3 2.2.0 2.2.1 2.2.2 2.2.3 ``` In Vega-Embed we figure out whether a spec is supported...
We use https://github.com/vega/ts-json-schema-generator to generate the schema (at least for Vega-Lite) so I think it could make sense to update that when tooling (like vscode and Ajv)are updated.