Schematics compliance with call-signature lint rule

[cyrilletuzi]

🚀 Feature request

Command

• lint

Description

It's a very good practice in TypeScript to enable the typedef: ["call-signature"] TSLint rule, which ensures that functions return type is explicit.

Why?

• because otherwise TypeScript infers the return type, but based on the code, which assumes the code is correct (while it may not);
• it's the minimal documentation that should be expected in any code.

Describe the solution you'd like

It would be nice if Angular CLI schematics could be compliant with that lint rule by default. It's currently not the case:

• in component schematic ngOnInit()
• in e2e schematics

The first one is especially annoying as then we need to add : void each time we create a new component.

That would also be more consistent with other schematics where the functions return type is indeed explicit (like guards, interceptors, etc.).

PR done in #16755. Note that it does not enable the lint rule, it just makes schematics compliant with it, so it has no consequences at all.

[angular-automatic-lock-bot]

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.}