7.0.0

Breaking Changes

We've added a new rule, object-shorthand, that's turned on by default with the option "properties":

// Good
const foo = {
  x,
  y,
  z,
};

// Bad
const foo = {
  x: x,
  y: y,
  z: z,
};

6.0.0

Breaking Changes

Introducing a new eslint rule to add true explicitly.

Example

// Good
<video controls />

// Bad
<video controls={true} />

Why is this valuable?

It's the ol' Implicit vs explicit approach. Implicit is great because sure it looks nicer and once you know what's going on in the code you don't need the explicit explanation. Still it's important to consider new team members reading our codebase, it benefits the entire development team so everyone has a clearer view of what is connected to what + it's more readable.

5.2.0

Added two new default rules related to flowtype:

• flowtype/use-flow-type
• flowtype/define-flow-type

5.1.1

Breaking Changes

The npm package was moved into the @zapier organization. To resolve, change your eslint config to point to @zapier/zapier instead of just zapier:

{
-  "plugins": ["zapier"],
-  "extends": ["plugin:zapier/prettier"]
+  "plugins": ["@zapier/zapier"],
+  "extends": ["plugin:@zapier/zapier/prettier"]
}

If you are referencing any custom rules directly, make sure to change those too:

{
   "rules": {
-    "zapier/disallow-lodash-get-dot-notation": "error",
+    "@zapier/zapier/disallow-lodash-get-dot-notation": "error",
   }
}

Other Changes

• Changed yoda rule to allow yoda conditions in range comparisons which are wrapped directly in parentheses, including the parentheses of an if or while condition (A range comparison tests whether a variable is inside or outside the range between two literal values).

4.0.0

Breaking Changes

• Added new rule flowtype/no-types-missing-file-annotation and turned it on by default. This rule enforces flow pragma in files that need it.

3.1.0

Breaking Changes

• Rule disallow-lodash-get-dot-notation now also reports on _.get calls with template literals.

New Features

• Added an autofixer for disallow-lodash-get-dot-notation rule.

3.0.0

Breaking Changes

• Converts to an ESLint plugin instead of config
• The new disallow-lodash-get-dot-notation rule is turned on by default

New Features

• New rule: disallow-lodash-get-dot-notation

2.1.0

New Features

• Adds prettier support. See README for more information.

2.0.0

Breaking Changes

• Enabled no-var and prefer-const rules