Kanit Wongsuphasawat
Kanit Wongsuphasawat
One natural way to support this in an automatic fashion is to allow setting the scale `domain` to be based on multiple fields [like in Vega](https://vega.github.io/vega/docs/scales/#multi-field-data-references). We may then include...
Because it’s way harder to implement than equal aspect ratio. You need to add extent transform, wire signals, etc. for a feature that is unclear if it is gonna be...
For context, I'm planning to use this when one registers a custom format function (e.g., a wrapper to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RelativeTimeFormat), and only uses the formatter when it exists.
For now, I'll make Vega-Lite only output certain custom formatType only if the formatType is also registered with Vega-Lite. https://github.com/vega/vega-lite/pull/6055/files#diff-6a66b8be2cdddd8881db273ef61ff401R77 This means that users need to register custom format function...
Great discussion everyone. Here are some replies for subtopics: > (@jheer) I would also assume that a default order (numerical or lexicographic) is applied if an explicit sort is not...
@jheer @jwoLondon -- I agree that ordinal itself aligns well with our teaching material and I agree that breaking changes ~~can be annoying~~ should be avoided. Here are my further...
@arvind @jheer @jwoLondon -- Let me reiterate my last comment. > With these reflections, we could consider these options for the public API: > a) Keep all the types as...
Right now, I'm leaning toward keeping the status quo given the interval term is probably too confusing anyway. That said, we should look into requiring type less https://github.com/vega/vega-lite/issues/6636.
FWIW, as I make type optional and remove unnecessary ones, I notice that "ordinal" is a source of confusion even among our team. For example, there are several examples that...