Support empty string as valid value on AutoComplete component

[blitzbohne]

Currently the problem is that the AutoComplete throws a warning if none of the options is matched due this pull request:

#20235

However it is now impossible to set an empty value aka "cleared" status on an AutoComplete as it always throws this warning which lets you go crazy with many AutoCompletes.

However providing a null value obviously transforms the component into an uncontrolled input and throws the React Error so one has no choice as of now except adding an empty option to the options list which makes no sense.

• I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

I'd strongly advise to either revert this pull request: #20235 OR at least extend it to also check and allow for empty string if the Auto-Complete component is clearable.

[blitzbohne]

Referencing @igorbrasileiro here as he originally created that pull request.

[support]

👋 Thanks for using Material-UI!

We use GitHub issues exclusively as a bug and feature requests tracker, however,
this issue appears to be a support request.

For support, please check out https://material-ui.com/getting-started/support/. Thanks!

If you have a question on StackOverflow, you are welcome to link to it here, it might help others.
If your issue is subsequently confirmed as a bug, and the report follows the issue template, it can be reopened.

[blitzbohne]

@oliviertassinari Why has this been closed? It is not a support request how could it be? Did I do anything wrong in the template?

[kaguya3222]

This is funny that we can't set empty string as value :)