Can someone with access to the pipeline re-run the tests? It seems that the runtime itself failed when executing the tests.

@fondraco adding you here, since you gave feedback on the issue, for some reason I can't add you to review

Hmm, the test still fails so I guess something got broken? Does the test locally works? I can only look at it tmr

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (86ac87b) 90.57% compared to head (16086fa) 90.57%.

@@           Coverage Diff           @@
##              dev    #7644   +/-   ##
=======================================
  Coverage   90.57%   90.57%           
=======================================
  Files         427      427           
  Lines       15225    15233    +8     
=======================================
+ Hits        13790    13798    +8     
  Misses       1435     1435           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fondraco The testing issues have been resolved.

I will add it to the documentation. If MaxLines is not specified, it defaults to 0 and therefore no max lines will be applied.

@henon I know it's about MaxLines, not maximum characters, but maybe it also worth to add to the note section, that if you will input a lot of text, the blazor server side will disconnect and you need to set MaximumReceiveMessageSize for the Hub? More info here #7263

OK, maybe as a note in the general description of MudInput?

@henon How about the following property description: "If AutoGrow is set to true, the input element will not grow bigger than MaxLines lines. If MaxLines is set to 0 or less, the property will be ignored"?

Clear to me.

@henon @ScarletKuro Done. Regarding the maximum characters issue I could add something like this (the text is just a draft):

But I'm not sure if that's MudBlazor's responsibility to inform users about possible issues related to Blazor Server.

You read my mind. If you could find a way to link to the issue #7263 on github then it would be perfect.

Maybe put the notice below the multiline examples

LGTM

But I'm not sure if that's MudBlazor's responsibility to inform users about possible issues related to Blazor Server.

Well, not really, but people do create a lot of github issues that are not related to MudBlazor, like "for loop doesn't work with MudBlazor components" when it's a C# behavior and if we can decrease the workload with some advices, I'm only up for such tips and tricks. @henon what do you think?

Done. Although I'm not sure if my placement of the MudAlert in the code is semantically correct. Couldn't find any example in the docs with text content below an example component. Looks like this now:

Thanks @AntMaster7, it looks good.

Hi @henon ,

We're using MudBlazor and noticed the AutoGrow feature we need has a closed PR but isn't in an official release yet. Could you share any plans for its release date?

Thank you!

Thanks for the reminder, we simply forgot to do a release. It has been released now: https://github.com/MudBlazor/MudBlazor/releases/tag/v6.11.1