Closed yumauri closed 1 year ago
Looks like an issue in effector-inspector If you set inspector option to true (which is a default) the issue occurs
Yep, looks like. Might it be because inspector calls event inside of compute step? https://github.com/effector/inspector/blob/master/src/index.ts#L235
UPD: I've tried to remove traceEffectRun
/traceEventTrigger
/traceStoreChange
events calls (line 222, line 235 and line 260) from installed inspector in node_modules folder, and issue in my repo has gone. So, looks like here is an issue, or at least, roots lay here.
Subj,
effector-logger
somehow breaks effector priorities, for example,sample
began to work earlier, than.on
, which completely breaks synchronous logic.Code
works differently, when you import from from
"effector-logger"
:import {} from "effector"
store$gate
containstrue
after calculationsimport {} from "effector-logger"
store$gate
containsfalse
after calculations, becausesample
executes earlier, than.on(passingBy
Repo with reproduce: https://github.com/yumauri/effector-logger-issue