marcominerva/minimalhelpers

A collection of helpers libraries for Minimal API projects.

minimalhelpers's Issues

Add Source Link support

SimpleAuthentication project must support Source Link, as described here: https://devblogs.microsoft.com/dotnet/producing-packages-with-source-link.

At https://github.com/ErikEJ/SqlClientExtensions/blob/main/src/SqlClientExtensions/SqlClientExtensions.csproj you can find a real example of a library with Source Link enabled.

Create MinimalHelpers.OpenApi library

Add Source Generator for endpoints registration

Currently endpoints registration relies on Reflection. In order to support Native AOT scenarios, this approach should be replaced by a solution that uses Source Generator.

Use static abstract interface members in .NET 7.0

With the relase of .NET 7.0, the library should explicitly target both 6.0 and 7.0 versions. The .NET 7.0 must use static abstract interface members.

Update MinimalHelpers.OpenApi to .NET 8.0

reference Microsoft.CodeAnalysis.CSharp version 4.9.2 is completely out of mind

Sorry if title feel harsh but how can i use source gen version if it reference Microsoft.CodeAnalysis.CSharp 4.9.2 while every tooling in newest Asp.Net core reference 4.5, is this lib suppose to use with preview version of .NET or we suppose to force reference 4.9.2 ??

Update MinimalHelpers.Routing to .NET 8.0

Remove fix for issue 45365

Now that .NET 7.0.3 includes the fix for dotnet/aspnetcore#45365, the workaround included in the MinimalHelpers.OpenApi library can be removed.

Add support for IFormFile and IFormFileCollection using WithOpenApi

When using WithOpenApi extension method, IFormFile and IFormFileCollection parameters are incorrectly defined in the swagger.json file. The issue is reported here: domaindrivendev/Swashbuckle.AspNetCore#2625.

While waiting for an official fix, it is necessary to provide a workaround for this behavior.

Provide a static abstract interface method to register endpoints

Currently, the library requires that we implement the IEndpointRouteHandler interface and, at runtime, reflection is used to instantiate the class in order to call the MapEndpoints method. With .NET 7.0, we can provide an alternative method to endpoint registration using static abstract interface members. The proposal is to add the following interface and the corresponding extension method to the library:

public interface IStaticEndpointRouteHandler
{
    static abstract void MapEndpoints(IEndpointRouteBuilder endpoints);
}

public static void MapEndpoints<T>(this IEndpointRouteBuilder endpoints) where T : IStaticEndpointRouteHandler
{
     // ...
}

In this way, we can register our handler using a syntax like this:

app.MapEndpoints<PeopleHandler>();
app.MapEndpoints<ProductsHandler>();

And no reflection at all will be involved in the registration process.

The question is: giving this new behavior, do you think that IStaticEndpointRouteHandler is a good name for the new interface?

Update MinimalHelpers.Routing to .NET 7.0

The library must work with both .NET 6.0 and .NET 7.0