API Feature Folders ⚡️

In ASP.NET Core (and unlike ASP.NET 5 / Web API 2), Web API controllers are just controllers. 🗂

You don’t need to inherit from a different base type or anything like that. ❌

What’s more, your API controllers should be returning DTOs that are separate from your underlying domain or data model. ↔️

What I’ve found to be a better organization is to do away with the Controllers folder (or keep it around if you’re using view-based controllers) and instead use feature folders for your APIs. 💎

I’m partial to having a root level API folder but if you’d prefer to put your features in the root of the project that would work, too. 👍🏻

Within each feature folder, you include the controller along with any model types it needs to work with, like this 👾 :

https://t.me/pgimg/124

Obviously one benefit of this approach is that it’s more cohesive. ✅

Things that change together are located physically next to one another, and the friction involved in moving between different folders with too many files in them is greatly reduced. ✂️

Another nice thing about this approach is that it just works. Unlike view-based controllers, you don’t need to change anything about how ASP.NET Core is configured to have this organization structure work for you. ✨


[ Article ] : bit.do/apif

〰〰〰〰〰〰
#AspMvc #Core #API
@ProgrammingTip