Flavien DELANGLE comments

Results 521 comments of


                                            Flavien DELANGLE

[dialog][alert dialog] Add `renderMode` prop to `Backdrop` part

Not a huge fan of the prop name. I saw quite a lot of `renderXXX` props that were render props (`renderItem={item => }`). So I wouldn't use the same type...

[dialog][alert dialog] Add `renderMode` prop to `Backdrop` part

I don't have a very good proposal :/ `nestedDialogRenderMode` is very verbose

[scheduler] Add visibleResources / defaultVisibleResources / onVisibleResourcesChange props

@copilot Please fix the CI

[scheduler] Add visibleResources / defaultVisibleResources / onVisibleResourcesChange props

@copilot The CI is still red

[scheduler] Add visibleResources / defaultVisibleResources / onVisibleResourcesChange props

@copilot please fix the CI, and re-run it before commiting...

[scheduler] Add visibleResources / defaultVisibleResources / onVisibleResourcesChange props

@copilot please use an object instead of a Map to represent the visible resources (`props.visibleResources`, `props.defaultVisibleResources` but also `state.visibleResources` and all the selectors and usage of this state).

[RichTreeViewPro] dataSource does not re-fetch root items when getTreeItems callback changes

@noraleonte is having a look at the issue 👍

[pickers] `DateTimeRangePicker` throws error with `format` prop in MUI X Pro v7.11.0

I'd be interested to have a reproduction case here before applying a fix. I agree that the failsafe proposed by @michelengelen make sense, but I would like to understand why...

[pickers] `DateTimeRangePicker` throws error with `format` prop in MUI X Pro v7.11.0

> Applying the suggested fix ruins the UX of the data selection, hence, I'm not sure if this is the best solution. 🤔 Is this the fixed you just merged...

[pickers] `DateTimeRangePicker` throws error with `format` prop in MUI X Pro v7.11.0

No problem keeping it simple for now :+1: