So I suggest you to remove this line.
remove compose filtering
As a developer I expect my code to throw an Error, not eat it. Also I strongly opposite to extra useless computations in redux. Why not to filter functions outside of compose if you really need this?
So big 👍 to this PR
This breaks the @evilj0e's use case described in #2073
But throwing errors explicitly is definitely a better thing.
What if it were to only filter out falsey?
@jimbolla why filter something at all?
The problem described in #2073 can be solved in many ways by one-liner. But the fix from #2073 is a fix of a particular codebase problems and it leads to ommited errors and performance regressions in others people code
One can filter everything he wants to outside of compose. It's so easy I can't even
Good points being made. Thanks!