@@ -28,8 +28,7 @@ module.exports = {
28
28
// Mocha allows you to write asynchronous tests by adding a done callback to the parameters of
29
29
// your test function. It is easy to forget calling this callback after the asynchronous
30
30
// operation is done.
31
- // @TODO (semver-major): Raise to `error`
32
- 'mocha/handle-done-callback' : 'warn' ,
31
+ 'mocha/handle-done-callback' : 'error' ,
33
32
34
33
// Limit the number of top-level suites in a single file
35
34
// This rule enforces having a limited amount of top-level suites in a file.
@@ -52,16 +51,14 @@ module.exports = {
52
51
// Disallow tests to be nested within other tests
53
52
// This rule looks for all test cases (it, specify and test) or suites (describe, context and
54
53
// suite) which are nested within another test case.
55
- // @TODO (semver-major): Raise to `error`
56
- 'mocha/no-nested-tests' : 'warn' ,
54
+ 'mocha/no-nested-tests' : 'error' ,
57
55
58
56
// Disallow returning in a test or hook function that uses a callback
59
57
// Mocha's tests or hooks (like before) may be asynchronous by either returning a Promise or
60
58
// specifying a callback parameter for the function. It can be confusing to have both methods
61
59
// used in a test or hook, and from Mocha v3 on, causes the test to fail in order to force
62
60
// developers to remove this source of confusion.
63
- // @TODO (semver-major): Raise to `error`
64
- 'mocha/no-return-and-callback' : 'warn' ,
61
+ 'mocha/no-return-and-callback' : 'error' ,
65
62
66
63
// Disallow setup in describe blocks
67
64
// Any setup directly in a describe is run before all tests execute. This rule reports all
0 commit comments