Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Rule Proposal: func-name-matching

See original GitHub issue

From requireMatchingFunctionName.

This rule will enforce function expression names with the variable name (or property name) which is the destination of the assignment.

Options

{
    "func-name-matching": ["error", {"module.exports": "ignore"}]
}

module.exports - The setting for module.exports = function foo() {};
- "ignore" (default) - The function is ignored.
- "propertyName" - The function’s name should be exports. Original JSCS rule has this option.
- (in my head, in future) "fileName" - The function’s name should match camelcase of the file name.

Examples:

/*eslint func-name-matching: "error"*/

// ✔ GOOD ---------------------------------------------------------------------
let foo = function foo() {};
foo = function foo() {};
obj.foo = function foo() {};
let obj = {foo: function foo() {}};

// ignore anonymous function expressions.
// it's warned by `func-names` rule.
let foo = function() {};
foo = function() {};
obj.foo = function() {};
let obj = {foo: function() {}};

// ignore it if it's not assigned
foo(function bar() {});

// ignore 'module.exports' by default.
module.exports = function foo() {};


// ✘ BAD ----------------------------------------------------------------------
let foo = function bar() {};
foo = function bar() {};
obj.foo = function bar() {};
let obj = {foo: function bar() {}};

// Should warn simple computed properties from original JSCS rule.
obj["foo"] = function bar() {};
let obj = {["foo"]: function bar() {}};