You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 from redux-saga/effects version 1.0.5
This triggers the eslint error, though in practice I was passing some parameters:
const test = (yield select())();
The text was updated successfully, but these errors were encountered:
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?
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: