Add "ctors" option to @no-direct-mutation-state" rule

[doochik]

This option allow to check specified methods like constructor.

Motivation
I have BaseComponent in my project and use it in this way:

class BaseComponent extends React.PureComponent {
   constructor(props, context) {
        try {
            this._init(props, context)
        } catch(e) {
           // log error
        }
   }
}

class MyComponent extends BaseComponent {
    _init() {
        this.state = {
            foo: 'bar'
        };
    }
}

_init method is actual constructor for MyComponent and I want to check it like constructor with the "ctors" options

"react/no-direct-mutation-state": [<enabled>, {
  ctors: ['_init']
}]

[ljharb]

I'm a -1 on this; React components should not use inheritance to share code. It's discouraged by the React team, it's not idiomatic in the community, and it's not even the best way to share code in CS overall.

[ljharb]

Please spell out "constructors" - letters don't cost money, but confusing abbreviations can.

[doochik]

@ljharb Let my clarify puprose of BaseComponent in my project. This is very tiny class which wraps in try-catch some lifecycle methods like constructor, render, etc. It has no functionality.
Basically it has same ideas like componentDidCatch in react@16.

At this time I can't update to esling-pligin-react@7.2.0 because you've fixed #832 :)

[ljharb]

I'd recommend doing that with a babel transform to change React.Component to your base component, and definitely not putting an unidiomatic pattern in your code.

Alternatively, you could also define componentDidCatch when needed, and you could use that babel transform only on components where that was defined.

[doochik]

Ok, I understand your point