Tobias Bieniek
Tobias Bieniek
> What's the advantage of using eslint's --cache over the async caching from broccoli-persistent-filter? 1) currently when using `ember serve` ESLint is run once on startup and shows you all...
> So you think the changes need to occur in broccoli-lint-eslint then? If so, should I begin work there? `ember-cli-eslint` should just be a very thin wrapper around `broccoli-lint-eslint`. essentially...
@rwjblue @stefanpenner it's possible that I misunderstood the current implementation. I thought only the generated test files were persisted between builds.
Checking the keywords would certainly be the better option, but it is also a little more complex to code so I used `.ember-cli` as a good-enough heuristic. Feel free to...
`eslint:recommended` includes that rule, which is used by the default config in this project. maybe your local eslint isn't picking up that config?
@jasonmit do you have any clue _why_ this popped up with Mocha 3?
this is most likely related to https://github.com/teddyzeenny/ember-mocha-adapter/blob/master/adapter.js#L169-L172 and Mocha 3 having done some changes in the `.only()` handling
@phyrog yes, haven't found a good solution to this issue yet đ
@rwjblue in theory yes, but it would obviously be annoying for Mocha users that don't use async/await yet. I wanted to go back and see if there is really no...
that is **awesome**!! đ