Repository navigation
OnInit is not added to new components any more #48575
Description
Describe the problem that you experienced
The linked stackoverflow topic do explain the issue well!
ng generate componentdoes not create ngOnInit and constructor
Enter the URL of the topic with the problem
https://stackoverflow.com/q/74870515/42580
Describe what you were looking for in the documentation
I was trying to run the TourOfHeros-tutorial when I could not match my experiance with the tutorial, so after some google-work I found the SO-topic.
Describe the actions that led you to experience the problem
No response
Describe what you want to experience that would fix the problem
No response
Add a screenshot if that helps illustrate the problem
No response
If this problem caused an exception or error, please paste it here
No response
If the problem is browser-specific, please specify the device, OS, browser, and version
No response
Provide any additional information here in as much as detail as you can
No response
Activity
JeanMeche commentedon Dec 22, 2022
Thank you for reporting that, I've open a PR to update the tutorial.
athirakarakkodath commentedon Dec 24, 2022
when I create components using ng g c component name , in my ts file ngOnInit and constructor are not creating.. I have to type that manually..using latest angular version..please help me i am new to this angualr
JelleBruisten commentedon Dec 24, 2022
@athirakarakkodath Since the latest angular, this has been removed from the generate component schematic. So you will need to add lifecycle interfaces yourself. ( And also don't need to remove them incase they are not needed )
docs: remove onInit from Tour Of Heroes.
docs: remove onInit from Tour Of Heroes. (#48576)
docs: remove onInit from Tour Of Heroes. (#48576)
docs: remove onInit from Tour Of Heroes. (angular#48576)
angular-automatic-lock-bot commentedon Feb 5, 2023
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.