That is a great idea!

+1

On Mon, Nov 26, 2018 at 10:19 AM Tibor Meller <tibor.mel...@gmail.com>
wrote:

> Shane, Thanks for gathering the information and raising this.
> I also feel that our UIs reached a level of complexity what makes this to a
> reasonable next step.
> This complexity on the client side will grow in the future and I believe it
> is better to prepare instead of trying to make huge refactorings later.
> NgRx/Redux is quiet the industry standard architectural library in both
> React and Angular realm. Pretty well known in the community.
> I would be happy to move forward with NgRx.
>
> On Fri, Nov 23, 2018 at 3:44 PM Shane Ardell <shane.m.ard...@gmail.com>
> wrote:
>
> > What I'm referring to is roughly the entire contents of the UI
> > application's memory.
> >
> > On Thu, Nov 22, 2018 at 6:29 PM Otto Fowler <ottobackwa...@gmail.com>
> > wrote:
> >
> > > Can you describe what you mean by “state” in a little more detail?
> Not a
> > > complete description, maybe just a crib list.
> > >
> > >
> > > On November 22, 2018 at 07:21:43, Shane Ardell (
> shane.m.ard...@gmail.com
> > )
> > > wrote:
> > >
> > > As both the Management and Alerts UI grow in size, managing application
> > > state continues to become more and more complex. To help us deal with
> > > managing all of this state and ensuring our application derives state
> > from
> > > a single source of truth, I suggest we start using NgRx, a state
> > > management
> > > library based on the Redux pattern but built for Angular. It is by far
> > the
> > > most popular library of this type for Angular. As you can see in the
> > > project's GitHub Insights tab <https://github.com/ngrx/platform/pulse
> >,
> > > it's quite actively worked on and releases are pretty frequent. The
> > > project
> > > is licensed under MIT.
> > >
> > > As far as an approach to integration, I don't think we necessarily
> need a
> > > big refactoring right off the bat. I feel something like this can be
> done
> > > in a piecemeal approach over time. I think we can start by introducing
> it
> > > into the project the next time we have a new application feature.
> > >
> > > What are everyone's thoughts around this?
> > >
> > > Cheers,
> > > Shane
> > >
> > >
> >
>

Reply via email to