I find it a bit challenging to distinguish between Component and Controller. How was the Controller replaced by component in Angular 2? I came across this description of a component:
In Angular, a Component is a distinct type of directive that utilizes a simpler configuration suitable for the structure of component-based applications.
This approach simplifies the process of building an app, resembling the usage of Web Components or following Angular 2's application architecture style.
Benefits of using Components:
- Simple configuration as compared to regular directives
- Promotion of best practices and default settings
- Optimized for component-focused architectures
- Transition to Angular 2 becomes easier with component directives
Situations where Components are not ideal:
- Directives requiring actions in compile and pre-link functions, which are unavailable
- When intricate directive definition options like priority, terminal, multi-element are needed
- For directives triggered by attributes or CSS classes rather than elements
Source: AngularJs Documentation
Moreover, explore the contrast between Directive vs Component
Despite these explanations, I have been incorporating similar logic in both component and controller.
Would someone be able to elaborate on this? And offer insights on structuring the application from a component-oriented perspective instead of relying solely on controllers.