Jeffrey Heer

It looks like this concerns Vega-Lite or really Vega. If Vega can support Polars then it will be easy to update this API to pass that through, just like other...

Thanks for the PR! We're going to have to think carefully whether or not we want to make this change. A few top of mind concerns that may not be...

Yes, I would like to add types! I think my preferred route is not to port to TypeScript, but rather provide type files included along side the JavaScript source files....

Just thinking through different options, one possibility might be to include an explicit key for window expressions. So alongside `expr` (for normal expressions) and `agg` (for aggregate expressions), we might...

Going to close out for now as we have no planned work here. Where applicable, one option is to perform window operations as part of the initial data loading, then...

I won’t be able to take a closer look at this until next week (the issue is that Mosaic interprets the table name as `schema.table`), but in the meantime here...

Thanks! And, yes, this is a known limitation. Interval interactors are currently only valid over a continuous domain. Long ago in [Vega](https://vega.github.io/vega) I implemented inversion methods for ordinal band and...

I like this! However, we might want to wait on merging for now. I also want to think through some complementary possible changes, such as adding a query queue in...

Ooh, having a reusable set of activation methods (shared across various interactors) sounds like a promising direction. Would be worth enumerating what we think that space of methods should be.

To which I would simply add: - Prefetch on load (i.e. precompute all indexes for individual active views/clauses) Right now individual interactors make their own activation decisions. This conversation is...