Open mjohnst opened 2 years ago
Yes, that's definitely a bug. Thanks!
Theoretically, if you had a select function that returns functions and then we'd not be able to scan it. Because you could return whatever function, which is a hard-stop for all sorts of static analysis.
I think we have some existing code that gives up and says "ok, that's bad. stop doing that" which I could reuse. I'm pretty sure the YieldExpression is just an omission here.
@mjohnst: Do I correctly understand that you were just messing around and this is not blocking some sort of important work?
@mozfreddyb correct, this is not blocking me at all
Writing react/redux code in Typescript and was experimenting to see if I could call result of yield'd
select
with some parameters (I do not believe you can actually do this, but I was just seeing if it would work).select
fromredux-saga/effects
version1.0.5
This triggers the eslint error, though in practice I was passing some parameters: