[Autocomplete] Prevent renderValue from being skipped when value is 0

[LakshitAgarwal]

• I have followed (at least) the PR section of the contributing guide.

Fixes #46131

[mui-bot]

Netlify deploy preview

https://deploy-preview-46145--material-ui.netlify.app/

Bundle size report

Details of bundle changes (Toolpad)
Details of bundle changes

Generated by 🚫 dangerJS against ca12679

[0210shivam]

I think the explicit check for value !== undefined is redundant, as value != null already covers both null and undefined.

[LakshitAgarwal]

I think the explicit check for value !== undefined is redundant, as value != null already covers both null and undefined.

okay i'll just remove that and raise a new PR, if that works?

[0210shivam]

No need to raise a new PR — you can amend the commit and push to the same branch to update this one.

[LakshitAgarwal]

okay i just did. Thanks

[0210shivam]

Thanks for the update! One small note — no need to strictly check for null here, != null is sufficient.

[LakshitAgarwal]

Thanks for the update! One small note — no need to strictly check for null here, != null is sufficient.

i didn't really get that. Is that not what I did?

[0210shivam]

I was suggesting to remove the strict check (like value !== null) — remove the extra equals sign — and use != null instead.

[LakshitAgarwal]

got it! Just made the necessary changes

[LakshitAgarwal]

Can this branch be merged now? And this issue be close?

[ZeeshanTamboli]

@LakshitAgarwal Thanks for the fix! I’ve added a test case as well.