Outsourcing validators to separate class-lib is not possible

I have the following project setup:

My requests, responses and validators are living outside of the API project that references FastEndpoints in a project called Contract. This is done to allow for easy integration of requests, responses and validators into the API and Blazor frontends.

Due to changes in #141 AbstractValidator<T> instances are no longer registered by FastEndpoints, so this doesn’t work any longer. Installing FastEndpoints into the Contract class lib is not an option as this will break Blazor WASM with the following error:

Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(427, 5): [NETSDK1082] There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

[dj-nitehawk]

guys give v5.0.0-beta7 a whirl…

so… by default only validators inheriting from FastEndpoints.Validator<TRequest> are auto discovered and registered.

if someone wants to include FluentValidation.AbstractValidator<TRequest> validators as well, all they gotta do is:

builder.Services.AddFastEndpoints(o => o.IncludeAbstractValidators = true);

an exception will be thrown during startup if more than one validator is found for a single request dto. in which case the user needs to be explicit about which exact validator must be used in the endpoint configuration like so:

    public override void Configure()
    {
        Get("test");
        Validator<MyValidator>();
    }

beta docs updated: https://dev--fast-endpoints.netlify.app/docs/validation#abstract-validator-classes

so… what do you think? have i missed anything?

[dj-nitehawk]

you can ignore the generator for now. I’ll look in to it later. for now it can be a limitation of the generator package. i.e. it will discover all validators.