Mathias Schreck
Mathias Schreck
Hello @perrin4869, thanks for raising this issue. This is indeed a problem, in several rules of this plugin. I have already an idea how to fix it and started a...
ESLint v7 is already declared as a peer dependency since `eslint-plugin-mocha` v7. So this is nothing new. The comment you mentioned seems also correct given the context that it was...
It is a mocha hook when using the TDD interface, you can read more about it in the [official mocha docs](https://mochajs.org/#tdd). However, I think it would be a good idea...
Which parser are you using? I think this should be rather fixed in `@typescript-eslint/parser`.
Thanks for the issue. The problem with the example you provided is that it depends on where `runSomeTests` is called, so it could create a sibling hook if it would...
@ljharb I think this is not the same issue as described here, but I fully agree with you that rules in this plugin should track where the identifiers are coming...
If this is only a problem with third-party parser but not the default parser I would think this is an issue in the parsers.
If someone provides an easy fix that doesn’t need to interact with `@typescript-eslint/parser` directly I’m happy to review and merge a PR.
Yes, I think you are right. The current implementation explicitly checks for a `CallExpression` of `done` or its direct parent, so passing `done` to a function should work but not...
Mocha always expects the `done` callback parameter to be the first argument. The behavior of injecting the `browser` parameter is added by nightwatch and is not compatible with the default...