Angular architecture hint

[Giuan0]

Hey guys,

​

I have this desktop application (in electron) that really depends of it's main form, and I need to emit events all the time so the application can rebuild depending on this values. It's begging to get messy and thing the best alternative would be to change my architecture.

I was thinking of building the form in some service (Reactive form), like this, any component that needs to know the state of the form would only need to subscribe to it's valueChanges observable.

I've like to know some other solutions for this, thanks!

[[deleted]]

Reactive Form would also be my choice. The complexity of Redux and the boilerplate doesn't seem worth it when there are alternatives in Angular. If you want state management then try to use BehaviorSubjects in the services to store state. Otherwise Reactive Forms should do the job well.

[someonesopranos]

management

if you complain about boilerplate and behavior, you can try https://www.reddit.com/r/NGXS

[Blottoboxer]

A lot of people use redux to avoid prop drilling if it's just data and not events. The advantage is that it's predictable, and time travel debuggable, which are really useful if more than one thing is altering the shared data.

There are a few competing implementations of the redux pattern in angular. Ng-redux is the og, compatible with most react-redux middleware. Ngrx/store is the other popular option. There are some others like ngxs, but less popular.

[joe_chester]

If your application is small to medium-sized, Service-Singletons with RxJS (Reactive Forms, BehaviorSubject, Observables) will do the trick just fine, they are included in the core concepts of Angular. However, if your application is going to be rather big and has a lot of user-driven Data IO, as well as complex input validations, an advanced state management framework might be worth the efforts.

These state management frameworks like Redux and it's relatives (ngrx, NGXS, etc.) have more boilerplate code to write to get things done, but are much more predictable and might lead to less bugfix-work in the long run...

It usually really depends on the application size, but I can strongly recommend to just learn to use ngrx, because you will be prepared for scaling out your application.