You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe title is self explanatory...I couldn't find some insight/discussions/info about what are the long term plans (if there are any) about controllers.
Is some long term plan to have minimal API only and deprecate controllers?
If someone could shed a bit of light it would be highly appreciated.
PS.
not that i'm not used to this node.js express style minimal way, just trying to understand plans if there are any so i could act accordingly.
tnx
The text was updated successfully, but these errors were encountered:
There's no plan to deprecate controllers, but we do want Minimal APIs to be able to be used in place of controllers for maybe 80-90% of scenarios. Controllers in ASP.NET Core MVC have many, many features that while powerful add a lot of complexity and, in some cases, ceremony that simply isn't required for a lot of apps. That complexity also adds overhead that means there's a limit to how much we can improve the performance of Controllers before hitting diminishing returns (in truth we're already there).
Expect to see a few more features inspired by MVC coming to routing/Minimal APIs in the future to help round it out, e.g. deferred result execution, and endpoint filters.
I believe title is self explanatory...I couldn't find some insight/discussions/info about what are the long term plans (if there are any) about controllers.
Is some long term plan to have minimal API only and deprecate controllers?
If someone could shed a bit of light it would be highly appreciated.
PS.
not that i'm not used to this node.js express style minimal way, just trying to understand plans if there are any so i could act accordingly.
tnx
The text was updated successfully, but these errors were encountered: