When creating React components it is more convenient to always follow the same organisation for methods order to helps you to easily find lifecyle methods, event handlers, etc.
Fixable: This rule is automatically fixable using the sort-comp
transform in react-codemod.
With default configuration the following organisation must be followed:
- static methods and properties
- lifecycle methods:
displayName
,propTypes
,contextTypes
,childContextTypes
,mixins
,statics
,defaultProps
,constructor
,getDefaultProps
,getInitialState
,state
,getChildContext
,componentWillMount
,componentDidMount
,componentWillReceiveProps
,shouldComponentUpdate
,componentWillUpdate
,componentDidUpdate
,componentWillUnmount
(in this order). - custom methods
render
method
The following patterns are considered warnings:
var Hello = React.createClass({
render: function() {
return <div>Hello</div>;
},
displayName : 'Hello'
});
The following patterns are not considered warnings:
var Hello = React.createClass({
displayName : 'Hello',
render: function() {
return <div>Hello</div>;
}
});
This rule can take one argument to customize the components organisation.
...
"react/sort-comp": [<enabled>, { order: <order>, groups: <groups> }]
...
enabled
: for enabling the rule. 0=off, 1=warn, 2=error. Defaults to 0.order
: optional array of methods to validate.groups
: optional object of methods groups.
The default configuration is:
{
order: [
'static-methods',
'lifecycle',
'everything-else',
'render'
],
groups: {
lifecycle: [
'displayName',
'propTypes',
'contextTypes',
'childContextTypes',
'mixins',
'statics',
'defaultProps',
'constructor',
'getDefaultProps',
'getInitialState',
'state',
'getChildContext',
'componentWillMount',
'componentDidMount',
'componentWillReceiveProps',
'shouldComponentUpdate',
'componentWillUpdate',
'componentDidUpdate',
'componentWillUnmount'
]
}
}
static-methods
is a special keyword that refers to static class methods.lifecycle
is referring to thelifecycle
group defined ingroups
.everything-else
is a special group that match all the methods that do not match any of the other groups.render
is referring to therender
method.
You can override this configuration to match your needs.
For example, if you want to place your event handlers (onClick
, onSubmit
, etc.) before render
but the other methods after it:
"react/sort-comp": [1, {
order: [
'static-methods',
'lifecycle',
'/^on.+$/',
'render',
'everything-else'
]
}]
With the above configuration, the following patterns are considered warnings:
var Hello = React.createClass({
render: function() {
return <div>Hello</div>;
},
onClick: function() {}
});
With the above configuration, the following patterns are not considered warnings:
var Hello = React.createClass({
onClick: function() {},
render: function() {
return <div>Hello</div>;
}
});
If you want to split your render
method into smaller ones and keep them just before render:
"react/sort-comp": [1, {
order: [
'static-methods',
'lifecycle',
'everything-else',
'rendering',
],
groups: {
rendering: [
'/^render.+$/',
'render'
]
}
}]
With the above configuration, the following patterns are considered warnings:
var Hello = React.createClass({
renderButton: function() {},
onClick: function() {},
render: function() {
return <div>Hello</div>;
}
});
With the above configuration, the following patterns are not considered warnings:
var Hello = React.createClass({
onClick: function() {},
renderButton: function() {},
render: function() {
return <div>Hello</div>;
}
});
This rule is a formatting preference and not following it won't negatively affect the quality of your code. If components organisation isn't a part of your coding standards, then you can leave this rule off.