►
From YouTube: Reactive libraries for Angular
Description
NgRx Store provides reactive state management for Angular apps inspired by Redux. Unify the events in your application and derive state using RxJS.
Brandon is a Web dev, Architect @ Nrwl, tech writer, NgRx maintainer, GDE, sports, and slinger of gifs. Streaming on Twitch https://twitch.tv/brandontroberts
Join bdougie and friends live for Open Source Fridays at https://www.meetup.com/GitHub-Virtual-Meetup
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
Google+: http://google.com/+github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
B
A
B
A
Yeah,
so
reactive
programming
to
me
is
kind
of
is
a
like
a
shift
in
the
normal
program
that
we're
used
to
where
you
have
you're
calling
commands
or
you're
performing
these
actions.
And
then
you
can't
you
kind
of
constantly
have
to
pull
or
check
to
see
if
certain
data
is
ready
or
if
something
has
happened
or
if
some
event
has
been
triggered
that
you
need
to
perform.
Some
task
against
reactive
programming
is
a
flip
of
that.
A
So
it
used
more
of
a
push
based
approach
to
where
you
listen
for
changes
and
when
those
changes
happen,
you
automatically
get
them
as
a
as
a
subscriber
to
those
events
and
rxjs
provide.
What
we
use
on
rxjs
provides
apis
to
allow
you
to
use
those
reactive
patterns
and
build
on
top
of
those
in
a
standardized
api,
as
opposed
to
like
say
you
having
a
poll
whether
something
has
been
updated
or
in
the
case
of
angular
applications.
A
B
A
Those
messages
that
are
coming
out
of
a
websocket
or
even
pub
sub
would
be
another
example
of
something
that's
more
push
based,
and
you
could
actually
wrap
an
observable
around
some
clubs
of
service
and
use
it
as
your
primary
api
to
for
your
consumers
to
listen
to
changes
as
opposed
to
everybody.
Having
a
you
know,
subscribe
to
the
club
sub
or
website
directly
so
they're
similar
in
that
way.
But
the
rxjs
and
observables
is
more
of
a
standalone
thing
because
you
can
use
like
say
you
can
use
websockets
with
rxjs.
A
A
Yeah
see
ya,
they
say
a
war
eagle
see
see.
This
is
where
the
this
is,
where
the
the
issue's
coming
in
see.
I'm
I
live
in
alabama,
but
okay.
I
lived
here
long
enough
to
say
I'm
from
alabama,
but
I'm
a
tennessee
transplant.
So
I'm
I'm
go
vols,
I'm
you
can
say
war
eagle
and
that's,
okay.
You
could
say
a
road
tie
but
tennessee
volunteers
over
here,
so
yeah.
B
Yeah
and
I
think
some
people
might
be
confused
because
I
know
we
have
some
uk
people
representing
in
the
chat
too
as
well,
who
are
silent,
we're
talking
about
football,
but,
oh
yes,
but
we're
actually
talking
about
american
football.
So
this
this
sort
of
banter
that's
happening
right
now,
it's
very
similar
to
like
football
over
there
in
europe
as
well,
so
yeah
sports.
It's.
B
B
A
B
A
B
A
B
B
A
B
Yeah
we
have
people
well,
I
guess
putin
is,
though,
he's
from
he's
from
huntsville
and
then
silicon
darks
in
atlanta.
So
if
you're
interested
definitely
check
out
the
conference,
I'm
not
sure
if
there's
a
remote
version
of
this
this
year,
but
zach
does
a
really
good
job
at
conferences,
so
I'm
sure
whatever
he
does.
It
will
be
pretty
good,
so
highly
recommend,
but
I'm
curious:
can
we
just
zoom
back
I'm
trying
to?
B
A
So
way
back
in
high
school
now
but
yeah,
I
got
into
tech
and
programming
in
high
school
and
I'm
just
gonna
admit
it
like
I'm
an
old
man.
So
I,
when
I
was
in
high
school
qbasic,
was
the
the
programming
language
of
choice
that
we
had
in
our
science
class
or
in
our
what's
kind
of
what
you
call
them.
Extracurricular
classes
yeah,
so
we
used
qbasic
and
I
really
enjoyed
doing
that.
I
think
the
first.
The
app
that
I
can
remember
building
was
a
basketball.
A
It
was
like
a
basketball
game,
so
it
was
completely
written
in
q,
basic
the
it
was
basically
like
a
stick
man
who,
who
I
had
a
stick,
man
and
a
goal
that
went
up
and
down
and
it
waited
until
you
pressed
the
button
on
the
keyboard
to
try
to
shoot
the
ball
and
if
you're,
you
know,
if
the
arc
was
correct,
then
you
timed
it
right.
Then
it
would
of
course
go
in
the
basket.
So
that
was
pretty
much
my
first
program.
A
The
first
time
around
came
back,
came
back
to
work,
and
but
I
was
still
like
doing
projects
on
the
side
like
little
side
projects
and
everything.
So
one
project
I
had
like
a
while
back
programming.
It
was
just
another
html.
This
was
back
when
this
was
back
when
tables
were
hot,
html,
css
and
a
little
bit
of
javascript,
but
it
was
a.
It
was
like
an
audio
site
where
you
could
go
and
listen
to
like
streaming
audio
tracks,
so
it's
just
a
little
homegrown
site
there.
A
But
along
that
way
I
had
worked.
I
had
done
side
projects
and
I
was
kind
of
working
through
school
and
I
ended
up
getting
going
through
like
community
college
and
going
through
getting
my
bachelor's
degree,
and
then
I
got
my
first
professional
job
as
a
php
developer,
so
I
was
working
actually
out
at
marshall
space
flight
center
that
we
talked
about
earlier
building
web
apps
for
like
their
support
systems,
so
it
was
like
php,
html,
css
and
just
a
sprinkling
of
javascript
in
there
for
that.
A
So
I
worked
there
for
a
little
while
and
moved
there
to
other
jobs.
Where
I
was,
I
had
to
get
my
put
my
feet
to
the
fire
with
jquery
and
build
some
maps
with
that
built
some
interactive,
interactive,
interactive
apps
with
html,
css
and
jquery,
and
then
kind
of
moved
on
to
other
projects
that
were
like
across
a
many
different
spans
of
technologies.
Like
say,
jquery
was
one
that
I
worked
on.
I
did
c-sharp
back-end
projects
and
one
project
that
I
think
is
still
active
today
is
sencha
js.
A
A
B
A
B
A
Years,
it's
been
at
least
10.
I
think
10
12
years,
but
yeah
the
we
built
the
site
to
like
expose
the
stats
to
the
players
of
the
you
know:
players
of
the
game.
So
you
can
see
what
level
you're
on
what
ranked
you're
on
and
we
built
some
other
things.
Some
other
web
properties
that
basically
promoted
stem
and
things
that
were
tailored
towards
taylor
story
stem
activities,
but
I
also
had
the
angle
of
if
you
were
interested
in
getting
into
the
military.
It
kind
of
suddenly
hinted
you
and
hey.
B
Yeah
I
mean
for
the
word
context,
and
maybe
you
maybe
I
I
this
is
the
context
I
had,
because
it
was
a
game
like
just
like.
Like
now,
everybody
plays
fortnite.
It
was
a
little
more
realistic
than
fortnight,
so
like
more
like
call
of
duty
before
call
of
duty
was
the
thing,
but
basically
first
person
shooter,
you
start
off,
like
even
the
training
was
like
you
start
off
in
boot
camp.
It
was
like
one
of
the
first
games.
B
I
remember
actually
doing
like
a
proper
boot
camp
and
a
game,
and
then
it's
just
an
online
shooter
where
you
just
do
like
army
drills
or
you
go,
take
out
terrorists
but
yeah.
It
was
quite
a
piece
of
like
I
don't
know.
If
it'd
be,
you
call
it
propaganda
or
whatever,
but
the
goal
was
to
sell
you
on
the
army
and
then
like
recruit
you
and
like
make
that
make
that
an
interesting
thing.
A
B
A
A
Yeah,
it
was
called
yeah,
it
was
called
angular
2
at
the
time,
yeah
yeah,
and
I
got
in
like
during
the
alpha
stages
of
that.
So
we
started
building
the
other
good
thing
about
working.
There
was
we
got
to
experiment
a
lot,
so
we
were,
you
know,
definitely
there
in
the
angular
2
alpha
days
and
we're
building
actual
apps
with
it
and
trying
to
see
what
we
could
do
with
it.
A
So
that
was
how
I
got
involved
in
the
angular
ecosystem
itself
and
how
I
got
involved
in
like
the
open
source
side
of
it
was,
of
course,
anglers
open
source.
So
I
wanted
to
get
involved
with
like
the
angular
router,
because
in
angularjs,
like
nobody
pretty
much,
nobody
used
the
one
that
was
built
in
yeah,
so
I
wanted
to
like
contribute
to
making
the
one
in
angular
2.0
a
lot
better.
A
So
I
basically
jumped
in
github
issues
and
tried
to
help
people
where
I
could
pull
down
sample
repos
and
try
to
build
things
with
it
and
kind
of
learned
it
that
way.
And
so,
if
we
fast
forward
that
I
had
gotten
involved
with
the
angular
router
and
then
we
had
built
something
like
that
built
some
things
with
america's
army
internally,
and
one
of
them
was
basically
an
angular
version
of
redux.
A
That
we
had
built
there,
but
we
couldn't
open
source
it
because
those
things
just
weren't
in
place
at
the
time
to
do
so
then
ngrx
comes
along
and
the
founder
of
indirect
his
name
is
rob
wormwald.
He
used
to
work
for
google
on
the
angular
team,
so
he
started
the
project.
Basically
as
a
weekend
project
for
it
called
it.
Ngrx
store
was
basically
an
angular
version
of
redux.
A
B
A
B
A
B
A
B
I'm
curious
of
how
you
approach
getting
open
source
contributions
and
work
done
and
maintaining,
because
I
tend
to
just
do
it
during
work
hours.
So,
like
you
get
to
the
point
where
you
just
do
your
like,
when
I
was
engineering
full-time
because
right
now,
I'm
a
developer
advocate.
So
I
ended
here
part-time.
But
when
I
was
engineering
full-time,
I
got
to
the
point
where
I
just
shipped
features
and
then
you
ship
the
same
feature
the
same
way
but
somewhere
else
on
the
app
say
become.
A
B
Expert,
so
I
would
get
my
job
done
in
like
two
or
three
hours
you
know
in
the
day
and
then
like
reddit
hacker
news
twitter,
like
I
filled
the
time
up
somewhere
else,
and
so
instead
I
started
transitioning
like
hey.
I'm
gonna
work
on
something
that
to
advance
my
skill
set
on
the
job
and
I
tried
to
get
the
balance
of
like
okay,
I'm
gonna
offload
my
free
time
open
source
contributions
into
my
work
time
and
it's
gonna
justify.
A
A
Today,
today
is
actually
out
of
out
of
the
ordinary,
I
would
say
because,
of
course,
being
juneteenth
our
company,
as
I
mentioned
before,
normal
actually
changed
it,
so
that
today
would
be
a
holiday
for
the
people
that
work
in
the
u.s.
So
normally
I
would
be
normally
how
I
work
on
ngrx
or,
if
I'm
doing
open
source
work.
A
These
days
is,
I
have
to
get
up
pretty
early
anyway,
so
once
we
once
I
get
up
and
you
know
get
everybody
out
of
the
house,
then
I
have
a
little
bit
of
buffer
time
to
where
I'll
check
on
the
project.
You
know
check
on
issues
see
if
anybody's
open
prs.
You
know,
since
I
checked
yesterday
and
check
on
that.
A
So
I
get
a
little
bit
of
time
in
in
the
morning
and
then
maybe
throughout
the
day,
I'll
just
kind
of
glance
at
the
project
see
because
of
course
I
can't
turn
my
notifications
off
because
well
I
guess
I
could,
but
then
they
would.
I
don't
want
them
to
pile
up.
So
so
I
still
get
emails
from
you
know,
github
when
people
file
issues
and
things
so
I
may
not
respond
to
them
immediately,
which
is
like
I
said
something
I'm
better
about
doing
now,
as
opposed
to
before
when
I
would
like.
A
Oh,
I
gotta
answer
this
now
or
they
they're
gonna,
think
the
project's
dying
but
yeah
that
so
it's
a
little
like
it's
more
sprinkled
throughout
the
day
like
if
I
get
a
take
a
break
during
lunch.
I
may
check
on
if
I
have
some
time
I'll
check
on
it,
then
or
if
I
have
some
time
to
work
on
something
really
quickly
I'll,
try
to
just
hammer
that
out
and
then
then,
of
course,
that's
like
I'm
still
going
through
the
work
day.
So
I
don't.
A
I
don't
take
anything
significant
during
the
work
day
as
far
as
working
on
it,
because
it's
still
a
it's
still
a.
I
guess.
You
call
it
a
traditional
open
source
project
where
we
don't
we
don't
it's
all
contributors
and
none
of
us
technically
get
paid
to
work
on
the
project
yeah
itself.
So
so
I
go
through.
I
still
go
through
my
normal
work
day.
Then
you
get
off,
get
off
the
normal
work
day.
Take
care
of
family
make
sure
we
get
through.
A
You
know,
dinner
and
all
the
normal
stuff
and
then,
after
the
end
of
the
day,
is
over
then,
if
I'm
not,
if
my
brain
isn't
fried
by
then
then
I'll
try
to
write
some
more
code
or
if
I
can
crank
out
some
documentation
or
something
like
that,
then
I'll
work
on
it.
That
way.
So
it's
still,
I
said
it's
still
a
balance
of
and
then
of
course
weekends.
You
know,
may
fridays
I'll
maybe
stay
up
a
little
later
to
work
on
it
or
sometime
on
saturday.
A
B
A
A
B
It's
usually
it's
me
first
and
my
son
wakes
up.
So
that's
when
I'm
sort
of
reading
through
stuff
answering
stuff
and
like
sort
of
naturally
transitioning
into
the
day,
and
then
I
tend
to
I
tend
to
write
code
in
the
afternoon.
So
usually
I'll
get
I'm
done
by
like
three
o'clock
in
the
afternoon.
Her
work
so
I'll
try
to
crank
through
an
hour
of
like
testing
or
try
to
like
prototype
a
solution
and
sort
of
like
hack.
B
And
then,
when
I
do
have
the
focus
time,
which
is
like
sometimes
in
the
middle
of
the
night,
sometimes
in
the
middle
of
the
day,
it
just
depends
on
how
busy
work
is
then
I'll
focus
as
I've
sort
of
like
hacked
away
at
solving
problems,
I'll
focus
and
get
it
done.
But
you
mentioned
something
about
email
notifications.
Are
you
exclusively
using
email
notifications
for
interactions
through
github.
A
Now
I
actually
I've
started
using
the
the
as
soon
as
the
github
app
came
out.
I
basically
downloaded
it
like
this
is
going
to
replace
my.
This
is
going
to
replace
my
emails
that
I
get
from
people
posting
issues
or
pull
requests
and
things.
So
I
use
more
of
the
github
app
now
than
I
use
email
traditionally,
because
I
would
just
open
the
email
and
click
the
link
to
go
to
the
mobile
website,
but
yeah.
B
B
One
of
the
we
have
two
maintainers
on
the
project,
so
I'm
like
I'm
half
of
the
decisions
that
are
made
or
half
of
that
gets
to
wait
to
basically
say
we're
doing
it.
So
I
like
to
have
let
people
sort
of
like
plead
their
case
or
grab
an
issue,
and
then
I
will
jump
in
and
be
like.
Okay.
Well,
thanks
for
grabbing
this
issue,
here's
a
solution
or
put
the
solution
there,
because
I
know
I
don't
have
bandwidth
to
sort
of
do
everything.
A
Yeah,
definitely
that's,
as
I
would
say,
that's
more
of
my
role
these
days
earlier
in
the
project.
We
did
a
lot
more
hands-on
coding
and,
like
I
said,
working
on
the
weekends
trying
to
the
put
additional
projects
in
the
platform
or
fix
bugs,
or
things
like
that.
But
these
days
I'm
more
of
working
to
unblock
people
who
are
trying
to
contribute
because.
B
A
Yeah
yeah,
we
I
I
am
on
the
twitter-
grind
getting
people
to
contribute
to
the
project
but
yeah
those
top
at
least
the
top
four
people.
There
are
core
court
court
members
of
the
team,
yeah
core
team
and
wes
another
one
of
my
counterparts
at
narwhal.
He
works
he's
on
the
project
too,
and
there
there's
other
people
on
the
team
also
that
contribute
more
in
ideas
more
than
code.
A
So
yeah,
that's
why
I
say:
I'm
the
you
know
the
primary
maintainer
of
the
project,
because
I'm
the
one
who's
cutting
releases
and
you
know
having
to
still
like,
nurture
the
project
along
to,
but
I'm
not
I
don't.
That
doesn't
mean
that
I
I've
given
up
the
handle
that
I
don't
have
to
build
everything
or
trying
to
build
everything
myself.
B
Excellent
yeah,
that's
I
dream
dream
of
days
where
I
can.
I
can
start
dictating
and
handing
stuff
to
people
and
like
watching
stuff
grow
without
me
needing
to
touch
everything
and
write
every
test
so
that
that's
that's
a
dream
I
have,
but
I'm
curious.
Can
you
talk
more
about
that?
Twitter
grind
like?
What
do
you
mean
by?
Are
you
actually
out
there
like
saying
hey,
I
got
a
contribution.
A
So
some
of
the
things
that
I
try
to
do
is
if
we
have
like
work
to
be
done
like
there's,
always
doc's
work
to
be
done.
There's
always
like
some
of
these
tasks
to
be
done.
So,
instead
of
like
me,
trying
to
say
oh
I'll
just
go
and
do
that
some
of
the
things
I
just
opened
up,
issues
for
and
I'll,
like
specifically
tag
them
with
like
the
first
issue,
so
that
people
can
say
that
well,
they
will
go
and
open
them.
A
A
A
And
I'll-
and
I
put
that
part
in
their
parentheses
after
if
you
say
yes,
because
some
people
say
yeah,
I
would
like
to
contribute,
but
I
don't
know
how
so
we're
trying
to
put
that
out
there
like.
If
you
need
help
submitting
a
pr,
then
we
will
help
you.
You
know,
like
I'm
saying
I
will
spend
some.
We
will
spend
some
time
to
help
you
submit
a
pr
to
this
project,
whether
it
be
for
docs
or
code
or
test
or
whatever.
A
So
that's
like.
I
said
we
try
to
put
that
out
there
up
front
to
help
people
or
to
remove
that
barrier
of
people
saying
well.
I
don't
know
how
to
use
github
or
I
don't
know
how
to
do
this
or
that
on
git.
So
I
don't
know
how
to
use
the
command
line
with
git.
So
it
was
like
that's
fine
you
can
we
can.
There
are
a
couple
of
ways
you
can
contribute
to
the
project
without
actually
having
to
download
the
git
client
and
do
it
that
way.
Nice.
B
B
A
B
A
Yeah,
I
will
say
that
yeah
the
yeah
I
will,
I
will
say
up
front
that
the
just
because
of
ngrx
build
being
built
on
top
of
rxjs
that
there's
a
learning
curve
to
be
had
there
yeah
and
there
are
certain
applications
for
it
where
you
would
use
it,
but
yeah
it.
What
the
targ,
what
you
know
what
we
targeted
like,
I
said
targeting
managing
state,
and
you
know
some
apps
just
you
know,
don't
need
it.
A
But
if
you
get
to
a
certain
point
where
you're
managing
a
lot
of
state
in
different
places,
that's
where
you
get
into
where
why
you
would
start
to
use
ngrx
in
the
in
your
project.
So
that's
always
my
pitch
to
people
of
in
the
at
least
in
the
angular
community,
about
whether
you
should
use
it
or
not,
because
it
help
what
it
what
it
does
is.
It
has
a
focus
and
we
try
to
make
that
the
best
like
focus
or
focus
that
and
making
it
as
best
we
can.
B
A
Our
application
that
we
have
baked
a
lot
of
our
best
practices
in
for
the
project
so
that
you
can,
if
you're
like
new
to
using
ngrx,
you
can
look
at
this
example
app
and
see
how
it
works,
and
you
can
run
this
app
locally.
If
you,
you
know
clone
the
project
and
you
can
also-
or
you
can
run
it
locally,
and
we
do
have
another
place
where
the
where
you
can
see
the
application
running,
I'm
just
trying
to
bring
it
up
here
or
okay.
A
A
B
A
A
Add
it
to
your
collection
and
then,
if
you
go
back
to
my
collection,
you'll
see
the
book
that
you've
added
there,
and
this
is
actually
using
the
google
books
api
yeah
to
list
or
for
the
search
results
and
like
it's
a
it's,
a
minimum,
pretty
minimum
application.
But
it
goes
through
a
lot
of
the
common
use
cases
that
you
would
have
with
building
a
reactive
application,
a
reactive
angular
application
with
ngrx.
B
A
If
I
can
jump
here,
let
me
click
on
it,
so
you
can
see
the
what
the
state
of
the
application
was
at
that
particular
point
in
time
and
jump
back
through
once
the
you
know.
The
books
are
books.
Collections
are
loaded.
You
can
go
through
it
that
way
so
yeah,
like
I
said,
we
have
full
integration
with
the
redux
dev
tools,
and
this
is
more
a
reference
application
that
people
can
use.
B
B
You
explain
the
the
power
of
having
the
time
travel
stuff
like
for,
like
debugging
for
exception.
Handling
like
this
is
something
I
used
a
lot
in
my
previous
employer.
We
had
set
up
the
redux
dev
tools
and
we're
able
to
have
exception,
handling
and
like
for
for
bug
tracking.
But
can
you
explain
that
I
guess
the
the
power
of
that
on
from
your
perspective,.
A
Yeah,
so
with
that,
when
we
use
the
redux
dev
tools
on
other
projects,
it
ke
it
tracks
the
all
these
states
that
happen
if
you're,
if
you're
using
it.
For
you
know
a
lot
of
your
parts,
every
application,
then
you
can
like
say,
track
those
states
and
over
time,
there's
states
that
your
application
was
in
over
time
and
what
we
used.
That
in
a
previous
application,
is
that
we
would
use
that
to
we
used
it
in
a
couple
of
ways
for
like
local
development,
we
would.
A
You
could
expect
to
see
what
you
know
what
the
application
state
of
the
application
was
in
at
that
point
in
time
when,
when
that
error
happened,
and
we
would
use
that
as
a
another
debugging
tool
to
see,
give
you
some
information
about
how
to
fix
that
issue.
So
they
provided
a
lot
of
it.
It
gives
you
more
information
that
you
wouldn't
normally
have
as
you're
building
an
application,
because
normally
your
your
those
things
are
isolated
within
smaller
silos
or
in
case
of
angular
you're.
A
A
A
A
So
the
store
itself
is
a
service
that
lets
you
select
state
and
dispatch
actions,
and
then,
if
we
go
into
the
state
service,
the
part
where
those
things
come
together
is
right
here.
So
we
are
listening
to
like
the
latest
reducer,
which
is
listening
for
state
changes
and
the
actions
that
so
you
have
a
given
piece
of
state
and
a
particular
action
that
happens,
and
we
are
scanning
those
actions
and
those
state
changes
to
produce
new
states.
A
B
A
B
Redux
also,
I
don't
know,
oh
you
have
to
chat
up.
I
didn't
send
a
chat,
but
you
found
your
way
there,
but
I
don't
know
if
everybody
has
the
quite
has
the
context
of
like
the
power
that
we're
sort
of
looking
at
and
sort
of
like
the
evolution
of
state
management.
For
you
know,
front-end
focused
applications,
I'm
curious.
If
angular
are
there
multiple
ways
to
handle
state
and
store
in
angular
or
is
ngrx
like
the
way
people
are
approaching
it?
These
days.
A
Yeah,
so
there
are
multiple
ways
to
manage
state
within
angular.
The
angular
itself
has
you
know,
built
or
has
services
themselves
that
you
can
or
services
that
you
can
build
yourself
that
are,
you
can
use
rxjs
directly
as
a
and
use
those
in
more
of
an
isolated
way
yeah.
So
you
can
just
you
can
take
a
service
and
you
can
expose
some
observables
on
that
service
and
use
that
to
manage
the
state
of
a
particular
feature
or
a
particular
page
within
your
application.
A
So
yeah
angular
has
has
a
mechanism
to
allow
you
to
manage
state
as
opposed
to
using
like
local
storage.
You
could
inject
a
service
and
manage
that
kind
of
in-memory
in
that
way,
but,
like
I
said,
those
are
isolated,
a
smaller,
I
guess
in
a
smaller
sample
of
state
management,
as
opposed
to
something
more
wide
like
redux.
A
A
A
We
call
them
the
sherry
principal,
which
is
a
person
it's
actually
the
person
that
we
named
the
principal,
as
of
is
a
person
who
used
to
work
with
right
that
I
used
to
work
with
and
her
name's
sherry,
so
we
kind
of
modeled
those
after
after
or
so
yeah
there
are
rules
or
things
that
you
would
like.
These
conditions
that
you
know
injuries
make
or
is
a
good
fit
for
your
project.
Yeah
and
the
sherry
principle
is
noted
here.
A
As
far
as
managing
state,
you
have
state
that's
accessed
by
many
components
of
services,
a
state
that
just
persisted
and
hydrated
from
external
storage.
I
think
local
storage
is
a
good
example
of
that
to
where
you
would
you
could
use,
you
could
manage
your
local
storage,
but
as
far
as
hydrating
it
and
bringing
it
back.
A
A
I
said
we
came
up
with
these
this
rule
of
principle,
and
these
are
the
things
that
you
would
consider
as
far
as
using
it,
because
these
things
tend
to
come
up
more
and
more
in
larger
scale,
projects,
larger
scale,
angular
projects,
and
it
helps
you
provide
that
process
and
pattern
to
use
across
teams
where
you
have
this
consistent
way
of
your
building.
These
features
yeah.
A
Can't
use
you
know
service.
The
other
pattern
that
you
would
use
in
angular
is
more
or
less
a
service
with
a
subject
pattern
and
that's
a
good
pattern,
but
in
some
cases
only
get
you
so
far,
and
this
is
kind
of
the
next
step
of
you
have
a
lot
of
state
in
a
lot
of
places
where
you
want
to
use
it.
There.
A
A
A
B
Excellent,
so
I'm
curious
if
we
can
transition
to
the
repo
itself
like
this.
This
open
source
friday
is
all
about
trying
to
have
contributions
and
things
to
work
on.
You
know
on
friday,
a
lot
of
people
if
you're
a
developer
tends
to
be
a
slower
day
like
a
lot
of
people
still
deploy
on
fridays,
but,
like
people
have,
you
know,
slowed.
B
Very
hard
to
pay
attention
to
my
side,
projects
yeah.
So
if
I
deploy
it
on
monday
and
then
I
have
to
take
half
a
day
to
re-fix
the
stuff
I
broke,
so
I
had
the
inverse,
but
mainly
because
it's
it's
open
source
and
it's
not
my
100
priority
but
yeah.
Let's
talk
about
contributing
and
you
had
mentioned
documentation,
I'm
curious.
If
there's
like
a
are
there
any
sort
of
like
big
things
or
big
pushes
that
ngrx
is
having
right
now
that
people
can
see
if
they
want
to
contribute
to.
B
Yeah,
why
don't
we?
You
switch
back
and
I'll
share
my
screen,
sure
excellent,
and
then
that
way
I
can
sort
of
oop.
I
think
this
is
the
one
I
can
help
you
you
can
navigate
me
through
if
I
was
trying
to
contribute
as
well
so
yeah,
I
think
so
far
we
just.
I
think
we
just
looked
at
the
documentation
and
we
got
that
far
so
you
could
either
like
explain
the
project
and
how
it's
sort
of
set
up,
or
we
can
start
talking
about.
B
A
A
B
A
A
B
A
So
we
ended
up
saying
we're
going
to
move
everything
to
a
mono
repo.
It
would
be
easier
for
us
to
manage
that
way
and
instead
of
doing
the
ngrx
ngrx
thing,
we
told
we
were
saying
that
interx
is
a
platform
or
a
framework.
Consider
we're
calling
a
framework
of
libraries,
so
we're
considered
more
of
a
platform
that
could
contain
many
libraries
that
you
can
use
in
your
projects
can.
A
Every
time
we
get
pr
or
prs
when
people
open
prs
and
we
go
through.
You
know
the
process
of
review
and
approving
each
one
of
those
once
the
pr
is
merged,
we're
using
circle
ci
for
that
right
now,
but
circle
ci.
We
have
a
job
set
up.
That
only
looks
at
when
the
master
branch
is
built
or
someone
merged
something
into
the
master
branch
and
we
go
and
build
all
of
our
projects.
And
then
we
publish
them
to
github
repos
for
people
who
want
to
like
the
latest
and
greatest.
A
If
you
want
to
go
and
get
because
we
we're
using
version
or
versioning
because
we're
using
versioning
so
that
we
don't.
Of
course
we
don't
break
people
break
people's
projects,
but
if
you're
like
I
want
to
live
on
the
bleeding
edge,
we
publish
those
those
builds
to
github
repos,
and
then
you
can
add
those
repos
to
your
project
directly.
B
A
A
A
B
B
A
B
So
my
thought
is:
let's
continue.
We
talked
about
the
building,
so
that's
where
we
were
nx
actually
was
talking
about
the
sort
of
building
we
stop
at
nx
and
that's,
what's
actually
the
automation
to
build
those
those
projects.
So
I'm
curious,
could
we
finish
the
thought
on
how
nx
works
and
how
the
automation
is
hitting
like?
Is
that
connected
to
circle
ci
or
where.
B
B
B
A
A
420
yeah
427.,
so
we
use
this
deploy
job
so
that
anytime
anyone
merges
something
into
the
deploy
job
or
deploy.
Job
is
defined
up
higher
in
the
configuration
file,
but
this
only
builds.
This
job
only
runs
when
mergers
are
made
into
the
master
branch
yeah,
and
so
what
that
deploy
job
does
is
we
unarchive
or
we
unarchive
our
cache,
and
we
run
a.
A
A
Ci
job
builds
the
projects
and
then
we
use
those
build
artifacts
to
deploy
them
to
github
repos
and
also
to
deploy
the
latest
version
of
the
documentation
to
next.ngrx.io,
which
people
can
see
like
I
said,
if
you
want
to
see
the
latest
and
greatest
of
what
was
successfully
built
on
that
branch,
then
you
can
use
that.
So
if
we
go
back
one
directory
real
quick
to
the
tasks
file,
let
me
show
how
that
works
and
if
we
scroll
down
there
is
a
job
there
that
yeah
there's.
A
B
A
We
we're
using
a
convention
of
whatever
the
package
name
dash
builds,
so
we
we
get
each
project
and
we
say
this
is
where
you
know
the
build
artifacts
for
those
that
project
is.
This
is
where
we're
going
to
publish
it,
and
then
we
use
the
prepare
and
publish
function
to
do
the
rest
of
the
work
we
can
scroll
down
to
see
where
the
prepare
and
publish
part
of
it
is
so
what
we
do
with
the
prepare
and
publish
is
we
get.
A
You
know
who
the
committer
of
that
pr
was
and
we
create
a
temporary
directory
and
we
copy
those
build
artifacts
into
that
directory
and
we
make
a
commit
and
then
we
push
we
push
well,
we
only
pull
the
latest
commit
from
the
current
bill
repo
and
then
we
take
a
copy
of
the
build
artifacts
and
push
those
push.
The
latest
build
artifacts
to
push
the
latest
build
artifacts
to
that
repo
for
each
one
of
the
for
each
one
of
the
projects.
A
A
So
the
a
lot
of
the
the
most
of
it
is
like
custom
tooling
to
where
we're
looking
at
the
we're
looking
at
the
project.
Each
project
has
a
certain
structure
and
has
a
certain
build
file
in
it.
So
we're
currently
looking
at
that
to
determine
which
projects
need
to
be
built
and
shipped,
but
we're
as
because
we're
going
to
say,
go
back
to
nx
again,
we
can
use
that
more
and
well.
You
have
to
go
back
there
about
the
same.
We
can.
B
A
B
Yeah,
so
it's
a
it
seems
very
similar,
so
I
have
a
project
that
I've
been
working
on.
I
mentioned
this
earlier
in
the
stream
with
iffy,
which
is
called
open
source,
and
I
have
it's
not
as
complicated
as
narwhal
or
nx,
rather
or
even
like
ngrx's
setup,
because
it's
a
much
smaller
project,
but
I'm
actually
doing,
I
don't
think
the
actual
builds,
I'm
syncing
the
issues
between
repos.
B
So
I
have
this
repo,
which
is
it
actually
lives
here
under
open
source
and
then
goals
template.
So
anybody
who
creates
a
new
repo
based
on
this
template
then
also
brings
the
actions
along
for
the
ride
and
then
this
this
action
itself
is
supposed
to,
for
example,
this
one
syncs
this
one's
a
little
simpler.
Actually
because
I'm
using
another
action
that
fork
bacon,
which
basically
it's
meant
to
every
time,
you
fork
a
project.
B
A
B
B
Yeah,
it's
yeah
automatically
and
it's
it's
built
with
actions
and
like
the
fact
that
this
action
can
go
along
for
the
ride.
No
one
has
to
sign
up
for
actions
like
it's
already
built
into
the
the
product.
Now
it
was
beta
before,
but
the
beauty
of
this
is.
I
have
two
different
repos
that
are
now
staying
in
sync
with
each
other
and
they
don't.
A
B
B
A
B
A
B
Excellent
yeah,
but
I
I
I'm
sorry
I
bring
that
up
because
the
the
understand
the
concept
of
this
build
and
the
scripting
I
love
having
like
ideas
of
automation
and
like
if
you
have
one
repo,
that's
doing
one
something.
The
one
way
like.
I
imagine
the
way
you're
doing
well,
nx
exists
because
the
way
that
narwhal
was
doing
it,
probably
they
probably
end
up
sharing
that
to
other
projects
like
ngrx.
B
So
I
think
what
I'm
getting
at
is
there's
a
lot
of
solved
problems
and
I
think
a
lot
of
people
have
approached
solving
it
themselves
and
then
finding
out
that
it's
hard
to
maintain
something
like
this.
When
you
could
just
actually
follow
brandon
and
follow
ndrx
and
see
how
they're
doing
it
and
just.
A
B
A
B
Well,
excellent,
so
I
I
guess
I
wanted
to
transition
us
to
I'm
not
sure
if
I'm
gonna
be
able
to
find
out
how
our
faces
are
gonna
get
back
on
the
screen.
Okay,
that
was
yeah.
I
I
guess
this
is
my
the
limitation
of
me
not
showing
hide
feeding
hide
video
panel
no
anyway.
If
anybody
in
the
chat
knows
how
to
use
zoom,
please
let
me
know,
because
as
soon
as
we.
A
A
Yep
so
because
you
click
on
the
docs
link
there
at
the
top,
so
yeah
on
the
on
the
each
page.
Right
now
has
a
small
pencil.
If
you
see
there
at
the
top
right
corner
of
the
page
and
what
that
does
is,
if
you
actually
want
to
make
a
change
to
this
project
like
yeah,
I
guess
you
have
to
have
a
yeah
work.
A
B
Yeah,
are
there
any
like
clear
areas
that
where
the
documentation
is
lacking
that
maybe
people
can
jump
into
because,
like
I
mentioned,
if
I'm
a
brand
new
like
ngrx
user,
I
might
want
to
start
using
androx
today,
like
I've
got
a
I've
got
a
problem.
I
want
to
solve
I've.
I've
understand
observable
now.
It's
like
I
want
to
basically
or
I
want
to
and
have
time
travel
debugging
as
part
of
my
project
like.
B
A
Accepting
contributions
for
documentation
in
the
issues
also,
like
I
mentioned
before,
have
some
issues
there
that
are
long-standing
issues
for
documentation,
ones
that
I
haven't
broken
up
specifically,
but
you
can
probably
look
for
them
either
under
the
docs
label
or
probably,
if
you
see
docs
labeling
me
as
the
author,
then
you'll
see,
we
do
have
documentation
ones
here
that
are
people
can
use
to
use
these
as
guides
for
like
yeah.
I
have
one
there
doctor
rewrite
guides,
that's
one.
That's
been
a
long,
long
running
one,
and
so
on
this
page,
oh
wow.
A
B
Yeah
excellent
yeah.
I
think
that's
like
a
great
thing
to
think
about,
because
I
think
one
thing
that
I
talk
about
a
lot
is
the
contributing,
md
and
like
actually
actually
turn
my
second
camera
off,
because
I
think
we're
gonna
be
good
to
go.
I
was
worried
that
my
power
was
gonna
shut
off
again,
but
it
seems
to
be
fine
but
yeah.
B
A
B
Out
places
where
you
can
improve
the
documentation
where
you
had
to
sort
of
struggle
through
and
figure
out
like
I
wish
this
was
better
docs.
One
of
my
biggest
gripes
is
like:
whenever
someone
like
uses
something
I
wrote
and
then
they're
like
hey,
this
is
broken
and
I'm
like
well,
could
you
at
least
just
open
an
issue
like
I
don't?
What
do
you
want
me
to
do?
You
want
me
to
like
pair
a
program
with
you
or
you
just
want
me
to
fix
it
turn
it
around.
The
standard
response
is.
B
A
A
B
A
Yeah,
the
yeah,
the
good
first
issue
is
like
you
have
never.
You
may
have
never
contributed
to
anything
before
you
may
not
even
know
like
how
to
and
like
I
said
we
can
walk
help
walk
through
you
help
you
walk
through
that
process
for
a
good
first
issue
and
those
are
specifically
for
first-time
contributors
like
if
someone
says
if
someone
who
comes
along
says
I'll.
A
So
that
one
is
like
a
clear
line
of
where
that
one
is
and
the
accepting
pr's
one
is
you
know
we
could
do
this
one
or
if
the
community
wants
to
pick
it
up,
then
you
know
we'll
they're
saying
this
is
a
thing
that
we
could
have
and
if
you
want
to
help
contribute
to
or
if
you're
like
a
recurring
contributor,
then
we're
saying
that
you
can
come
and
you
know
take
that
one
and
and
add
your
name
to
the
to
either
add
your
name
to
the
list
or
further
your
name
up.
The
ranks.
B
A
B
I
honestly,
I
really
like
that,
because
I've
been
doing
a
lot
of
trying
to
encourage
other
people
to
contribute
to
the
stuff.
I
do
I
write
some
blog
posts
and
say,
like
hey
here's,
where
the
future
of
the
project's
going
like
if
you
want
to
come
along
for
the
ride,
here's
the
steps
to
do
it.
I
created.
A
B
Called
the
triage
team
as
well,
which
is
something
I
took
from
express.js,
where,
if
you
want
to
onboard
onto
a
project,
but
you
don't
really
know
exactly
where
to
start
or
how
to
actually
like
work
with
like
this,
the
scripting
or
the
builds
and
stuff
like
that.
But
you
can
label
issues
like
or
you.
B
Just
debug
like
you
can
actually
just
use,
use
the
the
library
or
the
the
product
or
whatever
it
is,
and
then
just
like,
actually
open
up
issues
and,
like
point
out
edge
cases
of
like
hey,
you
know
I
was
standing
on
one
knee
and
I
had
two
laptops
open.
One
would
have
linux
and
like
stuff
broke,
like
okay
document
that
tell
me
the
versions,
tell
me
exactly
how
that
sort
of
came
to
like
to
being
because
most
of
my
development's
actually
on
the
mac.
I
don't
really
touch
linux.
A
B
A
web
ui
thing
like
I'm
finding
lots
of
css
bugs
and
firefox
that
I
have
to
change
the
way
I
approach
css,
but
that's
good.
It's
good
to
actually
have
that
sort
of
exposure,
but
I
just
don't
constantly
think
about
like
I
have
this
giant
beefy
windows
pc,
I'm
not
even
using
for
the
stream
which
I
should
have.
Apparently
I
would
probably
not.
B
Have
had
it
die
on
me,
but,
like
I
don't
do
enough
windows
stuff
to
be
able
to
do
that,
but
I
get
a
lot
of
contributions
for
people
on
windows
and
linux
and
stuff
like
that.
So
I
don't
have
to
like
have
two
laptops
open
at
the
same
time.
So
I
encourage
all
the
listeners
and
all
the
people
who
watch
this
after
the
fact
like.
Please
like
consider
yourself
like
a
member
of
the
triage
team,
just
by
default
like
if
you're
new
to
the
project,
try
things
out
read
the
documentation.
A
B
If
you
don't
understand,
like
the
words
or
the
verbiage,
like
we
spent
the
earlier
part
of
the
the
chat
talking
about
college
football
like
if
there's
an
analogy
about
college
football
and
you're
like
this
is
missing
me
like
you,
should
let
the
maintainer
know
and
be
like
hey.
Could
you
like
change
this?
So
the
concept
is
actually
understandable
to
me,
like
you
know,
somewhere
else
in
the
us
or
another
country.
So
that's
my
thought.
B
B
A
B
A
A
Linux
container,
so
you
can't
run
like
obs
natively
that
way
yeah.
So
this
was
a
way
that
a
project
I
thought
was
pretty
cool
that
you
could
attempt
to
do
a
twitch
stream
directly
from
your
chromebook.
So
I
tried
it
out
and
it
didn't
work.
It
worked.
Okay,
yeah,
it
did
work,
it
wasn't
great,
but
but
it
was
a
step
in
the
right
direction
for
someone
who
like
lives
inside
of
a
lives
inside
of
that
environment,
who
wants
to
like
try
doing
an
actual
stream
from
there.
A
Yeah,
so
I'm
I
well,
I
love
the
web
and
if
I
could
do
most
of
the
things
that
I
normally
do
on
the
web,
I
would
choose
that
direction
and
a
chromebook
makes
that
pretty
straightforward
and
it
the
other
part
of
it,
is
that
it
gives
me
the
linux
parts
that
I
want
and
the
other
linux
parts
it
tucks
away.
The
linux
part
that
I
don't
want
like
I
don't
want
to
fiddle
with
desktop
settings
and
tweaking
audio
configuration
and
all
that
kind
of
stuff.
B
B
A
Stack
blitzes,
it's
like
it's
become.
They
have
a
different,
a
lot
of
different
projects
here,
but
yes
for
angular
applications,
it's
pretty
much.
How
you
create
your
like
sandbox,
we
use
it
to
yeah,
we
use
it
to
create.
Yes,
like
code
sandbox,
we
use
it
to
create
if
someone
files
an
issue
and
you
we
use
this
to
create
like
reproductions.
A
So
we
have
like
a
can
stack
blitz.
That
already
has
the
ngrx
packages
installed
and
you
can
fork
that
stack
blitz
and
you
know,
then
it
make
it
your
own
using
you
can
fork
it
to
your
they.
You
can
log
in
with
github
and
fork
it
that
way
and
tweak
the
starter,
stack
blitz,
and
then
you
know
submit
that
with
your
issue
to
say
you
know
this
is
the
issue
I'm
seeing
here's
an
actual
reproduction.
That
kind
of
helps
us
out.
A
B
B
B
Use
it,
but
I
would
not
have
actually
ran
into
it
if
it
wasn't
for
me
having
a
call
out
for
for
sponsors,
so
I
highly
recommend
check
the
use.
Shopping,
cart
out.
I
haven't
used
it
myself,
but
I
will
hopefully
soon,
and
I
just
want
to
give
a
call
out
to
the
github
sponsors
as
well.
You
see
I'm
here
actually
should
we
do.
B
Yep,
so
there
you
go,
you've
got
oh,
you
have
20
sponsors,
oh
wait!
No
you're!
Almost
there
yeah,
almost
there
18.
yeah.
Last
time
I
checked
it
was
like
it
was
less,
but
I
don't
remember
what
it
was,
but
yeah
definitely
less.
But
I
see
a
lot
of
familiar
faces
on
here
too,
as
well.
Yeah
you've
got
the
the
ceo
of
github
sponsoring
him.
There.
A
B
Yeah,
well,
I
hope
I
mean
I
hope
it
goes
a
long
way
too
as
well,
because
I
think
there's
like
I
I
have
a
so.
I
have
a
whole
talk
that
I'm
giving
next
in
a
couple
hours
at
june
team
conf,
but
it's
around
like
the
value
of
sponsorship,
because
a
lot
of
people
will
give
you
mentorship,
but
sponsorship.
A
A
B
B
If
I
was
working
on
a
team
like
I
would
be
so
much
further
like
I
I'm
pretty
sure
I
can
figure
it
out
at
this
point,
I
do
a
lot
of
javascript,
but
what
I'm
getting
at
is
like
there's
so
many
other
people
out
there
that
could
use
just
proper
sponsorship,
like
people
actually
coding
up
like
coming
up
a
site
alongside
them
and
actually
giving
them
the
time
of
day
to
like
show
them
like
the
ropes
and
how
to
do
that.
So
I'm
a
big
fan
of
the
github
sponsors
for
using
it
in
that
realm.
B
I
know
we've
used
it
a
lot
for
like
elevating
people
who
already
doing
stuff,
but
there
are
a
lot
of
people
who
are
like
on
the
edge
of
like
yeah
going
to
like
we
just
check
again,
I'm
going
to
bring
up
iffy
because
we
had
a
longer
conversation,
it's
more
recent,
but
he
was
on
the
verge
of
actually
stopping
his
open
source
project
and
then,
oh
really,
and
then
somebody
sponsored
him
and
it
gave
him
like.
Basically
the
interest
like
I'm
not
just
coding
this
for
myself,
like
a
little.
B
Taking
up
my
nights
and
weekends
like
actually
somebody's
gonna
use
this,
so
I
will
put
my
time
into
it
if
someone
uses
this
thing,
but
like
is
this
like
this
weird
awareness
thing
that
if
you
don't
know
about
it,
you're
not
going
to
use
it.
So
how
do
you
get
people
to
use
it?
Do
you
throw
it
up
on
github,
throw
it
up
on
npm
and
then
hope
for
the
best
and
there's
like
a
lot
of
different
opportunities
for
people
to
do
to
get
exposure
around
with
the
work
they
do.
A
Yeah
definitely
like,
like
I
said
I
was,
I
was
doing
the
nights
and
weekends
work.
You
know
before
the
before
the
sponsorship
thing
came
up
and,
like
I
said
it's
not
it's.
It's
never
been
about
the
money
for
me,
but
it's.
I
appreciate
the
you
know
that
people
have
chosen
to
sponsor
me
and
to
continue
those
efforts
along
the
way.
So
hopefully
well
I'm
not
saying
hopefully
I
will.
You
know,
look
out
for
other
people
to
sponsor
also
so
that
we
can
like
say
it
and
pay
it
forward.