povilass

I think there are a couple of problems with disableClearable and freeSolo if both are true you can have an empty value and it allows it. So I guess disabledClearable...

Think real example would be with warning, sync, and async. 1. You have a payment form with multiple text fields, field are normalized on blur and warning would tell that...

Browsers use modules/or will transpile module maybe just add it "import": "./dist/esm/axios.js",?

Well this changed  Kinda destroyed what's use for browser and node platform because axios\dist\node\axios.cjs Got this  And axios\dist\axios.js got this  So this change must be reverted....

1. reduxForm returns initialize to InjectedFormComponent which actually know the name of the form. 2. To initialize value on the field is not optimal because you gonna hit multiple events...

I have experience in "far away" from and my forms are even interpreters+wizards. Probably you just don't know how to solve you know example. When you got interpreter forms defaultValue...

No example, no use case, at this moment looks like you miss use API and it renders components you don't want which is caused by you. Make example what you...

probably should be called fromFormat -> parse parse('1000.000-e', {format: '', groupSeparator, ...etc}) parse('1000.000-e')

Augmentation works, you are doing it wrong [codesandbox](https://codesandbox.io/s/material-ui-issue-forked-zr4sk?file=/augmentation.d.ts). You need to import interface with augmentated type, same goes for Badge. ``` import { ButtonPropsColorOverrides } from "@material-ui/core/Button/Button"; declare module "@material-ui/core/Button/Button"...

The component uses only some colors from the palette which are type of PaletteColor only. So maybe it makes sense that those colors should be included in this array. Look...