Chris Van Emmerik

@arcanis Yes, I suppose that is another drawback that should be added. Is this concern due to a performance hit or something else? The Javascript code would only be executed...

@arcanis Hey just following up on this. Can you tell me how likely it is that this [PR](https://github.com/yarnpkg/yarn/pull/7284) will be accepted anytime soon? The reason I am asking, is that...

@stragz How about this? ``` getInputProps={({ openMenu }) => ({ value: "Block", label: "Storage Type", placeholder: "Select Storage Type" })} ```

@stragz That is similar to how I have been using it. I also bind the onChange event to handleStateChange and any external onChange needed. I think part of the problem...

@stragz Here is some code I extracted/adpated from one of my redux applications. It is a little messy but might give you some direction. https://codesandbox.io/s/hardcore-curie-pxcll?fontsize=14

@stragz Ooops. That is just a typescript interface ``` export interface SelectItem { value: any; label: string; type?: any; item?: any; } ``` Also take some of the comments with...

@stragz If you can make a code sandbox reproduction I could take a look. The label state should be handled by the underlying MUI component, so you may need to...

@techniq @mtnori This is close to being ready. I did notice 1 JS warning on the 'with custom adornments' example. Once that is fixed (and also check all the other...

@Domino987 I am still getting JS warnings on the following demo examples: - [ ] Basic -> with custom adornments - [ ] Variants -> outlined with custom adornments -...

If someone could submit a PR that doesn't have JS errors or warnings on the examples, we can merge this. I spent some time on this initially but hit a...