►
Description
In this session we dive into polishing up a contribution to untamper-my-lockfile for Yarn2 support.
00:00 - Discussion about top-level folders
02:55 - Question about where to put "~/flash.js" or "~/alert.js"
07:04 - Question about "template" around "slot" in Vue
13:30 - Pairing on the untamper-my-lockfile MR
16:59 - Paul finally starts sharing his screen
19:42 - Let's TDD!
A
C
Yeah
starting
this
a
little
late,
we
were
talking
about.
How
do
you
know
when
to
put
something
in
a
top
level?
Folder
or
not,
and
ideally
the
folder
structure
will
represent
the
domain
structure
of
your
application
and
you
you
have
clearly
defined
domain
boundaries
and
relationships
between
them.
We
don't
have
that
Advocate
lab
on
the
back
end
or
the
front
end
really,
unfortunately,
but
ideally
where
you
can,
you
should
try
to
have
the
the
folder
structure
represent
what
your
domain
boundaries
are.
C
A
lot
of
conversations
going
on
in
the
back
end
about
how?
How
can
we
do
this
because
our
services
layer
is,
you
know,
kind
of
a
little
bit
of
a
mess
as
is
live
and
models,
but
there's
architectures
for
this
like
hexagonal
architecture
and
stuff?
It's,
like
you
know,
here's
your
domain
core
and
then
around
that
you
have
sort
of
the
utility
port
adapter
stuff
in
and
out
inside
of
that
UI
and
there's
ways
to
approach
this.
C
C
B
B
C
It's
not
I,
don't
know
how
applicable
it
is
to
view
because
it's
all
component
based,
but
on
the
back
end,
my
goal
is
under
the
Live
directory.
I
have
just
pure
cohesive
domain
logic
and
try
to
avoid
putting
any
domain
logic
in
the
services
layer
in
the
view
in
the
controllers,
and
you
can
sort
of
do
that
same
thing
on
the
front
end
as
well.
Although
you
have
less
domain
logic
to
deal
with
it's
more
like
how
do
you
make
a
UI
work,
which
is
very
yeah.
B
A
A
A
B
I
would
now
put
in
view
share
the
view
share.
This
is
a
grab
bag
which
we
wrote.
That's
a
last
resort,
oh
and
yeah
I
would
I
would
not
put
in
a
view
share,
I.
Think
it's
fine
like
this
I
would
put
it
I
I
would
put
it
in
like
in
the
lib.
We
have
a
lib
folder
if
we
wanted
to
put
it
not
in
the
top
level.
B
A
view
shared
is
like
for
was
intended
to
be
view,
components
that
we're
going
to
reuse
all
over
the
place.
That,
for
some
reason,
are
not
in
gitlab
UI
and
there's
a
lot
of
conversations
of
why
these
components
are
in
gitlab,
UI,
there's
a
lot
of
abusing
of
view
shared.
We
have
very,
very
domain
specific
components
that
live
in
there
and
they
really
shouldn't
so
view.
B
B
B
A
A
B
C
B
B
Or
not,
sorry,
I'm,
not
I'm,
not
I'm,
not
entirely
sure
we
do
to
do
a
ref.
We
use
the
attribute
ref.
So
ref
is
a
special
word
and
but
I
don't
know.
If
I
don't
know,
if
Vue
has
a
special
shortcut
for
it,
it's
only
I
say
recently,
but
it's
probably
been
two
years.
It's
only
recently.
We
started
doing
the
hashtag
thing
because
we
used
to
have
to
say
V
buying
slot
or
whatever,
whatever
it
was
I.
B
B
But
looking
at
it
now,
I
think
if
I
was
going
to
leave
a
comment
here
and
this,
depending
on
the
so
definitely
measuring
the
fatigue
of
the
Mr,
depending
on
as
you
already
have
of
like.
Okay,
where
am
I
gonna
leave
comments
or
not
one
thing,
I
would
look
at
here
and
think
about
would
be
like
okay.
Maybe
we
should
call
our
slot,
though
help
like.
Is
it
make
a
lot
of
sense?
B
B
Yeah,
that's
really
interesting,
thanks
for
sharing
that
and
yeah
thanks
for
thanks
for
Patiently
working
on
the
working
on
the
Mr,
because
I
think
the
the
that
mentoring,
stuff
does
go
a
long
way
and
I
know
it
could
feel
like.
Oh
man,
I,
don't
wanna
I
I
do
find.
This
is
an
exponential
investment
when,
when
the
the
comments
and
learning
that
you
shared
ideally
stick
with
the
receiver
and
hopefully
then
perpetuate
as
they
review
code,
is
that
kind
of
stuff
helps
out
a
lot
too
so
I
do
I.
B
Oh
no,
this
is
like
sounds
like
it
was
destined
to
be
yeah.
Well,
I've
got
some
stuff
that
we
can.
We
can
try
to
tackle
in
the
remainder
of
time.
We
can
also
try
to
find
it.
Is
this
known
bug
and
and
just
fix
it
while
we're
on
here?
That's
one
of
my
favorite
things
to
do.
Oh,
what
is
what
do
you
all
vote
for.
B
B
I
need
to
jump
on
this.
Last
time
we
talked
about
this
untamper.
My
log
file
that
I
was
updating
and
I
need
to
create
some
more
tests
around
this
and
get
the
current
Test
passing
and
respond
to
IPS
comments.
So
this
would
be.
This
is
be
really
nice
for
me
to
push
forward
some
because
we
kind
of
need
it.
B
B
B
B
This
is
the
package
that
may
be
referencing
in
our
package
Json
and
then
the
lock
file
has
all
this.
But
the
resolved
goes
to
some
sort
of
malicious
type
of
squatted
package
be
incredibly
difficult
thing
to
catch
from
a
reviewer
perspective.
If
a
malicious
contributor
adds
a
dependency
that
updates
the
lock
file
but
changes
this
little
bit.
So
that's
that's
why
we
have
this
security
package
in
place,
but
it
only
works
for
yarn
V1.
So
not.
B
B
That's
the
slogan:
everyone
can
try
to
contribute.
Oh
man,
that's
that's
intense,
so
this
doesn't
work
for
yarn
V2
for
the
web
ID
package.
We
use
yarn
V2
because
we
are
using
your
own
workspaces
to
have
nice
cohesive
packages,
and
so
we
haven't
been
able
to
turn
this
on
for
that
and
for
that
reason
we
also
don't
allow
merge
requests
at
the
moment.
B
B
A
B
Yarn
two
actually
looks
like
this,
where
the
resolution
is
like
the
name
and
then
we
got
it
at
npm
and
here's
the
version.
So
the
resolution
isn't
this
long,
URL
anymore
and
so
I
have
this
helper
for
parsing.
We
need
to
have
a
function
that
just
parses
the
package
name
out
of
some
of
these
patterns
that
look
like
this
and
so
all
of
there's
a
number
of
different
there's,
a
number
of
different
examples
of
these
kind
of
resolution
things
and
what
IP
observed
was.
B
The
regex
that
we
need
to
just
get
the
name
out
of
it,
because
these
wouldn't
work
with
the
current
implementation
of
it,
because
I
was
just
looking
at
at
npm
or
something
like
that.
I
think,
because
we
were
using
there's
sometimes
sometimes
you
can
have
these
patch
things,
I
guess
I,
don't
know,
but
here's
the
cool
thing
this
whole.
This
whole
file
doesn't
really
care
about
the
right
hand,
side
of
these
kind
of
strings,
and
we
really
just
need
the
left
hand
side,
the
actual
name
of
it.
B
And
so
I
was
trying
what
I
was
trying
to
do
was
touch
as
little
of
the
pre-existing
code
as
possible.
So
this
is
me
just
doing
an
edge
case
that
can
happen
in
yarn,
V2
land
and
then
composing
the
original
functionality,
so
I
didn't
have
to
divert
from
that
too
much,
but
IP
who's.
Maintaining
this
went
ahead
and
suggested.
B
Let's
just
use
this
kind
of
regex
and
call
it
a
day
now
before
I
do
that
I
think
it'd
probably
be
nice
if
I
actually
had
just
some
unit
tests
for
this,
so
maybe
let's
set
up
with
unit
test
so
that
when
I
change
the
implementation
of
it,
we
can
know
if
we
actually
kept
things
the
same
or
not.
Does
that
sound
good.