-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported Callee of type YieldExpression for CallExpression #194
Comments
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:
The text was updated successfully, but these errors were encountered: