React.createClass versus extends React.Component
Two ways to do the same thing. Almost. React traditionally provided theReact.createClass
method to create component classes,and released a small Syntax sugar update to allow for better use with ES6 modules byextends React.Component
,which extends theComponent
class instead of callingcreateClass
.
These differences are subtle in places,but have quite a few interesting differences worth exploring,which will allow you to make the best decision for which is best for you.
Syntax differences
First,let’s explore the Syntax differences by looking at two code examples and annotating them.
React.createClass
Here we have aconst
with a React class assigned,with the importantrender
function following on to complete a typical base component definition.
import React from 'react'; const Contacts = React.createClass({ render() { return ( <div></div> ); } }); export default Contacts;
React.Component
Let’s take the aboveReact.createClass
definition and convert it to use an ES6 class.
class Contacts extends React.Component { constructor(props) { super(props); } render() { ></div> ); } } default Contacts;
From a JavaScript perspective we’re now using ES6 classes,typically this would be used with something like Babel to compile the ES6 to ES5 to work in other browsers. With this change,we introduce theconstructor
,where we need to callsuper()
to pass the props toReact.Component
.
For the React changes,we now create aclass
called “Contacts” andextend
fromReact.Component
instead of accessingReact.createClass
directly,which uses less React boilerplate and more JavaScript. This is an important change to note further changes this Syntax swap brings.
propTypes and getDefaultProps
There are important changes in how we use and declare default props,their types and setting initial states,let’s take a look.
React.createClass
In theReact.createClass
version,thepropTypes
property is an Object in which we can declare the type for each prop. ThegetDefaultProps
property is a function that returns an Object to create initial props.
= React.createClass({ propTypes: { }, getDefaultProps() { return { }; }, render() { default Contacts;
React.Component
This usespropTypes
as a property on the actualContacts
class instead of a property as part of thecreateClass
definition Object. I think it’s nicer Syntax to create class properties so it’s much clearer what are React APIs versus your own on the definition Object.
ThegetDefaultProps
has now changed to just an Object property on the class calleddefaultProps
,as it’s no longer a “get” function,it’s just an Object. I like this Syntax as it avoids more React boilerplate,just plain JavaScript.
></div> ); } } Contacts.propTypes = { }; Contacts.defaultProps = { }; default Contacts;
State differences
State is an interesting change,now we’re using constructors the implementation of initial states changes.
React.createClass
We have agetInitialState
function,which simply returns an Object of initial states.
= React.createClass({ getInitialState () { default Contacts;
React.Component
ThegetInitialState
function is deceased,and now we declare all state as a simple initialisation property in theHighlighter-rouge" style="padding:1px 5px; background-color:rgb(245,which I think is much more JavaScript-like and less “API” driven.
super(props); this.state = { }; } render() { default Contacts;
“this” differences
UsingReact.createClass
will automatically bindthis
values correctly for us,but changes when using ES6 classes affect this.
React.createClass
Note theonClick
declaration withthis.handleClick
bound. When this method gets called React will apply the right execution context tohandleClick
.
= React.createClass({ handleClick() { console.log(this); // React Component instance },170)"><div onClick={this.handleClick}default Contacts;
React.Component
With ES6 classes this is slightly different,properties of the class do not automatically bind to the React class instance.
super(props); } handleClick() { console.log(// null } render() { default Contacts;
There are a few ways we could bind the right context,here’s how we could bind inline:
// React Component instance } render() { this.handleClick.bind(this)}default Contacts;
Alternatively we could change the context ofthis.handleClick
inside theconstructor
to avoid inline repetition,which may be a better approach if moving to this Syntax to avoid touching JSX at all:
this.handleClick = this); } handleClick() { console.log(default Contacts;
Mixins
React mixins are no longer supported when using React components written in ES6.
React.createClass
WithReact.createClass
we can add mixins to components using amixins
property which takes an Array of available mixins. These then extend the component class.
'react'; var SomeMixin = { doSomething() { } }; = React.createClass({ mixins: [SomeMixin], handleClick() { this.doSomething(); // use mixin },254)">default Contacts;
React.Component
Mixins aren’t supported in ES6 classes.