[SelectField] Port component

[oliviertassinari]

• Component
• Tests (at least unit tests)
• Docs
• Demo
• Composability Proposal: TextField as a Composable component for various field types #2416

I have gathered some though around things we could implement: #4891 (comment).

[damianobarbati]

Any news on this? When will SelectField make it into next alpha? :)

[jcheroske]

Not nagging, but this would be awesome to get in @next

[dcworldwide]

I reviewed my codebase, I could switch to next if this component was available. Hopefully someone smart from the community with some spare time can help us out :)

[damianobarbati]

@dcworldwide me too on about 6 projects, ready to move if @next gets a boost in development xD
I'd really like to contribute but I'm far from being able to do it.

[chyyran]

I'm building my app from ground up using @next so I'm waiting on SelectField, for now I'm using an html <select> until then.

[tkostus]

The way I worked around this (not only some components are missing in 1.x but I have also had issues with components in 0.x branch) was building material-ui 0.x locally and publishing to npm under a new name. I then npm install'ed it beside material-ui@next. Best of both worlds (if you can swallow increased bundle size...) :)

This of course allows you to mix and match components from 0.x and 1.x - so you get not only Select Field but all other components that are not yet ported and can switch to 1.x where useful (e.g. Table component which is awesome in 1.x).

Nonetheless, can't wait for SelectField in next!

[justinmasse]

I'm also having this issue @tkostus. Any chance you can share the npm module you created?

Really tricky situation because the software we're developing right now needs the updated, however missing so many components is also problematic...

[tkostus]

Ya sure, I called it material-ui-effco. Version I based it off was 0.17.3; I didn't have a reason to update it so far. Hopefully this will do the job for you. If you need more recent version I can rebuild it.

This is probably obvious, but just to avoid potential confusion: you will need to wrap your topmost component in MuiThemeProvider twice - once for each package.

[npramod]

@tkostus - Thanks for the workaround!

[oliviertassinari]

@justinmasse If you are using yarn, you can simply alias the two versions.

[swerky]

Hi, any news of a DropDownMenu or a SelectField ?

[the-simian]

@swerky I am working on a basic component right now: #7678

[vladimirpekez]

Our team is using v1 beta and we really miss selectfield - I guess v1 adoption will skyrocket after selectfield and date/time pickers ports are merged. Even breaking changes afterwards are fine :)

[damianobarbati]

+1

[Sharlaan]

Here a basic SelectField implementation, 100% composed with Material-UI v1 components (TextField, Menu & MenuItem)

But i feel these base components are quite limited in terms of functionality customisation. For example:

• TextField can't accept anything but string, so forget about displaying Chips ...
• i didnot find how to add a checkbox on MenuItem while keeping the "selected" functionality

[kybarg]

@Sharlaan Here is select input implementation #6301

[Sharlaan]

@kybarg this one is closed, and @dummerbd seemed to want to wrap a native select html5 component, which extremely limited for customisation imho.

Maybe did you meant this thread #7632 ?
Sounds great work so far, but (didnot tested) i'm wondering if this implementation is flexible enough to manage ANYTHING as children (ie Chips or complex composiitons), or also custom selectionsRenderer for multiple selections with custom elements instead of plain boring value text(s) ?

[5angel]

Subscribing to this thread, selectField is the only piece I need to migrate projects to v1

[oallouch]

My heart was beating when I saw the beta 7 was out.
Maybe next time :)

[sabatsu]

+1
thx