`Asp.Versioning.Http` package support

HI

Thanks for the awesome package. Its awesome.

we add versions to our Apis via api header:

services.AddApiVersioning(options =>
        {
            options.AssumeDefaultVersionWhenUnspecified = true;
            options.DefaultApiVersion = ApiVersion.Default;
            options.ReportApiVersions = true;
            options.ApiVersionReader = new HeaderApiVersionReader("api-version");
        });

The API versioning on https://fast-endpoints.com/docs/api-versioning#deprecate-an-endpoint uses a path for the versioning. For fast endpoints we are also using the “Configure()” override. How can we utilize our version header for apis and using the Configure option. The “Version()” override does not appear to work 😕

Would be awesome if it fastendpoints could support https://github.com/dotnet/aspnet-api-versioning

Thanks again…

[dj-nitehawk]

okay soo… with v5.9.0.1-beta you can now do the following (if you really must) 😉

using Asp.Versioning;
using Asp.Versioning.Builder;
using Asp.Versioning.Conventions;
using FastEndpoints;
using FastEndpoints.Swagger;

var builder = WebApplication.CreateBuilder();

builder.Services
    .AddApiVersioning(o =>
    {
        o.DefaultApiVersion = new(1.0);
        o.AssumeDefaultVersionWhenUnspecified = true;
        o.ApiVersionReader = new HeaderApiVersionReader("x-api-version");
    })
    .AddApiExplorer(o => o.GroupNameFormat = "'v'VVV");

var versionSet = new ApiVersionSetBuilder(null)
    .HasApiVersion(1.0)
    .HasApiVersion(2.0)
    .Build();

builder.Services
    .AddSingleton(versionSet) //this is the only part that's specific to FastEndpoints
    .AddFastEndpoints()
    .AddSwaggerDoc(x =>
    {
        x.DocumentName = "version one";
        x.ApiGroupNames = new[] { "v1" }; //needs to conform to 'GroupNameFormat' above
    })
    .AddSwaggerDoc(x =>
    {
        x.DocumentName = "version two";
        x.ApiGroupNames = new[] { "v2" }; //needs to conform to 'GroupNameFormat' above
    });

var app = builder.Build();
app.UseAuthorization()
   .UseFastEndpoints()
   .UseSwaggerGen();
app.Run();

public class Endpoint_v1 : Endpoint<Request>
{
    public ApiVersionSet VersionSet { get; set; }

    public override void Configure()
    {
        Post("test");
        AllowAnonymous();
        Options(x => x
            .WithApiVersionSet(VersionSet)
            .MapToApiVersion(1.0));
    }

    public override async Task HandleAsync(Request r, CancellationToken c)
    {
        await SendAsync($"v1 - {r.Name}");
    }
}

public class Endpoint_v2 : Endpoint<Request>
{
    public ApiVersionSet VersionSet { get; set; }

    public override void Configure()
    {
        Post("test");
        AllowAnonymous();
        Options(x => x
            .WithApiVersionSet(VersionSet)
            .MapToApiVersion(2.0));
    }

    public override async Task HandleAsync(Request r, CancellationToken c)
    {
        await SendAsync($"v2 - {r.Name}");
    }
}

public sealed class Request
{
    public string Name { get; set; }
}

[zfchai]

Let’s first take a look at two images, as follows:

• using FastEndpoints.Swagger;

• using IGeekFan.AspNetCore.Knife4jUI;

demo => Solution1.zip

The above API essentially only has three APIs, as shown below:

• /my/create
• /user/create
• /your/create

My belongs to Admin，The other two APIs belong to Users。

Reference Documents：https://fast-endpoints.com/docs/swagger-support#swagger-operation-tags

After testing, it is clear that it does not meet expectations. Are you sure this is not a problem?

Do you understand what I mean, or should you tell me what to do?