[TextareaAutosize] Rename rowsMax->maxRows & rowsMin->minRows

[mhayk]

Breaking changes

TextField

• Rename rowsMax prop with maxRows for consistency with HTML attributes.

  -<TextField rowsMax={6}>
  +<TextField maxRows={6}>

TextareaAutosize

• Rename rowsMax prop with maxRows for consistency with HTML attributes.

  -<TextareAutosize rowsMax={6}>
  +<TextareAutosize maxRows={6}>

• Rename rowsMin prop with minRows for consistency with HTML attributes.

  -<TextareAutosize rowsMin={1}>
  +<TextareAutosize minRows={1}>

Part of #20012

[mui-pr-bot]

Details of bundle changes

Generated by 🚫 dangerJS against 322ff33

[oliviertassinari]

Thanks for starting working on it, we would also need to handle rowsMin -> minRows

[mhayk]

@oliviertassinari done! 👊

[oliviertassinari]

@dmtrKovalenko Any idea on the fail with the DatePicker? https://app.circleci.com/pipelines/github/mui-org/material-ui/15930/workflows/3b1b360c-2f3b-4482-b5f0-afed19f04433/jobs/165238

What about we hold this pull request, and we upgrade the dependency on the pickers from v3 to the last alpha release? At the minimum, it will move us in the right direction.

[dmtrKovalenko]

It is a typescript error caused by conflict in typings.

Yes upgrading pickers will solve the issue

[oliviertassinari]

Alright, let's try the upgrade in another pull request and keep this one on hold :).
@dmtrKovalenko do you want to take care of it?

[oliviertassinari]

@mhayk Thanks!

[mbrookes]

@mhayk Thanks for working on this. Would you be happy to work on adding a deprecation warning on the master branch?

[mhayk]

Hey @mbrookes! Of course! I am going to do that .. thank you to invite me!

[mbrookes]

@mhayk That's great, thanks! If you need any pointers, you can check other examples that have already been completed: #20012

[mbrookes]

Hey @mhayk! 👋 Just checking if you still plan to work on adding a deprecation warning for v4? Thanks!

[mhayk]

Hi @mbrookes .. sorry for the delay .. #23530. Could you review please ?

[mbrookes]

@mhayk No need to apologize - thanks for working on it! It looks like there might be a couple of CI issues to fix. If the errors don't make sense, feel free to ping me on the PR, and I'll take a look.