Mike Ryan

@timdeschryver One challenge to overcome with built-in performance monitoring for selectors is that we don't have a name or symbol to point developers to when a selector has bad performance....

Implementation decisions in the algorithms of projector functions have stood out as a unique source of performance issues in NgRx apps that I've helped review. What I'd like to see...

@alex-okrushko This is the solution Brian and I use with clients right now. There are several drawbacks to this approach: 1. Documentation on how to use `createSelectorFactory` is lacking 2....

Looks like the probing may not be necessary soon. See ReactiveX/rxjs#2050

@alexeagle Definitely interested. I know we break it for Closure users semi-regularly but I don't know enough about Closure to add a useful compatibility test suite. cc @robwormald

@fxck I'm also doing a lot of form intensive development over the next month. Let's capture as many issues here in that time period and work on a design for...

Are you wanting it to be consistent across all ngrx projects? If that's the case, we'll need to update router, router-store, effects, notify, store-devtools, and store-log-monitor as well.

Sounds good. To be clear, the ES modules we output to `/lib` need to be ES5 with ES6 modules, correct?

Effects alternative: ### Effects An effect can be registered using the `withEffect` feature. An optional `eventName` can be supplied for an effect, which connects the output of the effect to...

> @anthony-b-dev > I'm a little confused by the heavy RxJS use in a signal based API, though. Seems a little counterintuitive. Especially needing to listen to events through an...