Prevent to implement OnChanges and DoCheck on the same class

[rafaelss95]

According to DoCheck#description:

Note that a directive typically should not use both DoCheck and OnChanges to respond to changes on the same input, as ngOnChanges will continue to be called when the default change detector detects changes.

I thought it was a good idea to add a rule to prevent this.

[wKoza]

It makes sense. 👍

[rafaelss95]

@wKoza Do you have any name in mind for this rule?

[mgechev]

no-conflicting-life-cycle-hooks?

[rafaelss95]

I like this name. I'm implementing it right now. Do you think this rule needs to be made in a generic way to provide flexibility or only for DoCheck and OnChanges hooks?

[kylekatarnls]

My 2 cents, an important part of this quote is "on the same input"

Using OnChanges and DoCheck to respond to independent changes is a relevant usage.