From d893eb12e633df5838dc0bdc83feaae9f04c087a Mon Sep 17 00:00:00 2001
From: Robin Ricard <ricard.robin@gmail.com>
Date: Mon, 22 Aug 2016 14:47:09 +0200
Subject: [PATCH] Deactivate the `new-cap` rule in ESLint

This rule is considered dangerous in certain situations. This is especially true for Immutable.js users. See the discussion at issue #465 for more information about this.
---
 config/eslint.js | 1 -
 1 file changed, 1 deletion(-)

diff --git a/config/eslint.js b/config/eslint.js
index 761add0f718..b2fb7dd7bdc 100644
--- a/config/eslint.js
+++ b/config/eslint.js
@@ -62,7 +62,6 @@ module.exports = {
     'dot-location': ['warn', 'property'],
     eqeqeq: ['warn', 'allow-null'],
     'guard-for-in': 'warn',
-    'new-cap': ['warn', { newIsCap: true }],
     'new-parens': 'warn',
     'no-array-constructor': 'warn',
     'no-caller': 'warn',