[material-ui][Autocomplete] onInputChange called with undefined event contrary to type definition

[sydneyjodon-wk]

Steps to reproduce

Link to live example: (required) https://stackblitz.com/edit/react-ouzbqw?file=Demo.tsx

Steps:

1. Set the onInputChange prop
2. Check what is passed in for the event param

Current behavior

Hello 👋

I'm noticing that the onInputChange is typed as:

onInputChange?: (
    event: React.SyntheticEvent,
    value: string,
    reason: AutocompleteInputChangeReason,
) => void;

with a non-null event param, but null seems to be coming through for the param on mount. See demo:

Expected behavior

I'm not sure if onInputChange is supposed to be called on mount or not, but if it is and it's expected that null is an option for event, would it be possible to update the typing of onInputChange to reflect that?

Thanks!

Context

We are trying to use strict null safety

Your environment

See https://stackblitz.com/edit/react-ouzbqw?file=Demo.tsx - also reproduce-able in this docs demo

Search keywords: onInputChange undefined event

[mj12albert]

@sydneyjodon-wk Thanks for the repro, in your sandbox I think onInputChange is called because the initial value and inputValue are different, and inputValue is updated to match value
If you initialize the values like this:

const [value, setValue] = React.useState<string | null>(options[0]);
const [inputValue, setInputValue] = React.useState(options[0]);

the console.log does not get called

Here's a working sandbox (forked from yours): https://stackblitz.com/edit/react-ouzbqw-6hz33h?file=Demo.tsx

[sydneyjodon-wk]

@mj12albert thank you! I'm still wondering though if the prop type can be changed because my original sandbox is still evidence that it is possible for null to be passed in as an argument for onInputChange contrary to what the type says. Either that or don't call onInputChange at all in those cases?