Marija Najdova

@jinqiangg if the select is from years ago, isn't it better to use two `DatePicker` components?

Do you have maybe examples of how it is implemented in other date range picker components?

I'd say we should we wait for upvotes on this one? What do you think @oliviertassinari @eps1lon?

+1 on Option 4 once again :D

I still like the JSX like API better, but considering everything I would be ok if we adopt the prop based API too. This would mean that we can add...

@alansouzati we can't generate the class name based on the sx's prop `maxWidth`, as it can contain integer/px values, percentage etc. In addition it does not support the same API...

I can start on it next week. We have it in our roadmap for this quarter, but happy to start with it earlier.

> Styling the component directly from the theme sounds better than creating new components to me but I do understand that it comes with a cost that we haven't discussed...

> the same here > I solved with > import { Box } from '@mui/material'; > but with that I end up losing the layout style All import should work...

I would recommend importing everything from the root, for e.g. from `@mui/material`. As far as I know there aren't issues like this. We are going to start tackling all blockers...