Flavien DELANGLE

Opened for review

I opened a PR for the env check because it's trivial to fix and doing it before the release is better For the rest we can do a follow up...

I would love if someday, the data-rich components have a `data` tab on the demo, like [Nivo demos](https://nivo.rocks/bar/) and receives a `data` prop on the demo. The data of `MyDemo.{js|tsx}`...

> There is also a notion of allowing a straightforward demo copy & paste experience. The main downside of the current approach being that it's hard to understand the demo...

Whatevers DX we end up having, I think that one is common enough to justify a doc example :+1: cc @alexfauquette

@oliviertassinari The only problem now is that I must choose between linking to the Rich Tree View or the Simple Tree View doc when I list the features

`date-fns@4` has new APIs for timezone support, this should make this issue doable: https://blog.date-fns.org/v40-with-time-zone-support/ I'm moving it back to "To grooming to discuss the priority

Hi, You can use the `referenceDate` prop to decide what date should be applied when you click on a section. For your usecase, you can just put an hour that...

This relates to [this page](https://mui.com/x/migration/migration-data-grid-v4/#removed-props) TLDR: We removed those events from `apiRef.subscribeEvent` so that only people that need them pay the performance price of setting the event on the HTML...

> Feels inconsistent that we publish cellMouseOver but not cellMouseLeave. I think we just kept the one we were using internally > @flaviendelangle I'm curious about the performance justification, isn't...