Skip to content

Commit f67f4a9

Browse files
committed
Fix linting errors
In #1277 we enabled some new eslint rules, but the branch hadn't been freshly rebased, so a few failures snuck in. I fixed these by running ```sh npm run lint -- --fix ```
1 parent d672588 commit f67f4a9

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

lib/rules/boolean-prop-naming.js

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ module.exports = {
4747
const propTypeNames = config.propTypeNames || ['bool'];
4848

4949
// Remembers all Flowtype object definitions
50-
var objectTypeAnnotations = new Map();
50+
const objectTypeAnnotations = new Map();
5151

5252
/**
5353
* Checks if node is `propTypes` declaration

tests/lib/rules/boolean-prop-naming.js

+4-4
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,12 @@
88
// Requirements
99
// ------------------------------------------------------------------------------
1010

11-
var rule = require('../../../lib/rules/boolean-prop-naming');
12-
var RuleTester = require('eslint').RuleTester;
11+
const rule = require('../../../lib/rules/boolean-prop-naming');
12+
const RuleTester = require('eslint').RuleTester;
1313

1414
require('babel-eslint');
1515

16-
var parserOptions = {
16+
const parserOptions = {
1717
ecmaVersion: 6,
1818
sourceType: 'module',
1919
ecmaFeatures: {
@@ -25,7 +25,7 @@ var parserOptions = {
2525
// Tests
2626
// ------------------------------------------------------------------------------
2727

28-
var ruleTester = new RuleTester({parserOptions});
28+
const ruleTester = new RuleTester({parserOptions});
2929
ruleTester.run('boolean-prop-naming', rule, {
3030

3131
valid: [{

0 commit comments

Comments
 (0)