Mattijn van Hoek

Thanks @binste! No rush! Maybe something for version 5.4

That would be great @kindofluke! Here is the explanation page [how to build the docs locally](https://github.com/altair-viz/altair/blob/master/CONTRIBUTING.md#building-the-documentation-locally). There are currently three different requirements pages: 1. [master/requirements.txt](https://github.com/altair-viz/altair/blob/master/requirements.txt) 2. [master/requirements_dev.txt](https://github.com/altair-viz/altair/blob/master/requirements_dev.txt) 3. [master/doc/requirements.txt](https://github.com/altair-viz/altair/blob/master/doc/requirements.txt) I'm...

Gentle ping @kindofluke, did you manage to make a start? I was planning to start working on this as well if you don't mind.

No problem! Completely understandable. If you don't mind, I like to give it a try in coming week as well.

You will have to define this by yourself, but I've heard the request of drilling more often. I personally like to have an example in the docs that can drill/highlight/filter...

Just want to say that it is a very interesting solution @binste! Nice. For another discussion: somehow wished we could facilitate Python users more to surface these internal computed datasets...

Hi @ChristopherDavisUCI! This was discussed in this issue: https://github.com/altair-viz/altair/issues/2759. It would be nice if we can extend and improve Altair by allowing for multiple predicates as part of a condition.

Is this page of help: https://vega.github.io/vega-lite/docs/condition.html?

You are right, it's not really clear from there. Maybe a bit from the Vega docs at this page: https://vega.github.io/vega/docs/marks/#encode. Scroll down to the section on _Production Rules_

Sorry mailinglist. I pressed shift+enter while typing which submitted the issue halfway. I finished the issue using the edit-button.