Adds mocha-aware prefer-arrow-callback rule #163
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #141
prefer-arrow-callback
rule code, test code, and markdown doc from: https://github.com/eslint/eslint/blob/master/docs/rules/prefer-arrow-callback.mdastUtils.isMochaFunctionCall(node, scope)
prefer-arrow-callback
rule before enabling themocha/prefer-arrow-callback
ruleThe following eslint rules are failing with this code:
It looks like it will take some substantial work to get this code in line with the complexity limit of 4. I think it would be preferable to not completely rewrite this rule so that updates from the core eslint
prefer-arrow-callback
rule can be applied more easily here in the future. Would the maintainers here be open to a rule-specific relaxing of the complexity and max-statements eslint rules (now included in code changes)?