Add requireArgs option in require-super-in-lifecycle-hooks rule

[samridhivig]

Fix #1784:

Updated require-super-in-lifecycle-hooks rule to error when super.init() is called without ...arguments.

[bmish]

We'll need to see some test cases to better understand what this change is doing..

[bmish]

We'll also need to put this behind an option (e.g. requireArgs) to avoid this being a breaking change. In a future major version, we could enable the option by default.

[bmish]

Just wondering, why are you only targeting init and not other lifecycle hooks?

[bmish]

Can we avoid searching for the node again? We should already have it from the above hasMatchingNode call right, so we can just check if that node has arguments.

[bmish]

Let's include a test case for both:

• implicit requireArgs = false (since it's the default)
• explicit requireArgs = false

[samridhivig]

@bmish Regarding your question, "Just wondering, why are you only targeting init and not other lifecycle hooks?"

Currently, I only added the requireArgs option for init hook as explicitly mentioned in the parent issue: ef4/ember-data-relationship-tracker#25 (review)

I didn't expand it to other hooks as I am not sure if all other hooks prefer to have ...arguments as well. If other hooks don't, then enforcing this linting rule for them can lead to verbose code.

[bmish]

@samridhivig I see. Yeah so we only know about the Ember Data issue with init needing args right now, but would you mind asking on the Ember Discord or otherwise doing some quick research to see if the other hooks should technically have args passed as well? I just want to avoid the situation where we need another breaking change later if we discover that all hooks need args. It also seems that we might as well require args for all hooks for consistency...which would also be helpful in case the other hooks end up needing args in the future.

[NullVoxPopuli]

Where's this rule at? Close?
Looks like there are some unresolved questions?