►
Description
Here's the resulting MR from this session:
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28223
Near the end, we run into a really weird issue where a textarea is not updating like we expect. After hopping off the call, this was fixed. It looks like there was an accidental insertion where we returned `$nextTick` *and* used `done` which caused some timing issues 🤷♀️
A
D
C
A
A
A
A
A
C
A
A
E
B
B
B
A
We
don't
me
Oh
collapse,
you
chills
spec,
so
to
be
honest,
I
actually
kind
of
like
it
like
this
like
this,
because
I
we
can
move
them
afterwards
and
I
now
have
been
nice
and
contained
right,
sure,
yeah,
I'm,
just
calling
them
move
or
whatever
doesn't
matter
and
I
just
need
to
adjust
the
that's.
Well,
that's
that's.
A
A
E
A
A
A
A
A
F
A
B
A
A
A
C
A
A
A
A
C
B
D
C
A
B
B
Yeah,
so
this
has
oh
I,
don't
you
think?
Oh,
this
is
a
weird
one:
how
persistent?
Even
we
don't
have
an
index
and
export
from
the
helpers',
so
I
think
we
want
to
do
help.
We
need
to
do
e.
Oh
yes,
this
is
like
the
old
JavaScript
always
index.
We
don't
want
to
do
this.
We
want
to
do
what
we
do
for
the
other
amount
component
with
store
thing.
Okay,
what
is
that
we
do
a
search
for
import,
mount
campano,
a
story
you'll
find
it.
You
mean
like
in
here.
A
A
B
A
A
B
B
A
A
B
B
A
B
B
B
A
B
B
B
B
B
A
B
B
A
B
B
B
A
A
B
A
B
A
A
B
A
B
B
D
B
A
A
If
you
have
an
image
diff,
it
tries
to
fetch
an
empty,
so
the
fix
is
actually
to
say
a
is
text
file
and,
to
be
honest,
like
I'm,
pretty
confident
with
that
just
by
looking
at
the
back
end
code
and
so
on
that
this
makes
sense.
To
be
honest,
I
I
don't
like
that.
This
is
at
all
here,
because
we
have
like
an
image
if
overlay,
mm-hmm
I
can't
be
moved
like
all
the
logic
that
has
to
do
with
the
text
file
into
another
component.
C
B
A
A
Cool
discussion
filters
pick
what
is
failing
here,
unremarked
request:
oh
just
free
test,
failing
that's
good
updates
through
the
selected
item:
okay,
okay,
so
apparently
what
they're
trying
to
do
is
is
only
updates
or
updates.
Okay,
so
I
assume
that
this
is
calling
some
stuff
in
the
background
and
we
again
have
no
URLs
right.
Yep
seem.
B
A
B
A
B
A
B
So
it
looks
like
our
notes,
data.
We
are
missing
a
path
variable.
The
way
you
can
have
notes
thing
on
somewhere.
Well,
I,
guess
in
our
notes:
yeah,
oh
well,
no
you're
right.
We
don't
have
no
state.
What's
in
our
discussion,
Mach
does
vary
discussion.
Markup,
that's
data.
Now
it
just
has
an
array
of
notes.
What
is
notes
datum?
That's
a
good
question.
Maybe
maybe
it's
another.
You
know
no,
it's
fate,
oh
gosh,
and
then
there's
a
notable
data
Justin.
You
called
this
out
man.
What
is
this
stuff.
F
A
The
compiled
component
right-
yes,
yes,
pauses,
you
know
to
be
honest,
like
no.
It
creates
the
store
here.
Okay,
just
I've
seen
what
does
the
notes
I've
actually,
so
this
is
by
the
way,
if,
if
I
look
into
this
component
mates-
and
this
component
is
actually
just
setting
the
notes
data
into
the
store,
this
is
like
the
most
hated
pet
on
that
I
have
is
like
hey
I.
Have
a
component
I
give
this
component
all
this
data,
and
then
the
only
thing
that
the
component
is
doing
is
setting
the
data
in
the
store
which
we've.
B
A
B
A
F
E
B
Like
so,
we
need
to
actually
we
can
either
do
a
set
state
and
are
in
our
store
here
and
and
I
would
do
it
in
our
before
each
and
so
I.
One
of
the
reasons
why
guess
we
could
do
it
in
the
mount
here
and
I
see
that
we're
creating
a
store
in
the
mounts?
It's
really
helpful
if
you
create
the
store
outside
of
mounting
the
component,
because
then
the
setup
for
your
tests
become
really
complex,
but
I
see
we're
already
doing
that.
So
it's
not
a
big
deal.
A
A
B
F
B
B
It
doesn't
make
a
life,
I
mean
it
makes
it
makes
things
nice,
but
we
shouldn't.
We
shouldn't,
do
this
boilerplate
for
every
test
we
should
about.
We
do
it
once
for
so.
What
do
we
do
here?
We
do
mock
equals
our
new.
You
have
to
instantiate
the
class,
the
new
Axios
mark
adapter,
but
then
you
actually
pass
your
axial
since
instance
into
it.
So
we
need
to
import
good
work.
It.