[AutoComplete] Fix overriding TextField value and onChange prop

[avocadowastaken]

Fix for another regression caused by #6497.

• PR has tests / docs demo, and is linted.
• Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
• Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

[oliviertassinari]

I'm not sure to understand the use case for that change. Don't we want user to override those values?

[avocadowastaken]

I'm not sure to understand the use case for that change.

E.g - Spreading props from redux-form fields.

Don't we want user to override those values?

If so - its a breaking change.
I already fixed it on my side but still it looks like a footgun cause devs can accidentally break internal AutoComplete functionality.

[oliviertassinari]

Thanks for providing more detail. Alright, I guess we could make an exception for those two values as they are quite idiomatic in the React world and reduce the breaking change potential.

[oliviertassinari]

Could you add a comment for the why? Thanks

[avocadowastaken]

Done 👍

Is there anything else?

[oliviertassinari]

@umidbekkarimov Thanks.

[antoinerousseau]

handleChange could call props.onChange if set

edit: sorry no, that would be a breaking change too