[material-ui][Select] Typescript errors with generic argument for multiple select

[Sengulair]

Steps to reproduce

Typescript reproduction example: Link
Using the generic argument in the Select component with multiple property causes an error by passing the generic argument to value and to onChange properties

Current behavior

Typescript error when using generic component and passing value with generic type to value and onChange function.

Expected behavior

No Typescript errors

Context

I tested the 5.15.10 version. It was good, without error. Looking at the source code of the newer version I see that passing Variant as a second type argument to the SelectProps type causes that error. Maybe it's a Typescript issue here, but I can't understand why.

Your environment

npx @mui/envinfo

  System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.10.2 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Chrome: Not Found
    Edge: Chromium (122.0.2365.66)
  npmPackages:
    @emotion/react:  11.11.3 
    @emotion/styled: ^11.11.0 => 11.11.0 
    @mui/base:  5.0.0-beta.38 
    @mui/core-downloads-tracker:  5.15.12 
    @mui/material: ^5.15.12 => 5.15.12 
    @mui/private-theming:  5.15.12 
    @mui/styled-engine:  5.15.11 
    @mui/system:  5.15.12 
    @mui/types:  7.2.13 
    @mui/utils:  5.15.12 
    @types/react: ^18.2.58 => 18.2.58 
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^5.3.3 => 5.3.3

5.15.10 -> 5.15.12

Search keywords: Select, generic, types, typescript

[DiegoAndai]

Hey @Sengulair, thanks for the report!

This is related to #39137 (comment) and #41356. I'll keep it open as it's a new case where the updated type breaks, so we should make sure that we fix it.

[DiegoAndai]

Adding the ready to take label in case we get any contributors with an idea of how to solve this. Let's discuss potential solutions here if you wish to work on this.