Often times, esLint would complain that a method should be placed after another method (I am using React so I'm not sure if it makes a difference). I am just wondering on what basis does it recommend a particular ordering?
All I know is that lifecycle methods should come first (in their proper order), then below them are the custom methods. But esLint would also complain about the ordering of those custom methods and I'm not sure why?
According to AirBnb react style guide which is what eslint rules follow, the ordering or method in React.Component shall be
- optional static methods
- constructor
- getChildContext
- componentWillMount
- componentDidMount
- componentWillReceiveProps
- shouldComponentUpdate
- componentWillUpdate
- componentDidUpdate
- componentWillUnmount
- clickHandlers or eventHandlers like onClickSubmit() or onChangeDescription()
- getter methods for render like getSelectReason() or getFooterContent()
- optional render methods like renderNavigation() or renderProfilePicture()
- render
