React style guide – forked from https://github.com/Khan/style-guides/blob/master/style/react.md

react.md

React style guide

Follow the normal Javascript style guide - including the 80 character line limit. In addition there are several React-specific rules.

In addition to these style rules, you may also be interested in React best practices.

---

Syntax

Order your methods with lifecycle first and render last.

Within your react component, you should order your methods like so:

1. lifecycle methods (in chronological order: getDefaultProps, getInitialState, componentWillMount, componentDidMount, componentWillReceiveProps, shouldComponentUpdate, componentWillUpdate, componentDidUpdate, componentWillUnmount)
2. everything else
3. render

Name handlers handleEventName.

Example:

<Component onClick={this.handleClick} onLaunchMissiles={this.handleLaunchMissiles} />

Name handlers in props onEventName.

This is consistent with React's event naming: onClick, onDrag, onChange, etc.

Example:

<Component onLaunchMissiles={this.handleLaunchMissiles} />

Open elements on the new line.

Easier on the eyes, eaily distinguishable.

Yes:

return (
    <div>
        ...
    </div>
);

No:

return <div>           // div on the same line as return
   ...
</div>;

Align and sort HTML properties.

Fit them all on the same line if you can. If you can't, put each property on a line of its own, indented four spaces, in sorted order. The closing angle brace should be on a line of its own, indented the same as the opening angle brace. This makes it easy to see the props at a glance.

Yes:

<div className="highlight" key="highlight-div">
<div
    className="highlight"
    key="highlight-div"
>
<Image
    className="highlight"
    key="highlight-div"
/>

No:

<div className="highlight"      // property not on its own line
     key="highlight-div"
>
<div                            // closing brace not on its own line
    className="highlight"
    key="highlight-div">
<div                            // property is not sorted
    key="highlight-div"
    className="highlight"
>

Only export a single react class.

Every .jsx file should export a single react class, and nothing else. This is for testability: the fixture framework requires it to function.

Note the file can still define multiple classes, it just can't export more than one.

---

Language features

Make "presentation" components pure.

It's useful to think of the React world as divided into "logic" components and "presentation" components.

"Logic" components have application logic, but do not emit HTML themselves.

"Presentation" components are typically reusable, and do emit HTML.

Logic components can have internal state, but presentation components never should.

Prefer props to state.

You almost always want to use props. By avoiding state when possible, you minimize redundancy, making it easier to reason about your application.

A common pattern -- which matches the "logic" vs. "presentation" component distinction -- is to create several stateless components that just render data, and have a stateful component above them in the hierarchy that passes its state to its children via props. The stateful component encapsulates all of the interaction logic, while the stateless components take care of rendering data in a declarative way.

Copying data from props to state ​can cause the UI to get out of sync and is especially bad.

Use propTypes.

React Components should always have complete propTypes. Every attribute of this.props should have a corresponding entry in propTypes. This documents that props need to be passed to a model. (example)

If you as passing data through to a child component, you can use the prop-type <child-class>.propTypes.<prop-name>.

Avoid these non-descriptive prop-types:

• React.PropTypes.any
• React.PropTypes.array
• React.PropTypes.object

Instead, use

• React.PropTypes.arrayOf
• React.PropTypes.objectOf
• React.PropTypes.instanceOf
• React.PropTypes.shape

As an exception, if passing data through to a child component, and you can't use <child-class>.propTypes.<prop-name> for some reason, you can use React.PropType.any.

Never store state in the DOM.

Do not use data- attributes or classes. All information should be stored in Javascript, either in the React component itself, or in a React store if using a framework such as Redux.

---

React libraries and components

Do not use Backbone models.

Use flux actions, or $.ajax directly, instead.

We are trying to remove backbone from our codebase entirely.

Minimize use of jQuery.

Never use jQuery for DOM manipulation.

Try to avoid using jQuery plugins. When necessary, wrap the jQuery plugin with a React component so you only have to touch the jQuery once.

You can use $.ajax (but no other function, such as $.post) for network communication.

Reuse standard components.

If possible, re-use existing components, especially low-level, pure components that emit html directly. If you write a new such one, and it finds a user in a different project, put it in a shared location such as the react.js package.

The standard shared location for useful components that have been opensourced is the react-components.js package in javascript-packages.json. This includes components such as these:

• SetIntervalMixin - provides a setInterval method so something can be done every x milliseconds
• $_ - the i18n wrapper to allow for translating text in React.
• TimeAgo - “five minutes ago”, etc - this replaces $.timeago

Reusable components that have not (yet) been opensourced are in the (poorly named) react.js package. This include components such as these:

• KUIButton - render a Khan Academy styled button.
• Modal - create a modal dialog.

This list is far from complete.