Generic Modal Parameters[Feature Request]

[thepigeonfighter]

Is your feature request related to a problem? Please describe.
I've have accidentally passed parameters that don't match Component Parameter Types into the ModalParameters object because there are no Type constraints.

Describe the solution you'd like
Create a generic Modal Parameters class like:

public class ModalParameters<TModal> : ModalParameters
{
    public void AddParameter<TProperty>(Expression<Func<TModal, TProperty>> propertyExpression, TProperty value)
    {
        if (propertyExpression is null)
        {
            throw new ArgumentNullException(nameof(propertyExpression));
        }
        if (value is null)
        {
            throw new ArgumentNullException(nameof(value));
        }
        LambdaExpression lambda = propertyExpression;
        var memberExpression = lambda.Body is UnaryExpression expression
            ? (MemberExpression)expression.Operand
            : (MemberExpression)lambda.Body;
        
        var propInfo = (PropertyInfo)memberExpression.Member;

        Add(propInfo.Name, value);
    }
}

As a note it is AddParameter and not Add to maintain backwards compatibility and to get the complier type safety. I originally had the method as an overload of Add but then you wouldn't get the complier error thus defeating the purpose.

Usage

 var modalParam = new ModalParameters<TModal>();
 modalParam.AddParameter(x => x.Foo, _foo);

[SSchulze1989]

This would be a really nice addition and helps a lot to clean up the code.
It helps especially in the case of passing EventHandlers or Functions to the modal, for example if i want an async submit action to be performend before closing the modal:

var parameters = new ModalParameters()
    .Add(nameof(ModalComponent.OnSubmit), new Func<ModelType, CancellationToken, Task<bool>>(
        (model, cancellation) => OnSubmitAction(model, cancellation));

with the generic version the code simplifies to:

var parameters = new ModalParameters<ModalComponent>()
    .Add(x => x.OnSubmit, new((model, cancellation) => OnSubmitAction(model, cancellation));

And the latter is also typesafe.

This saves a lot of typing (especially when doing so in the dreadful razor editor ...)
Since I am using a lot of modals for async updating data via REST API and i always want to wait for a response before closing I do encounter this problem often in my application.

@thepigeonfighter i did implement the same thing on my end and did not have any issues with the Method being named Add() as well. Since the first parameter is an expression and not a string the compiler can pick the correct overload.

[BenMakesGames]

we've written a basically-identical extension for our project at work. however: I wouldn't want such a method to throw an ArgumentNullException for null parameter values. there are many times we have optional (nullable) parameters in our modals.