Rules tend to be noisy in test frameworks about eslint-plugin-fp HOT 3 OPEN

@nickmccurdy another solution is to recommend users us the Validation applicative function instead of asserts.

from eslint-plugin-fp.

Thanks for the link. I've used applicatives in Haskell, and while it's a great pattern for general purpose pure functional programming, I'm concerned that this works against the much more imperative styles of almost all popular JavaScript testing frameworks (Mocha, Jasmine, Jest, Ava, Tape). I could use this pattern in my implementation, but I would need to use a test framework that only uses applicatives and pure results (which as far as I'm aware doesn't exist yet, though I've been experimenting with one. One could write their own testing infrastructure from scratch to meet these rules, but I feel like that's a lot of work for a linting library to impose.

What do you think about my possible solutions? I just converted them to a numbered list.

from eslint-plugin-fp.

@nickmccurdy I like your option 3, but this package seem to be unmaintained 😢
Option 1 is also okayish.

from eslint-plugin-fp.