Dominik Moritz
Dominik Moritz
For independent clients, it might make sense to maintain them separately and have a page with links similar to https://vega.github.io/vega-lite/ecosystem.html.
Should switch to https://github.com/duckdb/duckdb-rs/pull/373 once it's released.
Thanks for the issue. Do you think you can send a pr to fix it?
Do you want data from a Vega signal or a Vega-Lite selection? For the latter, we have https://github.com/vega/vega-lite/issues/1830.
I don't think the axe warning is specific to this example. You can add descriptions through the aria attributes in Vega.
This doesn't have anything to do with nearest. You should be able to set `description` property (https://vega.github.io/vega/docs/marks/) which should be exposed to a screen reader.
Oh, I see. So the issue is that you cannot set `description` for the mark created by the nearest transform? Maybe it should set aria-hidden by default since it's only...
Can you see whether you can modify the Vega to change the aria property of the nearest mark in SVG? I think this needs to be done in Vega.
Interesting. This seems to be a problem in Vega, not Vega-Lite ```json { "$schema": "https://vega.github.io/schema/vega/v5.json", "background": "white", "padding": 5, "width": 200, "height": 200, "data": [ {"name": "foo"} ], "scales": [...
https://github.com/tobymao/sqlglot could be an interesting experiment to build a rest server that proxies queries to another database. I'm sure it's still tricky because of data loading but worth a try.