►
Description
In this session we pair on an issue with modals for a timetracking MR and showing visible forks for the Web IDE button.
00:00 - Question about lifecycle of modals
11:06 - Displaying visible forks with Web IDE button
A
A
But
when
you
then
reopen
it
again,
you
don't
get
the
new
values,
and
this
is
very
expected
Behavior,
because
this
data
stuff
is
only
ever
run
when
the
component
first
gets
created
and
even
though
the
modal
itself
is
going
to
close
and
open
the
component
is
not
getting
destroyed,
it
would
get
destroyed
if
we
had
like
some
sort
of
V
if
ear,
but
we
don't
and
it
kind
of
makes
sense
that
we
don't
so.
Instead,
we
we
might
want
our.
A
A
A
A
I
kind
of
then
like
to,
rather
than
having
all
the
logic
baked
into
a
modal
component,
I
like
having
form
components,
I
put
inside
of
modal
components,
and
so
we
could
have
set
time
estimate
form
and
set
time
estimate
form
modal
in
the
form
I
can
like
create
and
Destroy
based
on
the
visibility
of
the
modal.
So
that
way
we
get
some
initialization.
A
A
A
A
A
C
A
B
B
So
when
Apollo
was
loading,
so
when
you
were
paging,
that
was
the
problem
when
you
were
paging,
the
labels,
weren't
updated
so
yeah,
potentially
I'd
interview.
If,
when
the
Apollo
State
changed
to
loading,
it
would
then
kind
of
toggle
a
re-render,
but
it
wasn't
I,
don't
think
it
was
the
best
solution.
Ultimately,.
A
A
So
if
you
want
to
go
that
route
without
using
the
VF,
but
we
can
talk
about
that-
maybe
asynchronously
specific
about
this
problem,
but
yeah
thanks
thanks
for
catching
this,
because
I
think
a
lot
of
people
will
write
all
of
this,
but
not
realize
what
happens
like
the
second
time.
The
model
opens
like
that's
it's
easy
to
be
like.
Oh,
my
happy
path.
Works
like
this
is
great,
but
we
really
want
to
make
sure
our
components
are
resilient.
A
Yeah
I,
don't
I,
don't
know
I'm
I'm,
now
you're,
bringing
it
up
I'm,
not
sure
if
it's
possible
that
the
underlying
bootstrap
model
just
doesn't
will
tear
down
the
slot.
When
it's
closed,
so
it's
possible,
we
don't
need
a
VF
and
that
in
that
sense,
which
would
be
really
interesting,
I
just
don't
know
actually.
So
let
me
see,
let
me
see
if
I
can
find
any
anything
about
it.
A
A
So
you
won't
need
a
VF,
because
I
think
the
form
will
only
be
initialized
when
the
mode
was
open.
The
big
question
is:
when
you
close
and
then
reopen
it,
does
it
lazy
and
then
memoize
the
rendering
of
it
or
does
it
tear
it
down
when
you
close
it
again
that
I'm
not
entirely
sure
about,
do
you
want
to
test
it
out?
We
could
create
a
little
code,
sandbox
thing
real
fast
and
try
it
out.
C
B
B
B
B
Well,
it
is,
and
it
isn't
Orchid
it
may
it
may
be
possible,
but
I
think
this
is
definitely
where
it
starts
to
get
challenging.
So
we'll
just
give
give
everyone
a
bit
of
a
recap
on
what
the
issue
is.
What
we're
trying
to
solve
the
moment
from
many
screens
I've
jumped
ahead
in
the
problem
here.
There's
the
opportunity
to
to
open
in
the
web
IDE
the
the
current
logic.
If
memory
serves,
is
pretty
much
if
you've
got
right
access
to
to
the
repo,
then
it's
all
good.
B
If
you
haven't,
then
it
will
check
if
you've
got
a
personal
Fork.
If
you
have,
then
it
will
give
you
that
option,
opening
a
forking
web
IDE
and
if
you've
not
got
Fork,
it
will
prompt
you
to
Fork
the
project
into
your
personal
namespace.
Okay
seems
simple
enough:
we've
got
to
make
a
change,
that's
why
we
did
the
back
end
stuff
and.
A
B
A
B
Yeah,
exactly
so,
and
I
I
think
I
was
looking
at
these
components.
I'm,
not
sure
we
moved
this,
didn't
we
or
no
dog
yeah.
We
moved
no,
not
today
confirm
for
Komodo
I'm
sure
we
moved
it.
Oh
yeah
there
we
go
so
yeah.
What
did
I
start
getting
really
I
I
think
it
was
the
fact
that
we're
passing
like
a
hundred
props
to
this.
C
B
Think
this
is
it.
This
is
where
I
started
getting
a
little
bit
so
I
was
like
oh,
my
God,
like
so
needs
to
Fork
I
was
like
right:
okay,
that
we
need
to
change
right,
because
you
don't
need
to
Fork
if
you've
already
got
a
fork
and
the
web
IDE
URL
and
the
edit
you
are,
and-
and
this
is
where
it
started
to.
A
A
B
A
C
C
A
A
A
A
A
B
A
B
A
A
A
B
I
guess,
then,
what
I'm
scared?
What
what
I
I
was
hoping
to
do
is
baby
steps
iterate
and
find
the
first
place
where
we
can
start
to
say
right.
Actually,
you
haven't
got
right
access
to
this
repository.
You
haven't
got
a
personal
Fork
of
this
repository,
but
you
do
have
access
to
one
or
more
force
of
the
repository
right
access,
I
should
say
so
yeah
we
started
and
we
were
making
pretty
good
progress.
You
know
the
confirmed,
Fork
modal.
We
tied
it
into
graphql
to
get
the
list
of
forks
that
they've
got
access
right.
B
B
B
Well,
that's
that's
what
I
was
gonna
say:
I'll,
be
a
bit,
hesitant
and
worried
that,
like
if
we're
changing
this
I
mean,
maybe
it
will
be
good.
Maybe
it
will
do
exactly
what
we
want
it
to
do,
but
I'm
worried
this
could
be
used
for
other
reasons
in
other
places
and
and
US
changing
its
Behavior.
The
way
we're
intending
to
change
it.
It
quite
a
drastic
thing.
A
A
A
B
Then
I
feel
like
that's,
probably
something
that,
should
we
really
be
doing
on
the
on
the
back.
We're
inclined
to
pass
the
the
information
about,
has
right
access
to
this
and
has
right
access
to
one
or
more
Forks,
I'd
almost
pass
from
the
back
end
and
then
I'll.
Let
the
front
end
maybe
make
the
decision
as
to
whether
to
show
modals
and
whatnot.
A
A
B
A
Right,
and
so
this
is
like
that
model
that
you're
gonna
pass
into
the
mustache
template,
or
something
and
so
having,
rather
than
having
complicated
templates.
Let's,
let's
make
our
model
work
for
us
is.
Is
this
my
preferred
way
of
treating
these
things
so
I
would
yeah
I'd
call
this
show
Fork
modal?
We.
A
A
B
A
B
Yeah
yeah
yeah,
it's
yeah
I've,
yet
to
really
put
it
through
its
Paces,
let's
say,
but
I
thought
I
felt
like
obligated
to
switch
it
on
to
cool
yeah,
that's
cool.
You
know
to
yeah,
try
and
try
and
test
it.
Oh
yeah
Okay,
so
we've
just
done
a
bit
of
Tidy
Up
really
so,
where
sorry
I
was
the
only
intent
intending
to
ask
you
for
a
bit
of
moral
support
here,
but
we've
ended
up.
A
B
C
B
B
A
A
B
B
A
B
A
C
A
B
A
B
C
B
A
B
A
B
A
B
A
A
C
A
C
C
A
A
A
A
B
A
The
other
thing
is
the
fork
I'm
pretty
sure
the
forks
default
Branch
can
differ
from
even
the
the
this
one
too.
So
it's
really
like.
If
we
go
to
the
fork,
we
really
want
to
just
get
that
Forks
default
Branch
or
the
web
ID
should
be
able
to
handle
hey
this
Branch
you
just
checked
out,
doesn't
exist.
Would
you
like
to
create
a
new
one
based
on
the
ref
or
something
like
that,
like
we.
C
A
A
B
C
A
B
If
you
have
got
any
or
then
say,
but
you
have
got
right
access
to
these
Forks
and
that
will
show
only
if
you
have
got
some,
but
there
will
always
be
this
well,
no,
we
don't
want
that.
Do
we
want
there
to
always
be
I,
guess
maybe
and
then
there
will
always
be
a
or
you
can
create
yet
another
Fork
of
it,
but
again
I
think
we
want
to
maybe
try
and
change
that
behavior
to
not
because
I
think
it
defaults
and
goes
straight
in
and
creates
your.
A
B
No
I
was
testing.
Yeah
I
was
testing
earlier
on
something
that
I
needed.
Oh
God
and
everything's
timing
out
something
I
needed
to.
There
was
a
Hammel
view
that
somebody
wanted
to
know
how
to
get
to
I.
I
have
no
idea
so
figured
it
out
that
you
had
to
you
had
to
enable
admin
mode,
and
you
had
to
enable
two-factor
authentication-
and
this
was
the
screen.
B
A
B
C
B
A
B
B
B
A
B
B
C
B
C
A
A
A
B
B
A
A
B
A
A
A
B
Yeah
so,
and
that's
what
was
frustrating
is
obviously
I
made
the
back
end
change
to
sort
of
facilitate
this,
the
the
kind
of
visible
Fork
stuff.
After
a
conversation,
we
had
that
that
was
reasonably
straightforward
got
through
in
good
time.
Then
we
started
hacking
on
this
together
in
a
pairing
session.
Again
made
really
good
progress
with
the
modal,
showing
the
visible
forks
and
yeah,
then
I
realized
I
had
a
little
Gap
plug
that
Gap,
but
then
like
this,
has
taken
and
will
take
longer
to
kind
of
I.
B
B
A
A
B
A
Yeah
it's
worth
getting
I
would
It's
Worth,
showing
you
like
some
screenshots
of
what
that
model,
the
states
of
it
like
if
there's
no
modals
I
mean
if
there's
no
Forks,
how
do
we
want
to
show
the
new
Fork
thing
worth
asking
the
ux
question
on
the
draft
and
Mark
to
solidify
some
sort
of
requirement
there,
but
I
think
I.
Think
that
looks
good.
So
if
we
go
back
let's,
let's
go
back
to
the
to
the.
B
A
B
A
B
A
B
B
A
C
B
B
A
A
Well,
yeah
I
I
think
so
we're
referencing
in
a
project
on
line
33
and
elsewhere.
So
I
think
it's
okay.
No,
it's
really.
It
was
really
good.
We
watched
it
with
with
the
kiddos
last
week
and
man.
It
was
like
super
exciting
it
was.
It
was
like
for
generally
for
kids,
but
is
pirate-esque
themes
like
whale
hunting,
Vibes
of
it's
really
fun
movie
for
nice.
B
A
A
B
A
B
B
A
C
A
A
So
collaborate
checks
for,
can
we
push
code,
can
I,
create,
merge,
requests
and
I
have
already
forked
or
if
I
can
push
specifically
that
Branch.
So
the
other
thing
to
keep
in
mind
is
so
just
in
testing
this
there's
the
state
I
think
right
now
we
have
the
desired
state
of
if
I've,
already
forked
and
if
I
haven't
forked
in
all
of
that.
But.
C
A
B
A
A
That
well
I
would
just
try
I
would
try
out
the
path
of
what
happens
when
merge
requests
are
disabled
on
Mr
and
I'm
able
to
read
it.
Do
we
show
them
the
oh
yeah
go
ahead
and
Fork
you
to
make
changes
like
what
did
we
do
previously?
What
are
we
doing
now,
like?
That's,
the
I,
think
it's
just
gonna
take
a
little
bit
of
Investigation.
B
A
B
A
B
Yeah
I
think
like
it
it's
hard
to.
We
shouldn't
guess
too
much,
but
my
expectation
is
that
you'll
have
no
Forks
a
fork
or
a
couple
of
forks
that
you've
got
access
to
like
anything
more
than
that
would
be
an
edge
case,
yeah
and
so
you're
better
off
not
having
to
to
click
in
and
and
yeah
being
able
to
see
everything
yeah.
B
B
B
A
B
To
be
yeah,
I
I
hope
so
even
like,
although
we
may
may
kind
of
come
to
to
regret
it,
but
we
were
starting
to
strip
out
a
number
of
methods
right.
So
that's
always
a
positive
sign
if
you're
saying
well,
we
don't
need
this
anymore.
We
don't
need
this
anymore
and
yeah,
but
yeah
I
can
see
this
being
one
that
will
take
a
little
while
for
us
to
to
work
through
this
sort
of
permutations
and
yeah
yeah
cool
awesome,
Wicked
thanks
your
time
as
always,
Paul.