Leonardo Montini

With proper moderation most of the issues will get answered/closed and simple bugs fixed, attracting new contributors... we just need some words from @iamkun :) I would be happy to...

We can discuss the implementation but I also agree having a `.uniq` shortcut is good :D

I also find the colors confusing in the current diagram. Taking the color of the last emitted value makes much more sense.

Yes the issue is definitely the effect being declared twice. As you can see in [ngrx docs](https://v8.ngrx.io/api/effects/createEffect), you no longer need the `@Effects` decorator when using `createEffect` otherwise it is...

Thank you for the reply! This indeed works if you want to set a value at first, and have a clean state :) However, if for example I type a...

I would say you can use an effect in between. 1. You dispatch an action with the info you currently have in the payload. 2. An effect can use `withLatestFrom`...

Maybe not the most efficient way, but you could save the values you want to keep before resetting and then set them back.

If you have a `Date` object you might want to learn more about [Value Conversion](https://ngrx-forms.readthedocs.io/en/master/user-guide/form-controls/#value-conversion) to let ngrx-forms handle it internally as a string, potentially avoiding your error. Back to...

I was having the same issue as some of my paths have the `$` sign. For everyone else coming here in the future here the solution that worked for me...

Hey, the link you provided in the example seems to be the default arrays example. Could you please update it with the link of a project reproducing the issue? :)