Hey @eloiqs, thanks for the report!

A workaround would be using a Type Assertion, for example:

function SliderExample() {
  const [value, setValue] = React.useState(20);

  const handleChange = (event, newValue) => {
    setValue(newValue as number); // or number[] for a range slider
  };

  return (
    <Box sx={{ width: 300 }}>
      <Slider value={value} onChange={handleChange} />
    </Box>
  );
}

Using the as keyword, you manually assure Typescript that newValue is a number, of which you can be sure as the provided value is a number as well.

Implementing a generic to narrow down the callback would be nice though. If you (or anyone) would like to work on a PR, that would be great as well 😊🚀

@DiegoAndai @eloiqs I would like to pick this up

@gitstart sure! let me know if you need any help

Hi there, I've also encountered this issue, so understand the concern. I've tried to work on a solution.

Here's some modifications to the proposed by @sai6855 . - #38753

Could you please review them?

It has worked on the latest master branch.