Skip to content

Planning for Minimal APIs in .NET 7 #36770

Not planned
Not planned
@DamianEdwards

Description

@DamianEdwards

Super early list of potential areas to investigate in .NET 7:

  • More OpenAPI
    • describe schemas, either from binders or metadata
    • query/header/path params
    • more automatic descriptions (less need to use manual metadata)
    • easier authn/z configuration with Swagger UI light-up
  • More inferred parameter binding
    • Form & File binding
    • etc.
  • Extensible parameter binding
  • Extensible Result processing, e.g. delayed execution, shortcutting
  • Validation
  • Hot Reload, e.g. top-level statements, modifying route mappings, DI, etc.
  • Composition, e.g.
    • Route grouping
    • Route handler filters
  • 3rd-party extensibility
    • nSwag
    • OData
    • Microsoft....ApiVersioning
  • Developer experience
    • Route debugging tool/features
    • Analyzers
    • API versioning
  • Trimming and AoT
  • Performance
  • Problem Details everything
    • DeveloperExceptionPage
    • Middleware/ExceptionHandler
    • Something else?
  • Anti-forgery support (XSRF), e.g. via a middleware
  • Teach MVC to do more stuff like Minimal APIs, e.g. auto service resolution
  • Expanding the minimalistic philosophy to other areas of ASP.NET Core
    • CORS
    • Authn/z
    • gRPC, SignalR, Orleans
  • Razor support (e.g. Results.Page())

Activity

added this to the .NET 7 Planning milestone on Sep 20, 2021
shaggygi

shaggygi commented on Sep 21, 2021

@shaggygi
Contributor

Bedrock? Just curious.

loic-sharma

loic-sharma commented on Oct 17, 2021

@loic-sharma
Contributor

Expanding the minimalistic philosophy to other areas of ASP.NET Core

Would introducing minimal APIs for generic hosts and worker services make sense?

gulshan

gulshan commented on Oct 17, 2021

@gulshan

Please keep asp.net core 7 runnable on .net 6 LTS runtime.

davidfowl

davidfowl commented on Oct 17, 2021

@davidfowl
Member

They ship together so that won't happen

ghost

ghost commented on Oct 11, 2022

@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.

DamianEdwards

DamianEdwards commented on Jan 26, 2023

@DamianEdwards
MemberAuthor

Closing this issue as many of these are done or tracked by other issues now.

ghost locked as resolved and limited conversation to collaborators on Feb 25, 2023
added
area-minimalIncludes minimal APIs, endpoint filters, parameter binding, request delegate generator etc
on Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-minimalIncludes minimal APIs, endpoint filters, parameter binding, request delegate generator etcfeature-minimal-actionsController-like actions for endpoint routingfeature-minimal-hostingold-area-web-frameworks-do-not-use*DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @davidfowl@DamianEdwards@Pilchie@loic-sharma@gulshan

        Issue actions

          Planning for Minimal APIs in .NET 7 · Issue #36770 · dotnet/aspnetcore