New Rule: no-callback-literal

What does everyone think of a rule that more strictly enforce the callback pattern? This will help people avoid the common mistake of calling back with an error message instead of an error object, which can lead to all sorts of weird bugs.

There is already this similar rule in ESLint: http://eslint.org/docs/rules/no-throw-literal

Here is how it will work:

Allowed

callback(null)
callback()
callback(undefined)
callback(null, data)
callback(err)
callback(someRandomVariable)
callback(new Error("error!~"))

Not allowed

callback(true)
callback("there was an error")
callback(1)

Of course we can figure out if we should include cb and next as well as callback in the list of allowed function names.

[dcousens]

The lack of callback(...args) support is a bit lame.

[dutchenkoOleg]

What about

return cb(...someArray);

why it’is error?