An updater/patchState/setState call is always triggered after an effect call

[m1h1r0]

Which @ngrx/* package(s) are the source of the bug?

component-store

Minimal reproduction of the bug/regression with instructions

My code at hand is messy so I can only give a pseudo example. Let's say I have a ComponentStore:

// State has a property foo, initially 0
propertyFooInState$ = select((state)=>state.foo);
// An updater to update foo
updaterA = updater<string>((state, foo)=> {...state, foo});
// An effect to print out foo's latest value
effectB = effect<>(trigger$)=> { return trigger$.pipe(withLatestFrom(propertyFooInState$), tap([_ , foo] => console.log(foo) }

When I call the updaterA and effectB in order:

someOtherObservable.subscribe(()=>{
  // Update foo's value to 1
  updaterA(1);
  // Print out foo's latest value
  effectB();
}

I would expect that foo being updated to 1, and printed out. However the effect gets triggered before the updater, and I see 0 being printed out.

Expected behavior

Expected: the updaterA takes effect and update the foo's value, and THEN the effect call takes effect to print out the latest foo's value.

Versions of NgRx, Angular, Node, affected browser(s) and operating system(s)

All latest versions of NgRx etc.

Other information

No response

I would be willing to submit a PR to fix this issue

• Yes
• No

[m1h1r0]

I notice in the source code that updater is called with 'observeOn(queueScheduler)', while effect is not. I don't fully understand what queueScheduler does. Is that what causes this issue? And why isn't effect using the queueScheduler?