Dominik Moritz
Dominik Moritz
I think the title of this issue is wrong. We already support datetime, but not date. See https://github.com/vega/ipyvega/blob/eab0c42de6193061c0df0fa73c366e4bc4ba41e7/vega/utils.py#L69
Vega can read dates as standard strings (as supported by browsers) and timestamps.
> If you don't use additionalProperties: false on the anyOf schema, but instead use it in each of the components of the anyOf, does that work? Actually, the problem is...
hmm, I tried the schema below in https://www.jsonschemavalidator.net/. ```json { "$ref": "#/definitions/BC", "$schema": "http://json-schema.org/draft-06/schema#", "definitions": { "B": { "additionalProperties": false, "properties": { "b": { "type": "number" }, "x": { "type":...
Ahh, I missed that. The thing is that intersection types need `allOf`.
Thank you for the kind words @kayahr. I don't think you have anything to worry about. Btw, I think the issue we are discussing here with intersection types will be...
I don't think we need an option but we could throw an error by default.
We are pre 1.0 so breaking changes are ok. I try to avoid breaking changes that affect a lot of people.
The duckdb version is running in a worker now.
Do you want to send a pull request?