Material-ui: [NEXT] Component porting timeline

[galki]

Are there any timelines set for component porting for @next?

I'm specifically interested in AutoComplete, "multiple select" Menu, and TextField Menu.

[stunaz]

I believe menu is available ==> https://material-ui-1dab0.firebaseapp.com/component-demos/menus

[galki]

@stunaz to clarify regarding "multiple select" Menu, current material-ui has a multiple property whereas material-ui@next does not

[oliviertassinari]

We don't have any ETA for porting components. They are ported by people requiring them in production. Anyone is encouraged to help us out. Notice that you can use both the latest and next release tag of npm at the same time on your projet. Material-UI versions do not conflict. Yarn makes it really easy by the way (npm don't make it easy).

Notice that porting the component you are describing is challenging as the implementation we have on the master is far from great (many many open issues). That's at least one week of work.

[oliviertassinari]

I have heard more feedback regarding those components. Same for me, soon or later I'm gonna need them for the project I'm working on. I'm wondering if we couldn't move from the alpha to the beta release once we have them.