Open noahnu opened 4 years ago
Thanks for reporting. I'll see when I have time to fix it. I think it depends where the spread object is defined. The rule would have to lookup the definition, which static code analyse can not do (so easily). Because the object could be defined in another module and imported into the linted file.
Sorry @noahnu I did not have time to tackle this yet and I am not sure when I will be able to.
@pke can you suggest any workaround? Adding // eslint-disable-next-line redux-saga/no-yield-in-race
has no effect - and then the only other possibility is to disable it for the whole file.
I found no workaround without patching the rule. I submitted PR #82 .
Given
Running eslint with the above results in:
This happens in the "no yield in race" rule. In
checkYieldInObject
, it assumes each property has a "key". TheExperimentalSpreadProperty
node does not have a key.If it's not reasonable to lookup the referenced object, a warning should be reported that object spread is not supported.