Use of Directives to create almost everything

1

I worked a few days ago on a project where we used angle 1. *. The case is that every table that we created on screen, or any element with data and a certain complexity, was created a directive for such, besides the controller, etc.

My question is: Should we create so many files like this just to put a table on screen? I do not know if this is a standard but if it is, I do not agree with it much ...

Are not we confusing things and bringing back responsibilities to the front and we end up duplicating them? I answer why this. This application I commented was developed from C # in the MVC template. In this template you already have the route settings. To do the same in the angle, or whatever the. Js framework.

The impression I get is that we have a lot more work in using the framework that has a lower lifecycle than parent technology (js, etc), and it makes me wonder if it's just worth using all these features and imposed standards.

  

I'm not talking bad about the framework, but trying to understand if this   standard that I really comment on and why it exists.

    
asked by anonymous 28.02.2018 / 20:52

0 answers