[Epic]: Minimal APIs enhancements

[rafikiassumani-msft]

This epic is to track all the potential work for Minimal APIs for .NET7.

Issues categories

Parameter Binding

• Minimal APIs route grouping : Improve minimal api routing with grouping #36007
• Stream/PipeReader parameter binding: Support binding request body as Stream/ReadOnlySequence<byte> maybe ReadOnlyMemory<byte>/ReadOnlySpan<byte> #38153
• StringValues parameter binding: Minimal APIs doesn't support binding to StringValues from query or headers #36726
  [ ] API to invoke binding logic in RequestDelegateFactory : Consider adding an API that enables invoking the default parameter binding logic of RequestDelegateFactory explicitly #38003
• Binding to Uri type : Support binding parameters to type Uri in Minimal Actions #36649
  [ ] FromHeaderAttribute and FromQueryAttribute enhancement: Add .ctor(string) to FromHeaderAttribute and FromQueryAttribute #36418
  [ ] More Parameter binding extensibility: Extend the ability to customize parameter binding for Minimal APIs #35489
• Array support for QueryString binding: Minimal Actions - array support in method signatures from querystring binding #32516
  [ ] Fix type mismatches between parameter and route constraints: Type mismatches between parameter and route constraints not caught #36859
  [ ] Support Form binding for Minimal endpoints #39430
• File parameter binding

Minimal hosting

[ ] Allow minimal host to be created without default HostBuilder: #32485

Result Enhancements

• Improve testability for IResult methods: Make IResult methods more testable #37502
• Clean up logs for IResult method : Scrub File prefix from internal File*Result types #36666
  [ ] Extensible Result processing, e.g. delayed execution, shortcutting
  [ ] Razor Support (Results.Page(), etc.) for Minimal Endpoints #39431

Endpoint Filters

• Support Minimal endpoint filters: Add support for endpoint filters #37853

Configurations

• Provide a better API for JsonOptions configurations: Consider a nicer API for configuring JsonOptions for minimal actions / route-to-code #39226
• Make IConfigureOptions consistent: Allow Use of IConfigureOptions Consistently Everywhere #39251

Validation

[ ] Add Support for validation framework for Minimal actions: #30666

OpenAPI Improvements

• Enhancements for OpenApi: [Epic] OpenAPI in .NET 7 #37098

Developer Experience

• Support more ProblemDetails (DeveloperExceptionPage, Middleware/ExceptionHandler, etc.)
• Support ProblemDetails Titles: Support more ProblemDetails Titles out-of-the-box for Results.Problem() #36417
  More Minimal APIs Analyzers: [Epic]: Analyzers for Minimal APIs + MVC #36637
  [ ] Provide capability for route debugging #44821
  [ ] Hot Reload /hot restart features (e.g. top-level statements, modifying route mappings, DI, etc.)[ ] Improve error messages for optional parameters and TryParse failures: Support custom error messages when validation fails on minimal APIs&nbsp;#35501 #44822
  [ ] Improve error messages for optional parameters and TryParse failures: Support custom error messages when validation fails on minimal APIs #35501

Expand Minimalistic Philosophy

• Simplify Authentication and Authorization configs for Minimal APIs: [Epic]: Configuring minimal APIs for auth should be suitably simple & featured #34545
• Add antiforgery support for Minimal endpoints: Add antiforgery (anti-csrf) support to minimal endpoints #38630
  [ ] Simplify CORS for Minimal APIs #44823
• Enable/Enhance response caching using Etag Filter for Minimal APIs endpoints #39429

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.