Export more types

[michael-land]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

These types are very useful when integrated with other form libs or build on top of Date Input

// current
import { DateRange, RangeInput } from '@material-ui/pickers/src/DateRangePicker/RangeTypes';
import { BasePickerProps } from '@material-ui/pickers/src/typings/BasePicker';

// expect
import { DateRange, RangeInput, BasePickerProps } from '@material-ui/pickers';

Describe the solution you'd like
A clear and concise description of what you want to happen.

Export types such as BasePickerProps, DateRange, RangeInput

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[oliviertassinari]

What's your use case?

[dmtrKovalenko]

It was done in the next branch. We reexported all the Props for all the components.

[oliviertassinari]

@dmtrKovalenko should we export or not the types of the private components that we don't allow to override with theme.props? If we don't want to export them, do we?

[dmtrKovalenko]

No, but BasePickerProps are actually shared props between all public root components, so we export them

[oliviertassinari]

So we can close? :)

[dmtrKovalenko]

I`d like to make sure everything is exported, and then close it

[oliviertassinari]

@xiaoyu-tamu Could you try the next version out (v4.0.0-alpha.7)? :)

[michael-land]

@xiaoyu-tamu Could you try the next version out (v4.0.0-alpha.7)? :)

Thanks. I will try the next version when it release.

v4.0.0-alpha.7 was released on May 6th.

[oliviertassinari]

@xiaoyu-tamu Did you try v4.0.0-alpha.8?

[michael-land]

Yes, it works👍👍👍