Mudblazor Select with multiselect and Fluentvalidation For-Expression

Question

I am binding to a select field in multiselect mode and I ran into a problem with the "For" property of the select field".

Here is a code snippet

When using a select field an options type must be set and in this example it will be string. To make validation work the "For"-Property needs to be set and pointing to a valid property of the same type as the select fields option (and thats string). But I am expecting a multiselect, so I am binding to an IEnumerable in my model and the validation code is also set for this property. I don`t have the necessary property to bind to and even if I did, the validation would not work as expected.

How do I make this work? I tried building a custom expression which would point to the first element of the array, but I am bad with expressions and couldn`t make it work.

@using FluentValidation


    
        
                
                        @foreach (var name in _names)
                        {
                            @name
                        }
                

                
                        @foreach (var name in _names)
                        {
                            @name
                        }
                
        
    
    
        Order
    


@code {    
    [Inject] ISnackbar Snackbar { get; set; }
    
    private string[] _names = new string[] {
        "Toni", "Matthew", "David"
    };

    MudForm form;

    TestModelFluentValidator testValidator = new TestModelFluentValidator();

    TestModel model = new TestModel();

    public class TestModel
    {
        public string Name { get; set; }
        public IEnumerable Names { get; set; }
    }

    private async Task Submit()
    {
        await form.Validate();

        if (form.IsValid)
        {
            Snackbar.Add("Submited!");
        }
    }

    /// 
    /// A standard AbstractValidator which contains multiple rules and can be shared with the back end API
    /// 
    /// 
    public class TestModelFluentValidator : AbstractValidator
    {
        public TestModelFluentValidator()
        {
            RuleFor(x => x.Name)
                .NotEmpty();

            RuleFor(x => x.Names).Must((parent, property) => property.Contains("Toni"))
                .WithMessage("Toni not found in those names!");
        }

        public Func>> ValidateValue => async (model, propertyName) =>
        {
            var result = await ValidateAsync(ValidationContext.CreateWithOptions((TestModel)model, x => x.IncludeProperties(propertyName)));
            if (result.IsValid)
                return Array.Empty();
            return result.Errors.Select(e => e.ErrorMessage);
        };
    }
}

Edit: Added code sample and trimmed unecessary code.

user_6843077 · Answer

Mudblazor snippet.

Ok, so you can trick the component by introducing a dummy property and binding the multi-select component to it then testing its name during validation.

When the form component passes the dummy property name to the validation method, you change the passed dummy name to the name of your collection so it's matched when fluent validation kicks in.

Something like this:

@using FluentValidation
@using System.Reflection


    
        
                
                        @foreach (var name in _names)
                        {
                            @name
                        }
                

                
                        @foreach (var name in _names)
                        {
                            @name
                        }
                
        
    
    
        Order
    


@code {
    [Inject] ISnackbar Snackbar { get; set; }

    private string[] _names = new string[] {
        "Toni", "Matthew", "David"
    };

    MudForm form;

    TestModelFluentValidator testValidator = new TestModelFluentValidator();

    TestModel model = new TestModel();

    public class TestModel
    {
        public string Name { get; set; }
        public string NameCollection { get; set; }
        public IEnumerable Names { get; set; }
    }

    private async Task Submit()
    {
        await form.Validate();

        if (form.IsValid)
        {
            Snackbar.Add("Submited!");
        }
    }

    /// 
    /// A standard AbstractValidator which contains multiple rules and can be shared with the back end API
    /// 
    /// 
    public class TestModelFluentValidator : AbstractValidator
    {
        public TestModelFluentValidator()
        {
            RuleFor(x => x.Name)
                .NotEmpty();

            RuleFor(x => x.Names).Must((parent, property) => property.Contains("Toni"))
            .WithMessage("Toni not found in those names!");
        }

        private async Task IsUniqueAsync(string email)
        {
            // Simulates a long running http call
            await Task.Delay(2000);
            return email.ToLower() != "test@test.com";
        }

        public Func>> ValidateValue => async (model, propertyName) =>
        {        
            propertyName = propertyName == nameof(TestModel.NameCollection) ? nameof(TestModel.Names) : propertyName;

            var result = await ValidateAsync(ValidationContext.CreateWithOptions((TestModel)model, x => x.IncludeProperties(propertyName)));
            if (result.IsValid)
                return Array.Empty();
            return result.Errors.Select(e => e.ErrorMessage);
        };
    }
}

Mudblazor Select with multiselect and Fluentvalidation For-Expression

1 Answers