`useAutocomplete` return values wrong on several `getXProps` functions.

Definition in question here: https://github.com/mui-org/material-ui/blob/e294394af1e5b2769ca22c5a084dc3b49933952a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.d.ts#L271-L278

I haven’t used all of these functions yet, but I know that the following are incorrect:

• getInputLabelProps
• getRootProps
• getInputProps
• getListboxProps
• getOptionProps

In my current project I have them typed as the following:

type StringLikeBoolean = boolean | 'false' | 'true';
interface RootProps {
    'aria-owns': string;
    role: string;
    'aria-expanded': StringLikeBoolean
    onClick: () => void;
    onKeyDown: () => void;
    onMouseDown: () => void;
}

interface InputLabelProps {
    htmlFor: string;
    id: string;
}

interface InputProps {
    id: string;
    'aria-activedescendant': string;
    'aria-autocomplete': 'list';
    'aria-controls': string;
    autoCapitalize: 'none';
    autoComplete: 'off';
    onBlur: (event: React.FocusEvent<HTMLInputElement>) => void;
    onChange: (event: React.ChangeEvent<HTMLInputElement>) => void;
    onFocus: (event: React.FocusEvent<HTMLInputElement>) => void;    onMouseDown: () => void;
    ref: React.RefObject<HTMLInputElement>;
    spellCheck: StringLikeBoolean
    value: string;
}

interface OptionProps {
    'aria-disabled': StringLikeBoolean;
    'aria-selected': StringLikeBoolean;
    'data-option-index': number;
    id: string;
    key: number;
    onClick: () => void;
    onMouseOver: () => void;
    onTouchStart: () => void;
    role: 'option';
    tabIndex: number;
}

If these are accurate I would be more than happy to open a pull request.

[kentaro84207]

Could I work on this? 😃

[tbremer]

I think I will have time this week to work on this problem.

I also found something in the onChange handler that should be updated: https://github.com/mui-org/material-ui/blob/e294394af1e5b2769ca22c5a084dc3b49933952a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.d.ts#L242

I had to handle this as the generic HTMLElement type. Is it consistent what element this should be? For instance, my event fires on an li because of how I build my listbox.