safer type checking (#179)

* safer type checking

Check for the existence of `node.property` before comparing `node.property.name`

* add test for fix case

In the scenario where you are importing from another file that has a `createClass` method with no name associated (such as a React abstraction), this can blow up if you have a custom `createReactClassName`.

* make test more realistic

Author: tquetano-netflix

src/index.js

@@ -224,7 +224,8 @@ export default function(api) {
 
                 return (
                   currentNode.get('callee').node.name === globalOptions.createReactClassName ||
-                  currentNode.get('callee').node.property.name === 'createClass'
+                  (currentNode.get('callee').node.property &&
+                    currentNode.get('callee').node.property.name === 'createClass')
                 )
               })
 

test/fixtures/react-create-class-custom-name-no-property-name/actual.js

@@ -0,0 +1,9 @@
+var { createClass } = require('./notReact')
+var PropTypes = require('prop-types')
+
+var Class1 = createClass({
+  displayName: 'Class1',
+  propTypes: {
+    foo: PropTypes.string,
+  },
+})

test/fixtures/react-create-class-custom-name-no-property-name/expected-remove-es6.js

@@ -0,0 +1,7 @@
+var {
+  createClass
+} = require('./notReact');
+
+var Class1 = createClass({
+  displayName: 'Class1'
+});

test/fixtures/react-create-class-custom-name-no-property-name/notReact.js

@@ -0,0 +1,5 @@
+var createClass = a => a;
+
+module.exports {
+  createClass
+}

test/fixtures/react-create-class-custom-name-no-property-name/options.json

@@ -0,0 +1,3 @@
+{
+  "createReactClassName": "createClass"
+}