I’m curious why they didn’t choose to define parameters like Variant, Margin or FullWidth as CascadingParameters? so they could be set using CascadingValue component.

<MudStack Class="mud-width-full" AlignItems="AlignItems.End">
    <MudTextField T="string" Variant="Variant.Outlined" Margin="Margin.Dense" FullWidth="true" Label="FirstName" />
    <MudTextField T="string" Variant="Variant.Outlined" Margin="Margin.Dense" FullWidth="true" Label="LastName" />
    <MudTextField T="string" Variant="Variant.Outlined" Margin="Margin.Dense" FullWidth="true" Label="dentificationNumber" />
    <MudTextField T="string" Variant="Variant.Outlined" Margin="Margin.Dense" FullWidth="true" Label="LicenceNumber" />
    <MudTextField T="string" Variant="Variant.Outlined" Margin="Margin.Dense" FullWidth="true" Label="Code" />
    <MudTextField T="string" Variant="Variant.Outlined" Margin="Margin.Dense" FullWidth="true" Label="BranchCode" />
    <MudTextField T="string" Variant="Variant.Outlined" Margin="Margin.Dense" FullWidth="true" Label="RegistrationNumber" />
</MudStack>

It would save a lot of duplication.

<MudStack Class="mud-width-full" AlignItems="AlignItems.End">
    <CascadingValue Value="Variant.Outlined">
        <CascadingValue Value="Margin.Dense">
            <CascadingValue Name="FullWidth" Value="true">
                <MudTextField T="string" Label="FirstName" />
                <MudTextField T="string" Label="LastName" />
                <MudTextField T="string" Label="dentificationNumber" />
                <MudTextField T="string" Label="LicenceNumber" />
                <MudTextField T="string" Label="Code" />
                <MudTextField T="string" Label="BranchCode" />
                <MudTextField T="string" Label="RegistrationNumber" />
            </CascadingValue>
        </CascadingValue>
    </CascadingValue>
</MudStack>