Angular - Lifecycle Hooks
Why is it recommended to keep initialization logic inside
ngOnInit instead of the constructor in Angular?Why is it recommended to keep initialization logic inside ngOnInit instead of the constructor in Angular?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Recall Angular initialization order
Constructor runs first, then Angular sets input properties, then ngOnInit runs.Step 2: Understand why initialization belongs in ngOnInit
Initialization depending on inputs must wait until inputs are set, so ngOnInit is the right place.Final Answer:
Because Angular sets input properties after the constructor but before ngOnInit -> Option DQuick Check:
Initialization after inputs = ngOnInit [OK]
Quick Trick: Initialize after inputs in ngOnInit, not constructor [OK]
Common Mistakes:
- Thinking constructor cannot have code
- Believing ngOnInit runs multiple times
- Confusing lifecycle order
Master "Lifecycle Hooks" in Angular
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Angular Quizzes