Download Latest Version v7.1.1 Release source code.tar.gz (356.3 kB)
Email in envelope

Get an email when there's a new version of ASP.NET Minimal APIs Made Easy

Home / v7.0.1
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2025-07-24 8.7 kB
0
v7.0.1 Release source code.tar.gz 2025-07-24 338.8 kB
0
v7.0.1 Release source code.zip 2025-07-24 651.6 kB
0
Totals: 3 Items   999.0 kB 0

❇️ Help Keep FastEndpoints Free & Open-Source ❇️

Due to the current unfortunate state of FOSS, please consider becoming a sponsor and help us beat the odds to keep the project alive and free for everyone.

New 🎉

Relocate response sending methods ⚠️ Response sending methods such as `SendOkAsync()` have been ripped out of the endpoint base class for a better intellisense experience and extensibility. Going forward, the response sending methods are accessed via the `Send` property of the endpoint as follows: :::cs public override async Task HandleAsync(CancellationToken c) { await Send.OkAsync("hello world!"); } In order to add your own custom response sending methods, simply target the `IResponseSender` interface and write extension methods like so: :::cs static class SendExtensions { public static Task HelloResponse(this IResponseSender sender) => sender.HttpContext.Response.SendOkAsync("hello!"); } This is obviously is a wide-reaching breaking change which can be easily remedied with a quick regex based find & replace. Please see the breaking changes section below for step-by-step instructions on how to migrate. Takes less than a minute.
Send multiple Server-Sent-Event models in a single stream It is now possible to send different types of data in a single SSE stream with the use of a wrapper type called **StreamItem** like so: :::cs public override async Task HandleAsync(CancellationToken ct) { await Send.EventStreamAsync(GetMultiDataStream(ct), ct); async IAsyncEnumerable<StreamItem> GetMultiDataStream([EnumeratorCancellation] CancellationToken ct) { long id = 0; while (!ct.IsCancellationRequested) { await Task.Delay(1000, ct); id++; if (DateTime.Now.Second % 2 == 1) yield return new StreamItem(id.ToString(), "odd-second", Guid.NewGuid()); //guide data else yield return new StreamItem(id.ToString(), "even-second", "hello!"); //string data } } } By default, the `StreamItem` will be serialized as a JSON object, but you can change this by inheriting from it and overriding the `GetDataString` method to return a different format such as XML or plain text.
Customize param names for strongly typed route params It is now possible to customize the route param names when using the [strongly typed route params](https://fast-endpoints.com/docs/misc-conveniences#strongly-typed-route-parameters) feature by simply decorating the target DTO property with a `[BindFrom("customName"))]` attribute. If a `BindFrom` attribute annotation is not present on the property, the actual name of the property itself will end up being the route param name.
Support for malformed JSON array string binding When submitting requests via SwaggerUI where a complex object collection is to be bound to a collection property of a DTO, SwaggerUI sends in a malformed string of JSON objects without properly enclosing them in the JSON array notation `[...]` such as the following: :::json {"something":"one"},{"something":"two"} whereas it should be a proper JSON array such as this: :::json [{"something":"one"},{"something":"two"}] Since we have no control over how SwaggerUI behaves, support has been added to the default request binder to support parsing and binding the malformed comma separateed JSON objects that SwaggerUI sends at the expense of a minor performance hit.
Auto infer query parameters for routeless integration tests If you annotate request DTO properties with `[RouteParam]` attribute, the helper extensions such as `.GETAsync()` will now automatically populate the request query string with values from the supplied DTO instance when sending integration test requests. :::cs sealed class MyRequest { [RouteParam] public string FirstName { get; set; } public string LastName { get; set; } } [Fact] public async Task Query_Param_Test() { var request = new MyRequest { FirstName = "John", //will turn into a query parameter LastName = "Gallow" //will be in json body content }; var result = await App.Client.GETAsync<MyEndpoint, MyRequest, string>(request); }

Fixes 🪲

Header example value not picked up from swagger example request If a request DTO specifies a custom header name that is different from the property name such as the following: :::cs sealed class GetItemRequest { [FromHeader("x-correlation-id")] public Guid CorrelationId { get; init; } } and a summary example request is provided such as the following: :::cs Summary(s => s.ExampleRequest = new GetItemRequest() { CorrelationId = "54321" }); the example value from the summary example property was not being picked up due to an oversight.
Xml comments not picked up by swagger for request schema There was a regression in the code path that was picking up `Summary` xml comments from DTO properties in certain scenarios, which has now been fixed.
Incorrect swagger example generation when '[FromBody] or [FromForm]' was used If a request DTO was defined like this: :::cs sealed class MyRequest { [FromBody] public Something Body { get; set; } } and an example request is provided via the Summary like this: :::cs Summary(x=>x.ExampleRequest = new MyRequest() { Body = new Something() { ... } }); swagger generated the incorrect request example value which included the property name, which it shouldn't have.
Default exception handler setting incorrect mime type Due to an oversight, the [default exception handler](https://fast-endpoints.com/docs/exception-handler) was not correctly setting the intended content-type value of `application/problem+json`. Instead, it was being overwritten with `application/json` due to not using the correct overload of `WriteAsJsonAsync()` method internally.

Minor Breaking Changes ⚠️

API change of endpoint response sending methods The response sending methods are no longer located on the endpoint class itself and are now accessed via the `Send` property of the endpoint. This is a breaking change which you can easily fix by doing a quick find+replace using a text editor such as VSCode. Please follow the following steps in order to update your files: 1. Open the top level folder of where your endpoint classes exist in the project in a text editor like VSCode. 2. Click `Edit > Replace In Files` and enable `Regex Matching` 3. Use `(?
Small change in the Server-Sent-Event response stream Previously the Server-Sent-Event response was written as: :::plain id:12345 event: my-event data: hello world! Notice the inconsistency in the spacing between the `id`, `event` and `data` fields. This has now been fixed to be consistent with the following format: :::plain id: 12345 event: my-event data: hello world!
Source: README.md, updated 2025-07-24