[Slider][material][base] Allow generic value type to narrow onChange value type

[gitstart]

Description

Narrow Slider onChange value type to be either number or number[] depending on the type of the value argument.

Updated onChange prop in:

packages/mui-base/src/useSlider/useSlider.types.ts
packages/mui-material-next/src/Slider/Slider.types.ts
packages/mui-material/src/Slider/Slider.d.ts

Closes #37854

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

---

This code was written and reviewed by GitStart Community. Growing great engineers, one PR at a time.

[mui-bot]

Netlify deploy preview

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

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against ee1935e

[gitstart]

Hi @DiegoAndai this PR is ready for review.

Note that I used a union of different call signatures to define the slider onChange type instead of a generic. WDYT?

[DiegoAndai]

Hi @gitstart! thanks for working on this

Sadly, I don't think this is solving the issue we want to solve 😕

Look at this codesandbox: https://codesandbox.io/s/slider-onchange-type-pr-37854-llcchv?file=/src/App.tsx

In the example, the slider is "single value" (as the value is a number). The handleChange function is typed as receiving a number[], so what we want with this fix is that handleChange throws an error when passed to onChange, as onChange should receive the same type as the value, which is number. Does that make sense?

We either have to extract the type from the value prop (I don't know if this one is possible) or transform the Slider into a generic component.

@michaldudak what's your take on this?

[gitstart]

@DiegoAndai thanks for the feedback. We actually tried exploring the first suggestion (extracting the type from the value prop), but it didn't work out. I think it's worth trying out your second suggestion.