Add flag to ng generate component that skips adding ngOnInit() interface.

🚀 Feature request

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• extract-i18n
• run
• config
• help
• version
• doc

Description

Generating components with ng g c component-name always generates a component implementing ngOnInit() interface.

Many components do not benefit from implementing such interface. A good example might be a dumb component, that uses mostly @Input() and @Output().

Right now there is no way to override this behaviour so if you want to generate a dumb component, you need to:

1. remove ngOnInit() method,
2. remove implements OnInit clause from the component class,
3. remove the OnInit import from ‘@angular/core’;

This has to be repeated for every component generated, so it gets old really fast 🤷

Describe the solution you’d like

Ideally, there should be an option to generate a component that does not implement the ngOnInit() hook.

Maybe something like this could work: ng g c component-name --skip-on-init or ng g c component-name --skip-lifecycle

It would match the naming of flags such as --skip-tests or --skip-selector.

[mgechev]

We started generating ngOnInit to encourage folks to not put complex logic in the constructor and make the component more testable.

I, personally, keep the hook less than 1% of the time.

To me it makes sense to remove it from the component generator, but would like to collect more community feedback before we move forward.

[y-nut]

I usually remove the ngOnit as well but I don’t like the flag approach on the generator. I would prefer to set it up in the project config file and then add a flag when creating the project like ng new project --skip-lifecycle