1
I worked a few days ago on a project where we used angular 1.*. The case is that, each table that we created on screen, or any element with data and a certain complexity, was created a directive for this, beyond the controller, etc.
My question is: Should we create so many files just to put a table on the screen? I don’t know if this is a pattern but if it is, I don’t agree with him very much...
Are we not confusing things and bringing back responsibilities to the front and thus end up duplicating them? I answer for that. This application I mentioned was developed from C# in the MVC template. In this template you already have the route settings. Why do the same at the angle, or whatever the . js framework is.
The impression is that we have much more work when using the framework that has a shorter life cycle than the parent technology (js, etc) and makes me wonder if it is worth it to use all these resources and standards imposed.
I am not speaking ill of the framework but trying to understand if this pattern that comment really exists and why it exists.
I think using Angular with a Restful Api, like Web Api 2 you would have more benefit from the feature, I think with MVC ends up being redundant even, but I don’t know what the architecture of the project is and why they decided to do so.
– William Cézar
It makes sense @Williamcézar. So actually, if you’re going to use the . net platform, it would make more sense to create an app without the MVC template, that’s it?
– DiegoSantos
For me, yes, it makes more sense to use the Web Api, MVC has a lot of dependency that you wouldn’t need using Angular, it might even be interesting to use . net core
– William Cézar
But then, we’re talking about the right template? The case of . net core don’t know. Why would he use it specifically?
– DiegoSantos