Angular 16 support

[matthewtquinn1]

Hi there,

I see that this repository is using deprecated versions of products such as Angular and RxJs.

Are there plans to upgrade to support Angular 16 and RxJS 7 etc.?

If you need any more information or support, let me know.

Many thanks,
Matthew Quinn

[craiggoldstone]

Our team would love to know this too. Sadly we are avoiding adoption of this awesome library because it appears to have lost momentum, with very few changes in 3 and almost 4 years. I guess the code is stable, which is great, but without ongoing fixes and library updates it does appear to be a risk we aren't willing to take right now.

@MrWolfZ please let us know if you plan on continuing support for ngrx-forms or would like help in doing so?

[MrWolfZ]

Hi there. The library is indeed in what I would call the "minimal maintenance mode" where I only do the most important fixes (for example, it is still using the old style of dispatching actions via ngrx). Unfortunately I've been out of frontend and particularly Angular development for quite some time now, which makes it tricky to keep up to date with all the latest and greatest changes in the Angular world.

The library itself is designed to have minimal dependencies (it doesn't even depend on rxjs for example, that is just used in the example app). The only true dependencies are @angular/forms and @ngrx/store and so far those have been mostly stable.

I fully understand the reluctance to adopt the library in this state. The ideas of this library also certainly go against what the Angular teams wants devs to do with forms. So maybe the wiser choice is to stay/move away from it. However, I am certainly welcoming any help in keeping the dependencies and the examples up to date, so if you are willing to provide PRs I'll gladly release a new version. Alternatively you could also consider to fork the repo and release a continuously updated version that doesn't depend on me. I'll gladly link to it in the README.

[fxck]

Works fine with Angular 16. Some minor changes needed to support the new material components, but otherwise it's still fine.

[ZsZs]

Hi, I'm particularly interested if SignalStore will be supported?

Thanks for your feedback.

[deefdragon]

@MrWolfZ Id be willing to submit some code to try to get at-least ngrx/component-store supported, but Im not sure the best place to start.

From when I experimented with it previously, I was able to put a form in the component store state and read values from the store to the display, but entering data into the form would not update the state (tho it would emit the events on the global store).

My understanding is that that is due to how ngrx-forms emits events to the global store, and how the component store cant then consume them. Do you have any recommendations on where I would need to start looking to update these patterns to allow component store?

From what I'm seeing looking at the code, I think I need to adjust how dispatchAction works to accept a non-global dispatch? (and the add some way to consume in the associated component store)

Edit: Having done more digging, it appears that it should be possible to use the ngrxFormsAction output on the form and the inputs to link the form to the state in the componentStore (I was able to get this functioning), but its not ideal. Would be nice to be able to set it just on the root level form and listen in on all input updates. I'm going to see if I can make a PR for that or something similar.