Just noting that all these files are not new, this is just the exact same previous components that were defined in a single file, I split them into dedicated files for clarity.

So, the relevant change in this PR (other than splitting files) is creating this FilterToggled component, that handles the filters visibility without having to expose the DataViews context to the consumer. Is that correct?

Can we update the Filters component instead to handle this? When is it useful having a Filters component that doesn't handle it?

Can we update the Filters component instead to handle this?

No we shouldn't because if you want to say render the "Filters" in a sidebar in your own implementation of DataViews, you can't use this with FiltersToggled, FiltersToggled is meant to be used in conjunction with FiltersToggle. The only other alternative is to actually remove FiltersToggle and let users implement it adhoc. I thought it's a nice shortcut for now, so I kept it.

I see. Though In that case, consumers need to create their own "toogle" because FiltersToggle will respond to clicking by changing its style from "pressed" to "not pressed", but the filters will still be visible.

Yes, exactly, and FitltersToggle is already exposed btw, and it just doesn't work on its own.

In other words, either you use both together (FiltersToggle and FiltersToggled) or you don't use any (Filters)