Wolverine.Http discover nested endpoint classes

[firedog]

Hi all!

I'm trying out a model where all endpoint related types live inside an outer class like in the following toy example:

public class AddSomething
{
    public record Command(string Name);

    public class Validator : AbstractValidator<Command>
    {
        public Validator()
        {
            RuleFor(x => x.Name).NotEmpty().MinimumLength(1).MaximumLength(50);
        }
    }

    public record Response(Guid Id) : CreationResponse("/api/somethings/" + Id);

    public static class Endpoint
    {
        [WolverinePost("/api/somethings")]
        public static Response Post(Command command, IDocumentOperations operations)
        {
            var something = new Something { Id = Guid.NewGuid(), Name = command.Name };
            operations.Store(something);
            return new Response(something.Id);
        }
    }
}

// Something class
public class Something
{
    public Guid Id { get; set; }
    public string Name { get; set; } = string.Empty;
}

The problem is that Wolverine does not discover the nested Endpoint class when mapping endpoints and a 404 is returned. Making the AddSomething class static makes no difference.

Is there some attribute or marker interface that can be used to aid Wolverine in finding a nested endpoint class? I tried applying the WolverineHandler attribute on the nested Endpoint class and even on its methods with no luck...

Some other way to achieve this? Manual mapping? Changing discovery?

Thanks!