@ScarletKuro What does the ParameterStateAttribute do or when should I use it? Haven't seen it in other components before:

[AttributeUsage(AttributeTargets.Property)]
public class ParameterStateAttribute : Attribute
{
    public ParameterUsageOptions ParameterUsage { get; set; } = ParameterUsageOptions.All;
}

[Flags]
public enum ParameterUsageOptions
{
    None = 0,
    Read = 1 << 1,
    Write = 1 << 2,
    All = Read | Write
}

@danielchalmers For future PRs: Should I always create a separate PR for cleanups or do you don't want cleanups at all?

@danielchalmers For future PRs: Should I always create a separate PR for cleanups or do you don't want cleanups at all?

We usually don't do separate PRs - might make the changes when the code in a PR naturally touches those areas. Like if this was a bigger feature it would blend in fine, but for something small it's nice to have bite-sized PRs.

@ScarletKuro What does the ParameterStateAttribute do or when should I use it? Haven't seen it in other components before:

This is when you use ParameterState. Adding [ParameterState] enables our analyzer to flag cases where someone reads from or writes to the component parameter directly instead of using the ParameterState field.
https://github.com/search?q=repo%3AMudBlazor%2FMudBlazor+%5BParameter%2C+ParameterState%5D&type=code

The other options don’t do anything yet, except that None disables the analyzer. The rest are intended for a future source generator, which will apply the attributes automatically rather than requiring them to be added manually.

Thank you!