Linus Unnebäck
Linus Unnebäck
It won't be a problem in the case of mocha though, since you always call the `done` callback somehow, if your test is asynchronous...
```js test('no callback (array)', function (t) { t.plan(2) var tasks = [ function (cb) { t.pass('cb 1') }, function (cb) { t.pass('cb 2') } ] parallel(tasks) }) ``` Seems like...
@klaemo nice find! Would be happy to accept a PR to improve the documentation
I personally think that looks better with an empty line between it ☺️ ```js if (...) { // something } if (...) { // another if } ```
Hmm, actually, I didn't understand that current ESLint versions still uses the object syntax. I thought that the change in Standard was due to upgrading to a newer ESLint version....
It seems like the following code is now producing two errors 🤔 ``` var foo = 1 var bar = function () {} bar(foo) ``` https://github.com/standard/eslint-config-standard/blob/176bbdd49bb929119c0227f27f54aa30f4b35e5b/test/validate-config.js#L12-L14
Have a look at [standardx](https://github.com/standard/standardx), it should suite your needs ☺️
I personally prefer there to be only one way of doing things, and, perhaps unfortunately, we already enforce it to be without spaces. Switching now could potentially be painful for...
@AbducteeZero you comment doesn't add anything of value at all, and instead just insults the people working on this project. Clearly there was grounds for adding the rule when it...
Ultimately up to @feross, I'm okay with it ☺️