enhance require-jsdoc to recognize function expressions

ESLint-version: 1.10.3, default parser

configuration:

"require-jsdoc":
                [
                        2,
                        {
                                "require":
                                {
                                        "FunctionDeclaration": true,
                                        "MethodDefinition": false,
                                        "ClassDeclaration": false
                                }
                        }
                ],

Running eslint (from a grunt task), I would expect this to cause an error:

module.exports.foo = function foo() {
    return 'bar';
}

Instead, it passes through fine.

So that’s why I would propose an enhancement to the require-jsdoc rule to also recognise missing JSDoc blocks in functional expressions such as the above.

All of the below should pass through fine:

/**
* some description
* 
* @returns {string}
*/
module.exports.foo = function foo() {
    return 'bar';
}

/**
 * some description
 *
 * @returns {string}
 */
foo: function() {
    return 'bar';
}

[mightypenguin]

Pinging this so people know there is still interest. This would bring my documentation to 90+%.

All I care about is: A) var myfunc = function() {}

B) var object = { myfunc: function() {} }

[sunjay]

The code I would like this to work for looks like this:

const Actions = {
  actions: new Set(),
  register(name) {
    ...
  },
};

Similar to what everyone else is presenting except instead of register: function(name) { I’m using register(name) { which is allowed in ES6.