Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.48%. Comparing base (9cd0827) to head (8d50859).

@@            Coverage Diff             @@
##              dev    #8545      +/-   ##
==========================================
- Coverage   89.51%   89.48%   -0.03%     
==========================================
  Files         410      410              
  Lines       11831    11832       +1     
  Branches     2355     2355              
==========================================
- Hits        10590    10588       -2     
- Misses        713      715       +2     
- Partials      528      529       +1     

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

I like the functionality, it is very useful, reminds me of LastChildFill in WPF's DockPanel. Before we merge it, we need to make sure we got the best naming for the parameter, the enum and its values in view of the other parameters that apply to the children: AlignItems and Justify.

Also, we should consider LTR vs RTL. First and Last are culture specific, so in RTL mode First should stretch the right most child. And since we use Start and End for all other culture specific directions in the lib we should use these names instead.

Naming suggestion:

[Parameter]
public StretchItems StretchItems { get; set; }

public enum StretchItems {
  None,
  Start,
  End,
  StartAndEnd,
  Middle, 
  All,
}

Usage:

<MudStack StretchItems="StretchItems.End">
  ...
</MudStack>

It might be good to add a StartAndEnd also.

I like the functionality, it is very useful

Yeah, I think this is very common functionality in the Xamarin, Flutter, MAUI, WPF etc.

[...] we need to make sure we got the best naming for the parameter, the enum and its values in view of the other parameters [...]

Taking this further, perhaps StretchItems with Stretch enum would be more appropriate?

<MudStack AlignItems="Align.Start" StretchItems="Stretch.End">
...
</MudStack>

Oh sorry, you didn't make the changes yet. Make sure to use the [CascadingParameter] public bool RightToLeft {get; set;} to achive the correct order for Start and End

Oh sorry, you didn't make the changes yet. Make sure to use the [CascadingParameter] public bool RightToLeft {get; set;} to achive the correct order for Start and End

MudStack has Reverse parameter which does that. Should this be replaced with CascadingParameter?

This is a tricky one because RTL does not mean the same in MudStack. When the stack is vertical (column), Reverse means bottom-to-top, not right-to-left.

I see that mudstack already implements right to left logic. so I guess you won't have to? It will be automatically correct?

This is a tricky one because RTL does not mean the same in MudStack. When the stack is vertical (column), Reverse means bottom-to-top, not right-to-left.

Reverse is independent of RTL

Question is, what should be done with Stretch.Start and Stretch.End when Reverse is true? I don't know

Whatever it is now feels natural in both LTR and RTL when reversed, and when not, so I'd leave it as is. I have changed parameter name to StretchItems, Enum name to Stretch, added Stretch.StartAndEnd + unit, corrected some other incorrect descriptions in MudStack and updated examples to use new generic MudChipSet.

Perfect, looks good. If you will add the nameofs real quick I'll merge this today.

AlignItems="Align.Start"

I have made a mistake here, it's AlignItems="AlignItems.Start". Should Stretch enum be StretchItems then?

In theory there could be other uses of stretching, i.e. for images where you would need Stretch.Uniform, Stretch.X, Stretch.Y etc, so yes, it is the safest bet to rename the enum to StretchItems

Thanks @BieleckiLtd

Hello guys
Thanks for the great components, they help a lot in my work!

Is it possible to implement this functionality in v6?

v6 is on community support which means that those who need something backported from higher versions or bug fixes can do so. We'll review PRs and merge them and release a new version of v6.