►
Description
In this session we talk about webpack bundles, fix emoji popups, and then talk about organizing feature specs.
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/93572
00:00:00 - Question about webpack bundles and MR's that remove dependencies
00:07:40 - Exploring is-this-known slack channel
00:17:40 - Fixing emoji autocomplete with leading space
00:50:45 - Question about rspecs with shared contexts
A
We
are
going
speed,
hello
and
welcome
everybody
29th
of
july
another
week
of
pairing,
a
question
that
I
stumbled
up
on
today
and
I've.
Maybe
I've
even
answered
it
for
myself,
but
it's
still
still
a
funny
observation
as
I
I
suppose.
So
I
was
reviewing
this
merch
request
by
ip
and
it
is
kind
of
trivial
they're
still
super
beneficial,
because
the
only
thing
it
does
is
check
in
our
package,
json
being
like
okay,
there
is
a
dependency
in
there
that
we
are
not
using
anymore.
A
Let's
get
rid
of
this
cleanup
work
so
far,
so
good,
fantastic
stuff.
What
do
we
have
over
here?
Another
cleanup
another
cleanup
entry
for
a
package.json
dependency,
not
needed
anymore,
so
far,
so
good,
perfect
and
some
things
they
get
more
interesting
when
you
have
multiple
of
them
and
similar
merge
requests
kind
of
fall
in
that
perspective,
because
I
was
like
wait
a
second,
we
are
removing
things
from
our
package
json.
What
does
our
package
json
represent?
A
Well,
we'll
kind
of
be
feeding
webpack
this
thing
and
then
we'll
create
a
bundle
if
we're
removing
something
from
this.
What
about?
What
about
our
bundle
size?
And
I
feel
like
what's
kind
of
interesting
is
for
this,
mr,
we
are
getting
at
least
the
the
bot
or
the
tool
which
is
generating.
This
report
is
getting
a
significant
reduction
on
four
entry
points.
B
Sorry
janet,
could
you
just
double
check?
Could
you
double
check
that
one
because
I
think
quite
often
it
may
not
be,
but
quite
often
it
says
that
this
is
a
complete
guess
and
it's
probably
wrong.
Is
that
a
prefix
there
you
go?
We
don't
have
exact
data,
so
we've
used
data
from
this
one,
so
it
might
be
complete
nonsense,
but
I
could
I'm.
A
Point
thanks
for
mentioning
this
haven't
checked
out,
then.
C
C
With
especially
what
the
merge
primal
enterprise
requests
done,.
A
D
That's
really
weird,
like
we
don't
have
any
new
entry
points
with
oh
yeah,
so
I
would-
and
so
I
would
the
way
I
would
reveal
this
kind
of
mr
is
just
looking
for
that
keyword,
that's
being
removed
everywhere,
because
it's
like
here,
aws
sdk,
like
we
may
not
be
using
that
in
the
javascript
code,
but
maybe
we're
actually
including
something
in
our
style
sheet
from
this
package
and
or
maybe
we're
actually
static,
serve
something
from
this.
D
We
have
linters
and
stuff,
for
we
have
linters
for,
like
direct
usage
of
a
package,
needs
to
live
in
package.json
in
the
code,
but
there's
all
sorts
of
indirect
ways
to
use
the
package,
and
so,
whenever
a
package
being
removed,
I
would
just
global
search
on
the
keyword
like
code
mirror
and
see.
Where
do
we
reference
it?
If
we
don't
really
reference
it
anywhere,
then
it's
probably
good
to.
D
A
Them,
okay,
yeah,
it
seems,
like
I
maybe
put
too
too
much
trust
in
our
bundle.
Analyzes
two
as
well,
but
thanks
for
the
clarification.
So
to
summarize
things
seem
odd,
but
and
that's
for
a
good
reason-
and
this
is
more
of
a
very
rough
estimate
than
an
actual
truth.
Because
what
would
you
mention
paul
that
I'm
100
with
you
that
if
we
remove
an
unused
dependency,
webpack
shouldn't
have
any
differences.
A
But
I
would
argue
that
that
might
be
the
case
and
we
still
see
some
weird
kind
of
differences
in
the
in
the
bundle
size.
Analysis.
A
Stupid
cool
and
yeah-
that's
just
something
I
stumbled
on
today.
So
thanks
for
brainstorming
with
me,
what
else
do
we
have.
D
Yeah
we
can,
we
can
jump
to
the
is
this
known
channel.
I
can.
I
can
share
my
screen.
We
can
jump
there.
No
one
thought
about
it
too.
I
said
that
a
package
could
be
a
week.
D
So
that's
a
good,
that's
a
good
thing,
the
only
the
other
ways,
though
we
could
implicitly
use
it,
is
we
sometimes
these
packages
have
more
than
javascript,
and
so
we
could
use
the
css
and
we
need
to
be
aware
of
that
or
we
could
use
other
kind
of
static
assets
that
we're
referencing
somewhere.
So
that's
a
good
question.
Thanks
for
bringing
it
up,
that's
a
really
good
question
I'll
share
my
screen.
Let
me
make
sure
I'm
not.
D
Okay,
so
we're
going
to
dive
into
is
this
now?
That's
the
topic
of
the
day.
Let's
do
it
share
the
screen,
I'm
going
to
share
the
right
screen
all
right:
okay,
oh
yes,
and
while
we
were
talking
about
diving
into
is
a
snow
and
I
snuck
my
issue
in
here,
which
I
was
so
excited
to
do.
Oh,
this
is
being
addressed
already.
C
D
Oh
great,
so
my
issue
was,
and
so
this
is
a
good
reason
why
I
bring
it
up
to
the
business
now,
because
I
would
have
just
created
the
whole
issue
for
it.
But
hey
it's
already
being
worked
out,
but
my
issue
had
to
do
with
when
you're
attaching.
D
It
didn't
attach,
inside
the
table
cell,
it
added
a
new
line
to
attach
the
file
which
is.
D
D
E
D
Kind
of
makes
it
hard
to
build
these
images.
F
D
B
D
B
A
They're
a
little
painful
to
to
set
up
and
reproduce,
and
I'm
afraid
that
is
probably
not
the
easy
thing
that
I
definitely
know
for
sure.
B
D
Yeah,
that's
tough.
This
is
about
deleting.
D
E
A
While
we're
scrolling
through
this,
I
might
have
another
idea
yes
to
to
check,
but
it
it
involves
the
the
at
who
library.
Once
more.
That's.
A
Everybody's
free
to
leave
now
of
everybody,
no,
but
it
it
is
super.
It's
it's
super
similar
to
the
the
key
listener
event
that
we've
been
we've
been
dealing
with.
If
you
would-
and
I
noticed
from
the
top
of
my
head,
if
you
would
press
call
answer
on
an
mr
comment
and
press
colon,
it
would
open
the
emoji
picker
and
the
problem
with
that.
A
It
will
now
give
you
you
might
be
in
a
situation
where
you
want
to
browse
possible
emojis,
but
it
will
give
you
a
limitation
from
about
10
ish.
Oh.
A
Emoji,
and
that
is
quite
annoying
because
you'll
be
like
what
is
this
thing
called
smiley,
slight
smile?
What
what
are
you
referring
to
you
most
likely,
if
you
know
you'll,
be
scrolling
up
all
the
page
to
then
now
check
for
the
list
and
copy
paste
and
go
cry
for
a
couple
of
minutes
afterwards,.
D
B
It
can't
be
as
bad
as
I
use
fingers
crossed
quite
a
lot.
I
think
I've
probably
shared
this
with
you
before.
Unfortunately,
a
lot
of
things
default
when
you
type
finger
to
middle
finger.
F
B
D
All
right,
just
don't
just
put
it
on
me
all
right,
let's
get
gdk
running
and
we
can
figure
that
out.
E
D
A
Yep
paul,
while
you
set
it
up,
maybe
can
we
look
at
a
merge
like
a
random,
mr
and
check
if
we
can
see
the
behavior
and
how
we
would
wish
for
it
to
behave.
D
Yes,
let
me
pause
sharing,
while
I
log
in.
A
If
you
go
down
to
the
comment
section:
okay,
yep
colin,
there
we
go
and
it's
only
one,
two,
three
four
five
yeah
and
that's
unfortunate.
Oh
look.
D
Yeah
splade
is
that's,
that's
my
that's
the
one
that
gets
me.
So
are
you
thinking?
We
want
to
show
more
emojis.
A
I
I
would
say
so
because,
like
I
would
not
necessarily
I
maybe
I
would
not
even
bother
with
these
search
results
like
if
you
would
say
column
m,
then
maybe
that
is
all
right,
but
at
least
for
the
for
the
very
first
beginning
for
the
column.
I
would
expect
it
to
allow
me
to
browse
through
all
the
emojis.
B
D
D
That's
a
harder
problem.
One
of
my
biggest
issues
is,
if
I'm
here
and
I'm
doing
like.
A
A
And
you
know
what
that
is
not,
and
that
is
where
the
issue
is
coming
from,
that
is
not
100
only
100
acceptable
in
yemo.
That
is
only
that
syntax
is
100
acceptable
in
french
as
well,
and
our
french
users
are
not
very
happy
with
that.
Behavior
wait.
French.
A
A
A
Exactly
they,
I
don't
know,
if
that's
for
every
comment
they
do,
but
every
once
in
a
while
they
will
be
doing
a
space
before
the
column,
which
is
absolutely
appropriate.
B
C
D
D
A
D
F
A
Yep,
it
seems
yeah,
that's
that's
quickly.
Like
probably
the
issue
already
has
a
couple
of
those
user
experience
goal
there.
We
go
look
at
that
face.
D
A
D
Right,
let's
figure
that
out,
let
me
open
up.
D
F
D
D
We
know
we
know
this
is
gonna,
be
in
at
hill
land.
We
know
that
that
is
in
our
what
is
it
called
our.
A
D
D
So
wait,
let
me
go
back,
though
do
we
do
we
do
the
same
thing
for
users.
E
D
D
I
wonder:
what's
triggering
it
to
hide
when
we're
like?
Do
a
member
search.
E
E
See
call
backs
matcher
that
is
followed
by.
Oh
I've,
never
seen
that
followed
by.
B
You've
reminded
me
of
something
that
I
tried
to
tackle
a
while
back
and
gave
up
on
that.
Maybe
we'll
look
at
in
the
future
yeah.
Let's.
E
D
Yeah
our
failing
test-
let's,
let's
figure
out
how
to
test
how
these
things
are
tested.
We
have
we
have
these
specs
and
you,
you
created
some
tests
for
this
recently
right.
D
These
are
just
testing
these
are
just
these
are
such.
D
You
did
the
no
events
listener.
One
okay,
yeah
yeah,.
E
D
All
right,
I
happen
to
know
that
we
have
another
set
of
tests
that
could
make
this.
D
A
D
We
have
we
have
front-end
integration
specs,
where
we
like
target
page
test
things
at
integration,
so
not
necessarily
at
the
unit
level
as
tests
of
behavior,
because.
A
D
In
this
environment,
there's
a
readme
about
this,
but
the
backend
is
all
mocked
out
with
certain
specific
routes,
including
like
fetching
all
the
emojis.
So
because
it's
marked
out,
we
can
actually
just
trigger.
D
D
D
It's
really
helpful
right
so,
like
imagine
the
web
id
that
has
so
many
components
going
on
and
we
originally
wrote
like
10
feature
spikes
for
this
and
it
became
the
longest
r
spec
in
the
suite
it
took
like
30
minutes
to
run
the
10
specs.
A
Yeah
we
should
take
this
with
a
grain
of
salt
because
I
know
starting
to
understand
why
paul
doesn't
doesn't
trust
the
pipelines
we're
having.
D
There
you
go
the,
and
so
then
we
try
to
push
these
down
the
pyramid,
so
we're
testing
the
id
whole
ide
bundle
and
it
and
and
what
I
really
love,
is
just
how
readable
these
tests
are.
It's
like
so
we're
going
to
update
the
file
and,
like
that's
all
contained
in
some
logic,
of
what
that
looks
like
we're,
testing
the
whole
page
bundle,
but
we're
still
in
jsdom
blank,
because
we're
still
really
interested
in
performance
and
stuff,
so
yeah,
the
front-end
testing
environment,
it's
pretty
it's
pretty
nice.
D
Definitely
a
little
quirky,
but
you
know
nothing,
nothing
that
us
professional
software
engineers
can't
handle.
D
Cool
all
right.
So
yes,
yes,
yes,
yes,
yes,
space.
A
D
E
D
A
Yeah
yeah
yeah
sweet
and
that's
just
circuit.
That
is
just
the
expected
results
for,
if
you
type
in
circuit,
okay,
yeah.
D
For
circle,
I
think
you
would
really
want
red
circle
like
you'd
want
red
circle
to
be
up
there.
Maybe
yes!
Yes!
Yes!
Yes,
look
at
it!
Look
at
it.
We
got
our
failing
test.
Yes,
it's
gonna
be
so
easy
all
right,
I'm
so
stoked.
B
F
D
B
D
No,
no
you're
good,
so
this
is
this
is
a
look
behind
right.
I
don't
think
that
is
what
we
want
and
look.
This
is
saying
for
anything
that
is
not
a
colon.
We
just
keep
going.
B
B
D
D
C
D
Red
should
return
the
red
circle.
I
want
to
make
sure
we
don't
lose
that
behavior.
E
D
What
what's
the
problem
I
did
already?
Oh,
I
already
broke
this,
I
think.
Did
I
already
break
it?
I
did
that's
good
the
thing
I
added
that
test.
F
D
Square
this
this
that
is
so
weird,
let's
do
a
different
space.
I
think
these
circles-
oh
yeah.
Oh
that's!
Actually,
what
it's
doing
look
at
that.
I
don't
know
what
that
is.
It
looks
like
it's
a
different
language.
It's
gotta
be
like
fortrans
yeah,.
F
Interesting
all
right.
F
A
Yeah,
let
me
let
me
see
if
it
is
in
the
chat,
but
I
hope
it
is
yeah.
It
should
be.
The
very
last
issue
I
put
in
there.
A
Yeah,
that
was
the
one
about
the
the
escape
key
listener.
So
no,
but
it
has
already
the
issue-
has
five
thumbs
up.
So
there
is
an
audience
awesome.
Okay,.
D
Cool
we
got
our
failing
test
so
now.
The
big
thing
I
think
is.
D
D
F
D
F
B
D
B
D
So
the
brackets
is
a
character
set
and
then
every
character
in
there
is
going
to
be
the
set.
But
then
the
mirror
is
saying
not
in
this
set.
But
this
is
why
we
write
tests.
D
D
Okay,
insert
your
regular:
oh
that's
just
a
regular
expression.
So
here's
my
test
string
boom
that
matches.
D
F
D
F
D
D
So
if
I
do
large
red
circle,
yeah,
that's
great,
that
it
doesn't
show
it
up
here.
That's
great!
This
is
all
working.
So
let's,
let's
start,
let's
start
writing
some
french.
B
D
E
D
We
don't
want
it
to
be
empty,
so
that's
what
did
I
change
here
again.
D
Oh,
no,
it's
got
to
be
this
capturing
group
thing
I
think.
Maybe
oh
yes,
I
bet
it
is
that.
F
D
Compared
to
our
last
pairing,
I'm
going
to
do
my
console
log
debugging.
Instead
of
fancy
general
script.
D
So
previously,
this
capturing
group
always
existed.
D
So
it
would
match-
and
this
capturing
group
would
just
be
empty
because
it
was
a
whatever
star
so
and
it
didn't
have
anything
so
be
empty.
Yeah.
B
B
D
Move
the
question
mark
move.
D
When
I
did
that,
regex
can
actually
just
like
skip
it
like
okay
yeah,
so
I
I
do
want
to
do
this,
but
I
think
this.
B
D
That
I
want
to
do
is
I
think
I
want
to
do.
F
D
A
D
Was
the
only
one
that
had
that?
That
was
the
only
one
that
had
that
issue
right.
D
A
It
was
like
if
you
would
start
the
search
string
with
a
space
like
that
was
pretty
useless
before
anyhow,
so
I
don't
like
what
kind
of
emoji
would
you
be
searching
for?
Let's
start
with
space.
E
D
A
Fantastic
fantastic
in
if
anybody
has
more
time
to
spare,
I
actually
came
up
with
a
little
syntax
quill
that
but
like
everybody's
super
free
to
leave.
But
if
anybody
still
wants
to
hang
out,
then
there'll
probably
be
like
disclaimer
speaking
about
ruby,
but
syntax
wise.
You
probably
could
help
me
out.
Let
me
grab
the
screen
because
that
just
came
to
my
mind.
D
B
A
Awesome
we
are
speaking
about
the
aspect
tax
tests
that
I
introduced
that
I
showed
you
last
week.
If
I
remember
correctly-
and
it
is
about
the
let's-
let
me
put
this
up
yeah.
So
that's
how
it
currently
works.
We
are
we
there.
There
are
plenty
of
tests
running
there.
What
we
want
to
make
sure
is
that
we
are
looping
through
it
with
a
false
and
true
flag
volume.
So
so
far
so
good
this
is
working.
The
current
version
is
working
perfectly
fine.
A
One
downside
that
it
has
to
it
is
that
it
reduces
a
ridiculously
large
diff,
which
is
because
you
have
to
indent
everything.
That's
in
there,
so
it's
it's
just
massive
and
a
tip
that
I
got
from
a
reviewer.
Let
me
let
me
see
so
yeah.
A
This
is
all
of
this
nasty
stuff
because
it
basically
doesn't
have
any
changes,
but
it
it
looks
like
it
has,
and
a
tip
I've
got
from
the
backend
maintainer
is
to
use
this
with
a
shared
contacts,
because
that
will
probably
reduce
the
the
diff
quite
big
time.
A
I'm
not
too
familiar
with
how
the
shared
context
work,
but
that
is
something
we
could.
We
could
figure
out
together,
like
I
kind
of
I
kind
of
get
it.
What
I
don't
so
going
by
this
example,
and
I
feel
like
I've
already
pasted
something
in
there
yeah
going
by
this
example,
and
this
is
just
a
dummy
for
for
now,
what
I'm
having
trouble
with
is:
where
is
this
variable
defined
like?
How
would
I
approach
it.
C
B
B
C
A
Okay,
so
just
starting
at
line
nine,
basically
yeah
exactly
okay,
sweet.
So
then
that
would
then
allow
me
to
get
oopsie
just
the
original
context.
So
I
would
be
able
to
delete
this
and
delete
one
of
those
ends
and
put
this
back
one
level
correct
right,
oh
okay,
but
that's
still
like
I'm
now
for
the
context.
I
feel,
like
I've
doubled
this
now,
because
we're
having
a
shared
context
with
a
valid
username
and
password
in
a
context.
F
C
A
To
just
for
your
understanding-
and
the
only
thing
I
did
is,
I
want
to
add
the
before-
do
and
stop
the
features
like
once
with
a
true
and
once
with
a
false
value.
That's
what
I'm
trying
to
do
right
so.
C
D
Do
you
need,
do
you
need
this,
these
contacts
to
be
used
outside
of
this
file?
Is
it
just
with
this
file.
A
A
So
the
way
I
read
this
for
now,
I
would
have
it
for
this
file
only,
but
we
are
having
multiple
files
that
are
affected.
D
C
But
yes,
I
do
remember
what
you're
talking
about
and
I
think
it's
so
you
think
about
the
the
different
axes
of
of
matrix
that
you
have
so
the
with
few
factor
authentication
and
then
with
valid
username
and
password,
and
it's
got
a
lot
of
different
things
under
that
right.
A
Might
sound
weird,
but
that
is
the
case
to
give
you
a
quick
background
on
this.
Dsmr
is
introducing
a
redesign
for
the
for
the
login
page
and
the.
What
we
don't
want
to
do
is
touch
any
of
the
functionalities,
basically
just
a
visual
layer,
but
if
we
would
only
deal
with
the
feature
flag,
toggled
on
then
out,
our
our
specs
would
only
test
for
the
new
version
and
not
for
the
old
anymore,
and
since
it
will
probably
take
us
a
while.
Therefore,
it
would
be
best
to
test
for
both
cases.
C
D
C
So
yeah
yeah,
like
ordinarily,
like
a
feature
flag.
You
it's
like
isolated
one
or
two
specs,
but
in
these
cases,
where
it's
like
multiple
files
and
do
it
in
a
a
less
intrusive
way
like
exactly
like
this,
without
having
to
indent
the
whole
thing,
and
we
when
we
do,
we
like
mixed
it
in
or
something.
D
Yeah,
let
me
let
me
see
if
I
can
find
it
lee
lee
parted
with
this.
Can
I
let
me
let
me
start
by
sharing
all
mr
parts.
Oh
man,
good
thing.
We
made
all
this
traceability
and
stuff.
No,
I
wasn't
gonna
share
my
screen.
I'm
just
gonna
share
this
this
link
and
then
you
can
open
it
up
and
we
got
it.
D
D
C
A
Catch
it
combine
menu
like
okay,
it's
it's,
mr
635,.
A
A
A
Okay,
so
we're
on
the
same
page:
let's
see
how
this
is
implemented.
Shared
examples
combine
menu
of
future
flex.
Examples
before
do
stop
feature
true.
A
Where
would
the
false
one
be
like?
Is
that
because
it
is
false
by
default
deflect?
What
do
you
mean?
The
old
one
because
true
is
is
hard
coded
in
here,
I'm
looking
for
the
so
that
would
be
the
example
for
the
stopped
license
features
when
it's
when
it's.
C
Like
that's,
not
our
flag,
okay,
I
see
unrelated
go
back
to
the
diff.
F
C
C
C
F
D
D
D
Yes,
so
the
intention
with
this
workflow-
and
so
you
may
not
be
in
the
same
workflow,
okay,
we
already
have
all
the
tests
passing,
and
so
what
we
did
is
take
our
main,
rather
than
rather
than
the
shared
example
being
rather
than
the
sorry,
rather
than
the
shared
example.
D
Flagging
the
putting
the
flag
on
and
off
the
core
code
is
the
shared
example
and
then
your
context
around
it
or
the
core
tests
for
the
features.
The
shared
example
and
the
contacts
around
it
are
flag
on
or
flag
off,
so
that
that
it
behaves
like
combined
menu,
feature
flag
examples,
that's
actually
what's
testing
this
operations
link
or
something
like.
So
that's.
Instead
of
calling
that
shared
example,
combined
minion
feature
flag
examples,
maybe
it
should
we
could
have
called
it
shared
examples,
operations
like
stuff
or
whatever.
D
D
Say
that
it's
basically
flagged
that
it's
pending,
and
we
only
do
that
if
you
notice
on
line
33
when
the
feature
flag
is
on,
we
had
no.
When
we
this
was
originally
written,
we
had
no
code
for
it
and
mastered
yet
it
just
basically
broke
the
top
nav,
and
so
that's
when
we
would
actually
flag
it
as
pending.
So
we
have
all
of
our
tests
ready
to
go.
We
could
try
out
what
tests
pass
when
we
do
this
when
we
iteratively
build
out
the
feature,
but
this
enables
you
some
test
driven
development.
D
A
D
The
the
thing
that
you,
the
thing
that
you
will
might
need
is,
I
think,
breaking
off,
and
here
I
think
we
chose
that
32-50.
C
F
A
D
A
D
And
no
is
it
shared
contacts
or
shared
examples?
Are
those
the
same
thing
no.
D
C
Then
you
don't
need
to
when
you
remove
the
feature
flag,
you
just
have
to
change
it
back
to
your
context.
Instead
of
a
shared
context,.
D
F
D
I
don't
think
so.
Does
that
work
with
shared
stuff.
C
B
C
A
Better
understood,
yeah
and
that's
that's
absolutely
fine,
like
the
thing
trying
to
achieve
there
is
to
make
sure
everything
is
covered
with
the
smallest
amount
of
dips,
and
that
is
absolutely
what's
happening
in
there
and.
C
C
A
C
A
I
see
something's
not
quite
right.
It
behaves
like
with
two
factor:
authentication
could
not
find
shared
examples,
maybe
shared
context
like
what
we're
looking
for.
C
A
C
A
Okay:
okay,
sweet
speaking.
A
Yeah
it's
looking
looking
looking
great.
Is
it
acceptable
to
reproduce
this
behavior
in
every
file,
or
would
you
expect
to
to
have
this
shared
across
many
files.
C
I
think
we
had
that
same
discussion
when
paul-
and
I
did
this
in
my
opinion-
the
the
barrier
for
dryness
is
a
lot
lower
in
in
specs,
so
like
this
is
going
to
get
deleted
right.
It's
not
like
this
code
is
going
to
be
here
forever.
This
feature
flag
code
is
going
to
get
deleted
so
just
having
it
at
the
bottom
of
every
file,
I
think
is,
is
easier
to
understand.
What
do
you
think
paul.
F
D
That's
not
a
big
deal,
I
would,
I
would
do
it
if
it
was
like
every
time
we
use
sign
in.
We
have
to
do
this,
it's
like!
No,
let's
find
it.
Let's
find
a
better
way
or.
A
Gotcha:
okay,
interesting
that
some
tests
are
failing
on
me
now,
but.
C
A
F
A
Absolutely
okay:
sweet
thanks!
So
much
for
helping
out
looking
forward
to
to
see
dmr
for
ufx
ball.
D
D
Yeah
I
kind
of
get
the
feeling
chad
likes
the
back
and
pairing
one
more.
I'm
joking
chad,
I'm
giving
you
a
hard
time.
I
mean.