Angular - Lifecycle Hooks
What will happen if you try to access an @Input property inside the constructor instead of
ngOnInit?What will happen if you try to access an @Input property inside the constructor instead of ngOnInit?
medium📝 Predict Output Q5 of 15
Step-by-Step Solution
Solution:
Step 1: Understand @Input timing
@Input properties are set after the constructor runs, before ngOnInit.Step 2: Accessing @Input in constructor
Accessing @Input in constructor may get undefined or default value because Angular hasn't set it yet.Final Answer:
The @Input property may be undefined or not yet set -> Option BQuick Check:
@Input ready after constructor, safe in ngOnInit [OK]
Quick Trick: Access @Input only in ngOnInit or later [OK]
Common Mistakes:
- Expecting @Input to be ready in constructor
- Assuming Angular throws error for early access
- Confusing compile-time and runtime behavior
Master "Lifecycle Hooks" in Angular
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Angular Quizzes