Route order in fastendpoints library

How can I fix the route order in fastendpoints library? I have two routes: /onboarding/{OnboardingId} and /onboarding/restore. But fastendpoints always goes to the first route because it thinks restore is also an OnboardingId.

[dj-nitehawk]

just tried the following and it works as expected:

public class RestoreRequest
{
    [QueryParam]
    public string CrmId { get; set; }
}

public class RestoreEndpoint : Endpoint<RestoreRequest>
{
    public override void Configure()
    {
        Get("/onboarding/restore");
        AllowAnonymous();
    }

    public override async Task HandleAsync(RestoreRequest r, CancellationToken c)
    {
        await SendAsync($"Hi from /onboarding/restore?crmId={r.CrmId}");
    }
}

public class OnboardingEndpoint : EndpointWithoutRequest
{
    public override void Configure()
    {
        Get("/onboarding/{onboardingId:minlength(10)}");
        AllowAnonymous();
    }

    public override async Task HandleAsync(CancellationToken c)
    {
        await SendAsync($"Hi from /onboarding/{Route<string>("onboardingId")}");
    }
}

[itsoli91]

This is interesting…  if I put the restore method on top of another method http://localhost:5019/onboarding/restore now returns 200 ok

app.MapGet("/onboarding/restore",
        ([FromQuery] string? crmId) =>
        {
            return $"Hi from /onboarding/restore?crmId={crmId}";
        })
    .WithOpenApi();

app.MapGet("/onboarding/{onboardingId:minlength(10)}",
        (string onboardingId) =>
        {
            return $"Hi from /onboarding/{onboardingId}";
        })
    .WithOpenApi();