[AutoComplete] onChange being called when value is duplicated

[ryjogo]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

According to the documentation:

Callback fired when the value changes.

However, it seems that when the value is a duplicate - the onChange hook is ran.

Expected behavior 🤔

onChange should not run, as the value has not changed?

Steps to reproduce 🕹

https://codesandbox.io/s/vibrant-surf-ztbsl

Steps:

1. send a freesolo item, i.e. "hello" press enter
2. send a second freesolo item, "hello" press enter
3. observe the chip is not added, however in the console the onChange event happens..

Context 🔦

I would like to send my chip updates as tags to a RESTful API:

switch (reason) {
  case 'createOption':
  case 'selectOption':
    console.log('POST: ' + detail.option);
    break;
  case 'removeOption':
    console.log('DELETE: ' + detail.option);
    break;
  default:
    console.log(reason);
    break;
}

However, currently it will produce POST requests upon a duplicate item. I can of course, handle this in the backend - but as far as i can see in the docs it states onChange will fire when changed.

Your environment 🌎

`npx @mui/envinfo`

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

[michaldudak]

Thanks for the report. I agree that onChange should not be called in this case.

[alisasanib]

Hi! I would like to work on this issue

[michaldudak]

@alisasanib go ahead, it's all yours!