►
From YouTube: Insomnia Stream 2022 04 12
Description
A weekly stream focused on Insomnia's open source community.
Join us on the #stream channel over on the Insomnia community slack: https://chat.insomnia.rest/
A
C
Hey
guys,
hey
dimitri.
B
Hey
how's,
it
going
mark
welcome
to
the
insomnia
stream,
so
today
we're
gonna
do
something
a
little
different.
First,
I
gotta
tell
you
what
the
insomnia
stream
is.
So
this
is
a
weekly
stream
that
we
do
here
at
kong,
run
by
the
insomnia
team.
We
almost
always
do
things
specifically
focused
on
insomnia,
but
this
is
something
that
is
owned
by
the
insomnia
team
that
we're
going
to
talk
about
today.
That's
sort
of
relevant
to
insomnia,
insomnia
uses
it,
but
there
are
other
things
that
use
it
too.
B
It's
called
http
snippet
and
we're
going
to
spend
probably
most
or
all
of
the
time
today
talking
about
http
snippet
and
it's
good
to
have
mark
here,
because
I'm
going
to
explain
mark
is
new
to
the
team.
Welcome
mark
we've
been
super
excited
to
have
you
join.
Thank
you.
B
I'm
going
to
explain
to
mark,
I
think,
like
what
it
is,
and
that
will
be
good
because
he
hasn't
seen
it
before
so
maybe
it'll
be
a
good
introduction
for
anyone
and
then
there's
a
pr
so
we'll
get
to
this
in
a
second
I
think,
but
there's
a
pr
open
here
and
that
I
I
guess
four
days
ago
and
you
can
see
that
everything
has
changed
for
the
most
part
and
we're
going
to
talk
about
what
this
pr
is.
B
All
you
know
all
about
and
what
it's
doing
and
everything
like
that.
So
first,
I
want
to
start
by.
Let's
pull
up
insomnia
here.
B
I
want
to
talk
about
what
insomnia
uses
http
snippet
for
or
like
why
it's
useful.
So
here's
insomnia
right,
okay,
this
is
actually
sometimes
I
don't
know.
What's
gonna
come
up
when
I,
when
I
pull
up
my
insomnia,
because
it's
like
you
know,
I'm
developing
on
it.
So
sometimes
there's
like
crazy
things
here
with
like
garbled
messages,
so
there's
a
couple
things
that
insomnia
uses
it
for
the
first
is
this
copy
is
curl
command.
So
this
is
a
you
know,
a
thing
that
we
set
up
and
insomnia.
B
B
Hot
close
and
active
views,
okay,
be
a
linux,
user,
okay!
So
right
so
this
is
what
happens.
This
is
what
was
in
my
clipboard.
Then,
did
I
add
some
stuff
yeah,
so
I
added
a
query.
Okay,
see,
I
told
you
there's
crazy,
crazy
things
that
I
add
so
basically
that's
the
first
thing
we
use
http
snippet
to
do
that
functionality
to
generate
the
current
command.
B
B
It's
supposed
to
be
said,
but
you
see
we
have
all
these
other
things
and
we
have
all
these
other
languages.
So
if
you
wanted,
like,
I
don't
know
if
you
want
to
convert
this
to
like
go
or
something,
this
is
like,
go
new
request,
there's
other
things
c,
sharp
rest,
sharp,
so
yeah
basically,
and
we
have
copied
a
clipboard
here.
So
oh
look
at
that
code
gener,
I
didn't
realize
that
was
there
generated
by
http
snippet
and
then
it
links
to
the
repo.
That's
nice.
Oh,
we
have
our
dr
evil
board.
B
Okay,
so
the
yeah-
that's
that's
what
it's
for
so
mark
any
questions
about
that
so
far,
it's
very
clear,
yeah,
okay,
great
so
yeah!
Then
then,
from
there
we
have
the
like
historical
bit,
so
I'm
gonna,
I'm
gonna
jump
now
to
the
pr
so
yeah,
I'm
dimitri.
Okay.
I
already
introduced
myself.
Kong
is
an
owner
of
http
snippets.
So
that's
something
I
think
wasn't
super
clear
in
the
past
and
then
I'm
a
geek
about
our
core
values
at
kong.
B
So
I
mentioned
that
you
can
ignore
me,
but
basically
what
happened
is
this.
This
was
an
unmaintained
project
for
quite
a
while
and
actually
last
week
on
the
stream.
We
had
a
problem
and
with
copy
is
curl-
and
I
forgot
because
I'm
left
forgetful
like
that.
I
forgot
that
copy
scroll
was
powered
by
http
snippet,
and
so
we,
you
know
like
we're,
trying
to
add
some
functionality
to
copy
as
curl
and
we
weren't
able
to
do
it
because
it's
done
via
http
snippet.
B
So
this
happens
to
us
a
lot
and
I'm
not
the
only
person
that
has
had
this
problem.
So
you
know,
although
we
also
have
problems
with
it.
We
also
have
aspirations
for
how
we
can
like
make
it
better
going
forward.
So,
okay,
that's
great.
So
then
there
are
some
considerations.
B
The
first
consideration
is
that,
as
it
stood,
there
were
tons
and
tons
like
600
fixture
tests,
so
the
fixture
tests
are
like
the
input
is
like
the
underlying
data
and
I'll
talk
about
what
that
underlying
data
is
in
a
moment
the
input
is
the
underlying
data
for
the
request
and
the
output
is
the
like
character
code
point
output,
like
the
string.
This
is
considered.
You
could
consider
this
one
string
right,
and
so
we
had
lots
and
lots
of
tests
for
every
single
I'll.
Just
did
a
terminology
here,
an
http
snippet.
B
This
is
called
a
target.
The
thing
on
the
this
this
drop
down
here-
and
this
thing
over
here
is
called
a
client,
so
we're
at
the
c-sharp
target
with
the
rest,
sharp
client.
We
have
hvp
client
client.
Let's
see
there
are
others
http
http,
1.1
client.
So
you
see
how
that
goes.
Yeah
great!
So
that's
the
first
good
thing
and
then
the
second
thing
is-
and
we
don't
talk
about
this-
a
lot
in
programming,
but
I
think
it's
relevant.
The
the
domain
of
the
problems
that
this
package
serves
to
solve
is
finite.
B
There
are
a
limited
number
of
things
that
you
would
ever
want
to
do
with
this
package
or
that
we
would
seem
to
see
that
as
valuable
and
we
can
we
can
do
it
like
we
can.
We
can
feature
complete
this
thing
now.
Always
there
will
be
new
targets
and
new
clients
that
people
will
want
to
add.
That's
fine.
B
I'm
not
actually
super
concerned
about
that,
because
what
this
in
my
mind,
this
project
is
just
a
a
bill,
a
landing
zone
or
it's
like
a
jumping
off
point
for
being
able
to
create
those
you
could
think
of
them
as
plug-ins,
although
they're
not
exactly
that,
but
we
want
to
be
able
to
have
a
really
strong
foundation
so,
okay,
so
then
I
set
out
to
to
modernize
it.
It's
super
duper
old.
So
let's
look
here
when
it
like.
B
Let's
look
at
some
of
the
history
here,
so
you
know
seven
years
ago
a
lot
of
things
were
done
and
then
not
touched.
It's
been.
It
was
touched
once
seven
months
ago,
but
for
the
most
part,
if
you
look
at
the
commits,
there's
like
not
been
like
the
panda
bot,
I
guess
there's
not
been
very
much
actual
work
done
on
this
in
the
last
calendar
year.
So
that's
kind
of
an
issue
and
we're
hoping
to
solve
that
issue.
A
little
more.
You
know
a
little
more
broadly.
B
So
then,
okay,
what
about
this
pr?
So
this
is
gonna,
be
a
major
release.
Pr
there's
some
other
stuff
that
I
didn't
do
in
this
pr
that
I'd
like
to
do
like
github
ci,
some
fixing
with
the
docker
files
having
just
report
line
coverage.
So
that's
like
gonna
come,
I
think
later,
but
right
now.
B
The
key
key
key
thing
is
that
these
fixture
tests
are
the
same
and
that's
very
important,
because
that
gives
us
a
lot
of
assurance
that
the
functionality
hasn't
shifted,
at
least
if
it's
shifted,
it
hasn't
shifted
much.
There
may
be
edge,
I'm
sure
there
might
be
an
edge
case
or
somewhere
some
option
passed
that
wasn't
well
tested
before
that
is
that
is
that
has
changed
it's
possible,
but
we
know
that
the
core
functionality
of
what
it
broadly
does
is
the
same.
B
Then
there's
a
cli
as
well,
we'll
talk
about
the
cli,
probably
last,
and
that
cli
can
be
used
to
just
convert
things
like
on
the
fly
and
that's
what
this
is
a
screenshot
of
is
showing
like
what
the
cli
looks
like
I
made
a
to
do.txt
file
and
we're
going
to
look
at
that
in
a
second
just
to
talk
about
some
of
those
things
before
we
really
dig
in,
and
I
made
a
little,
I
wrote
a
little
note
about
how
to
review
this,
so
I
I
put
like
here's
get
kraken.
B
It
goes
off
the
page.
I
mean
there.
There
are
tons
and
tons
of
commits
and
changes,
and
I
I
did.
I
tried
to
do
things
like
atomic
commit
ish,
but
you
know
it
doesn't
always
it
doesn't
always
work
out
that
way,
so
that
works
for
me,
but
so
much
I
mean
literally
everything
changed.
So
it's
not
really
worth
it
to
go,
commit
my
commitment
just
basically
look
at
it
as
a
fresh
new
repo,
I
invited
some
people
to
take
a
look
at
the
time.
I
wrote
this.
B
It
was
late
on
a
friday
evening
and
there
was
I
could
smell
the
pizza
downstairs.
So
then
I
stopped
typing.
So
this
is
the
first
review.
Any
questions
on
that
stuff
I'll.
Do
a
quick
tour
of
the
code
base,
if
not.
B
Sounds
okay
good
so
far,
so
this
is
the
the
to
do.
Txt
convert
to
github
actions
have
docker
files.
There
was
this
debug
package.
Let's
look
at
that.
Maybe
we
can
look
at
that
today
and
pm.org.
Is
it
okay?
Well,
that's
national
association
of
pastoral
musicians.
B
That's
interesting!
What
is
this.
B
Not
the
mpm,
I
was
looking
for
okay
debug,
the
lightweight
debugging
utility
for
node.js.
Let's
make
this
bigger
cool,
so
this
is
a
yeah
this.
This
is
a
okay.
This
is
something
that
you
can
kind
of.
Like
turn:
okay,
debug.
You
have
debug
lines.
Great
and
http
is
probably
just
an
argument.
B
So
this
is
a
this
returns,
a
default,
a
function
and
then
http
returns
an
argument
and
then
okay
worker,
a
okay,
yeah
worker,
a
I
remember
this
is
like
super
old-fashioned
type
of
way
to
do
things,
but
that's
fine,
so
they're
logging
with
a
they're
logging,
with
b
work
b,
and
then
you
probably
yeah
control
it
with
an
environment
variable.
B
So
this
is
a
thing
that
this
is
something
that
I
took
away
that
it
used
to
have
that
it
doesn't
have
now,
I'm
not
sure
how
useful
it
is,
but
you
know
we
can
go
back
to
it.
That's
that
cli
and
ci
tests
I
moved.
I
did
move
from
yards
to
commander,
okay
cool.
I
have
to
completely
redo
the
readme.
We
won't
do
that
today,
prettier.
This
came
up
in
the
comments
pretty
early
for
js.
B
We'll
talk
about
that
when
we
read
through
the
comment,
add
an
option
to
curl
for
prettifying
for
minifying
json
bodies.
This
is
the
thing
that
I
was
telling
you
about.
We
were
trying
to
do
an
insomnia,
so
node
support.
This
was
in
a
comment,
we'll
talk
about
it.
Then
there
there
were
names
for
some
of
the
targets
and
one
of
them
changed
from
it
used
to
be
1.1,
so
the
client
was
the
client
was
http
and
the
target
was
1.1.
B
I
can
understand
why
that
was
done,
but
I'm
actually
using
I'm
actually
using
the
names
like
I.
I
need
them
to
be
sort
of
similar
to
variable
naming
conventions,
so
they
start
with.
I
can
take
out
like
known
characters
like
periods,
but
I
changed
that
so
it
starts
with
a
h
such
the
character
formatter
strings.
So
this
is
a
big
thing
in
the
code
in
the
past.
B
We'll
look
at
some
abe
comparisons
of
like
what
it
used
to
look
like,
but
they
were
using
these
like
percent
s,
substitutions
that
were
from
like
yonder
year.
This
was
before
this
code
base
was
before
template
strings
were
in
javascript,
and
so
they
were
doing
a
lot
of
string.
Concatenation
string
manipulation.
You
know,
like
templating
stuff,
that
we
just
really
don't
have
to
do
anymore.
B
B
And
you
don't
need
to
do
that
anymore.
You
can
just
you
can
just
put
every
single
statement
on
its
own
line.
There
is
a
it's
not
just
my
opinion.
I
think
about,
like
my
tastes,
about
reasoning
for
changing
this
there's
also,
I
saw
some
bugs
where
I
think
there
were
things
behaviors
that
were
really
confusing
regarding
indentation,
because
actually
the
second
argument
to
all
these
functions
is
an
indentation
and
it's
it
can
get
a
little
complicated.
B
Okay,
the
javascript
target
will
be
ses6
code,
so
I
think
that's
pretty
standard
practice
at
this
point
in
history
that
that
saves
us
from
having
to
polyfill
a
bunch
of
things
and
do
a
bunch
of
magic
to
get
es3
capabilities.
And,
of
course,
if
people
want
es3
capabilities,
they
can
you
know
web
packet
themselves
or
whatever
some
people
do
and
then
http
stipple
is
no
longer
the
default
export.
It's
it's
now
a
named
export.
C
Not
so
far
sounds
like
a
really
clean
explanation
here:
the
code
that
push
yeah
this
yeah,
I'm
just
curious,
like
yeah.
B
Yeah,
let's
do
it
that's
great,
let's
find
a
target
to
compare
so
before
the
targets,
so
I
also
changed
like
where
things
were
organized
so
they're
in
one
place.
But
before
you
go
to
source,
then
targets
then,
like
I
don't
know,
pick
one
that
you'd
like
to
see
or
do
java.
I
don't
know,
let's
do
javascript,
okay,
javascript
and
then
let's
do
like
axios.
Okay.
B
B
B
B
So
here's
here's
what
was
happening
before,
like
basically,
you
had
code
dot,
push
and
then
a
function
call
and
then
no
semicolon
and
then
dot
push
again.
Dot,
push,
dot,
push
dot
push,
and
you
see
here
we
have
code,
dot,
push
dot
blank,
but
over
here
we
have
co,
we
have
push
and
blank.
We
just
call
them,
and
this
is
actually
kind
of
good
because
it
it
mirrors
it.
B
It
pushes
things
like
in
a
top
like
a
top
to
bottom
sort
of
manner,
and
it
forces
you
to
see
like
what
the
code
is
in
line,
but
the
other
side
of
the
coin
is,
I
also
moved
the
arguments
around
so
the
before
there
was
an
optional
for
so
I
don't
believe
in
optional,
like
order
of
arguments.
So
look
at
the
api
before
this
one
has
one.
This
one
has
two
arguments:
it's
so
confusing.
Okay,
this
one
has
two
arguments.
B
As
far
as
I
can
tell,
there's
absolutely
no
reason
to
do
this
like
it
doesn't
make
any
sense
to
me
anyway
like
why
you
need
to
like
why,
wouldn't
you
just
write
catch
function,
you
know
like
why,
wouldn't
you
just
write
it
out
with
regular
characters
or
whatever
right?
So
that's
a
little
strange
and
then
the
other
thing
is.
So
that's
that's
with
just
strings,
but
the
other
thing
is
you
could?
What
do
you
think
this?
Does
I'm
just
going
to
ask
you
mark?
What
do
you
think
this
line
does.
C
Oh
yeah,
I
was
muted,
I
was
muted,
it
looks
like
maybe
it's
it's
doing
something
inside
the
den
block
to
you
know,
console
lock
the
response.
Data.
B
This
is
saying
indent:
this
line
one
level.
Okay,
that's
it's
not
very!
It's
not
very
yeah.
It's
it's!
I
think
it's
not
like
super
obvious,
exactly
what's
happening
there.
Let
me
see
if
I
can
find
the
the
code
builder.
B
This
is
a
good
thing
for
us
to
look
at
actually
yeah,
so
so
before,
let's
make
this
full
screen.
B
B
Okay
anyway?
This
build
mine
function.
Here,
I'm
gonna
make
it
a
little
smaller
called
yeah
build
line.
What
did
I
call
it?
Oh
I
changed
it
to
called.
I
called
it
indent
line.
Okay,
this
this,
this
indent
line
function.
Where
are
we
sorry,
this
indent
line
function
here
does
exactly
the
same
thing
as
this.
B
B
This
was
a
thing
that
was
super
common
back
when
with
javascript
like
like
10
years
ago
or
so,
and
up
up
until,
like
maybe
six
years
ago,
you
would,
you
would
have
like
a
overloaded,
optional
argument
structure
so
that,
if
you
like,
look,
if
you
just
pass
a
string,
it'll
do
one
thing:
if
you
pass
a
number
and
then
a
string,
it'll
do
a
different
thing
and
if
you
pass
a
number
and
then
a
string
and
then
other
strings
it'll
do
a
different
thing.
B
B
We
don't
need
to
do
any
of
that
stuff.
We
have
evolved
all
we.
You
know
as
a
world
we
have
come,
we
have,
we
have
learned
from
our
mistakes.
All
we
need
to
do
is
have
the
string
that
you're
gonna
put
on
and
the
indentation
level,
and
then
we
take
our
indentation
character,
which
was
given
when
we
created
the
code
builder
and
we
repeat
it
that
whatever
number
of
times
defaulted
to
zero
and
then
we
can
carry
the
two
together
and
return
them.
B
That's
all
it
is
it's
very
simple:
unshift
adds
a
line
at
the
beginning,
push
adds
a
line
at
the
end.
Look
I
mean
it's
really
simple.
You
can
there's
a
line
and
then
an
optional
indent,
indentation
level.
B
Let's
get
this
full
screen,
there's
a
line
and
an
option.
That's
the
string
that
you're
going
to
push
and
then
an
optional
indentation
level,
and
we
pass
that
to
the
indent
line
function
that
we
just
did.
And
then
we
code
is
an
array
of
strings
right
and
we
we
just
push
it.
B
I
see
yes
and
blank
pushes
pushes
an
empty
string
and
then
join
calls.
You
know
array.join
on
on
all
the
the
line,
things
on
all
the
line
lines
in
the
array,
seeing
the
join
character
that
we've
holded
to.
B
It
that's
the
whole
code
builder.
It's
really
like
there's
really
not
much
to
it
it's
lines
of
code,
but
before
I
mean
there's
a
lot
of
stuff
that
was
happening
and
there
weren't
classes
before
so
they're
doing
like
you
know,
you
have
to
do
codebuilder.prototype.push
equals
and
all
this
other
stuff,
so
yeah
much
simpler.
B
So
that's
the
first
thing
and
then
the
main
the
main
file
in
this
in
this
project
is
this
one
http
snippet,
I'm
gonna
make
this
a
little
smaller,
but
basically
what
we
do
is
so
I
told
you
I
would
talk
about
what
the
input
is
so
for
http
snippet.
They
use
this
thing
called
the
har
format,
let's
find
it
on
wikipedia.
B
So
the
har
format
is,
is
a
json
format
archive
file
for
logging,
a
web
browser's
interaction
with
a
site
so
commonly
with
the
heart
extension.
So
this
is
a
standardized
like
format.
It
has
a.
It
has
a
spec.
We
can
look
at
the
spec,
it
has
a
you
know:
json
schema.
It
has
typescript
types
that
people
have
made
from
the
spec,
so
it's
pretty
useful
thing
and
pretty
standard.
B
B
In
fact,
do
I
use
entry
anywhere
else
if
I
like,
if
I
rename
this
to,
if
I
just
do
like
entry
f,
are
there
other
errors?
B
Oh
yeah,
yeah,
okay,
okay,
so
because
I
could
have
inlined
this
if
I
didn't
anyway,
this
is
an
entry
array.
So
it's
a
it's
a
har
request
array
here
and
then
we
have
like
version
creator
name.
So
that's
a
way
that
you
can
do
multiple.
You
can
create
a
har
archive
for
multiple
r
requests.
That's
they
could
have
just
used
an
array
json
array,
but
they
created
this
like
log
format
where
you
can
add
a
little
extra
stuff,
a
tiny
bit
of
metadata
on
top.
B
B
So
the
function
one
of
the
utilities
of
the
library
is
to
add
in,
like
we
have
full
url
query,
object:
headers
object,
uri,
object,
cookies,
object
all
headers,
so
these
are
things
that
are
kind
of
appended
to
the
har
request
in
a
bit
of
a
dirty
way,
but
you
know
it
works
for
what
it
is
and
then
like.
Let's
look
at
a
usage.
Okay,
so
here
is
the
axios
client
that
we
were
looking
at
a
second
ago
this.
B
This
has
a
type
and
the
type
requires
that
it
has
some
info
about
it
like
what
the
key
is,
the
title,
the
link,
the
description.
So
this
is
like
metadata
that
http
snippet
uses-
and
you
know
that
shows
up
like
in
various
places
like
that
metadata.
C
B
B
That's
these
things
all
required,
and
then
this
converter
function,
a
converter
function,
is
a
function
that
has
as
a
first
argument
a
request
which
is
a
concatenation
of
it's
like
basically,
the
http
snippet
request
like
it
has
the
request
extras
and
I
had
to
do
some
magic
because
there's
some
stupid
thing
with
the
types
don't
ignore
this
with
post
data,
but
because
there's
like
an
npm
for
har
request,
and
it
has
some
it
does,
they
have
some
way
of
doing
things,
that's
not
very
ergonomic,
so
I
have
to
fix
it,
but
it's
basically
like
the
the
total
source
object
with
all
the
extras
added
in
and
then
the
second
thing
we
have
is
options,
so
it's
possible
to
pass
options
to
these
converters.
B
If
you
want
them
to
do
specific
things,
we
don't
expose
that
functionality
in
insomnia
but
like,
for
example,
with
the
easiest
examples
like
with
curl
right.
These
are
the
long
forms
like
request,
url
header
data,
but
there's
also,
like
I
don't
know
slash.
You
know,
dash
d
instead
of
dash
dash
data.
C
B
If
people
want
there,
you
can
send
options
into
http
snippet
to
be
able
to
get
those
things
to
show
up.
So
then
this
look
at
this
convert
function.
All
it
returns
is
a
string,
no
data
structure,
just
a
string,
so
it's
a
very
simple
function.
It
it
has.
It
takes
this
input
and
it
returns
the
final
output.
So
all
of
the
things
that
you
need
to
do
then
are
for
any
given
target
or
a
client
rather
are
in
here.
So
oh,
this
is
a
target's
file.
B
Okay,
so
this
is
where
we
like
collect
all.
So,
let's
go
back
so
here's
our
convert
function.
The
first
argument,
like
we
said
that's
this
stuff
and
I
just
destructured
it
out-
is
all
the
stuff
that
comes
from
the
http
snippet
when
it
ingests
the
heart.
So
like
is
there
a
test?
I
wonder
if
there's
a
test
for
just
let's,
let's
look
at
the
picture
tests
in
a
minute,
but
so
basically
we
have
all
headers,
you
know
is
whatever
it
is
method.
B
Url.
We
have
these
things
that
come
from
http
snippet.
We
have
some
options,
so
this
one
doesn't
have
any
custom
options,
but
sometimes
there
are
custom
options
and
you
can
pass
that
as
a
generic
to
the
client
and
then
they'll
show
up
here
automatically
and
we
call
code
builder.
So
that's
the
thing
that
we
saw
before
that
allows
us
to
build
up
our
lines.
B
Our
builder
has
blank
push
and
join,
so
we
start
right
off
the
gate:
import
axios
from
axios.
So
now
we're
you
know
now
we're
moving
and
then
we,
you
know
we
start
doing
some
things.
We
start
building
up
some
objects
and
before
long
you
know
we're
pushing
lines
of
code.
So
if
we
see
that
it's
multi-part
form
data,
then
we're
pushing
some
codes
related,
some
code
related
to
form
data
stuff.
B
You
know
if
we
see
you
know
axios
passing
axios
options
and
we
stringify
the
request
options
to
get
those
things
to
pass
in.
You
know
we
do
some
stuff,
this
one's
pretty
simple,
because
we're
just
making
like
a
simple
request
and
the
the
options
are
really
straightforward
and
then
we
find
then
we're
done
and
that's
how
we
get
this.
Let's
go
back
to
javascript
axios
like
that's.
That's
how
we
get
this
thing.
You
know
this
is
that
options
object.
B
We
built
up
my
rams
here
and
then
this
is
the
the
thing
at
the
any
any
thoughts
or
questions
on
on
that.
C
That's
really
cool
and
I
really
like
that
you've
cleaned
up
a
lot
of
things,
just
one
question
more
more,
like
not
a
question,
though
more
like
my
observation.
Is
that
the
you
so
we
we
converted
the
builder
object
into
a
class
that
returns
methods.
B
Like
push
and
blank
and
join
yeah,
okay,
see,
let's
see
cool,
so
the
code
builder
doesn't
really
know
what
it's
building
it.
Just
it's
just
a
fancy
wrapper
around
like
string
concatenation
that,
like
the
reason
to
have
the
I
thought
for
a
second
like,
do
we
even
need
the
code
builder
at
all?
Can
we
just
use
a
string
array
inside
everything?
B
B
So
if
we
pass
two
as
a
as
a
argument
to
push
like,
if
we
passed
two
here
it
would,
it
would
put
like
one
two
three
four:
it
would
put
four
spaces
in
in
front
because
two
times
the
number
of
the
indent
and
that
actually
becomes
important
because
there
are
places
in
the
code
where
we
do
like
we
do
tab
indent,
for
example,
or
we
do
crlf,
let's
do
options
or
we
allow
it
or
we
allow
it
to
be
configurable.
B
C
B
Don't
know
he
said:
okay,
okay
yeah,
I
don't
know
either
so,
but
anyway,
clear
I've
seen
it
before
I've
just
never
really
cared,
but
anyway,
that's
that's
what
that
is,
and
yeah
http
snippet,
like
the
constructor
like
it
does
this
prepare
step
where
it
it
loops
through
everything
and
passes
back
like
the
full
object
that
you
need,
that
has
all
the
stuff
and
that's
where
a
lot
of
the
work
is
done
in
this,
like
80
of
the
work
like
the
broad
work
for
this
project
is
in
this
file,
this
http
snippet
file,
which
it's
not
that
long,
but
you
know
there
are
things
in
here
that
need
fixing
and
I
didn't
fix
them.
B
I
tried
really
hard
not
to
fix
any
like
there's
this
one,
where
we
have
like
a
forced,
multi-part
boundary
that
it
has
like
a
it's.
It's
it's
forced
to
this
specific
string,
which
is
an
easter
egg
that
somebody
I
added
this
part.
This
is
binary
for
api.
B
I
mean
that's
cute
and
everything,
but
it
actually.
There
are
use
cases
where
you
need
to
allow
the
the
input
to
set
the
boundary
and
it
doesn't
work
with
http
snippet.
If
you
do
that
and
that's
kind
of
an
issue
so
well
whatever
one
way
or
the
other
yeah,
that's
it.
So
I
wanted
to
spend
half
an
hour
and
we
just
just
hit
it
talking
about
the
architecture
there's
a
little
more
to
it,
but
that's
basically
it
I
mean
I
want
to
give
you
an
overview
here
of
how
things
are
organized.
B
Actually
there
is
one
more
thing
we
just
have
to
talk
about,
which
is
how
the
fixture
tests
work.
So
this
is
the
project.
Let
me
make
this
like
really
big.
This
is
the
the
project
structure
on
the
left
here,
so
we
have
source
and
then
inside
of
sources
helpers
which
are
like
util
functions
and
things
specific
to
this
library.
B
We
have
fixtures
which
this
contains
this
fixtures
slash
requests
contains
par
format,
fixed
requests,
so
we
can
see
here,
like
here's
one,
that's
called
full
and
this
gets
used
in
a
lot
of
tests
and
it
has
like
a
query
string
which
are
these
key
value
pair
thingies.
It
has
some
headers,
which
are
also
like
name
value
pair
things,
cookies,
same
sort
of
format,
notice,
trend,
params
inside
of
post
data,
and
then
you
know
so
it
has
some
stuff.
It
has
a
url.
The
url
has
a
certain
format.
It
contains
the
protocol.
B
You
know
all
that
kind
of
thing
has
an
http
version.
So
then
we
have
you
know.
I
have
some
tests
for
custom
targets,
there's
more
http
requests,
custom
fixtures,
so
there's
two
files.
I
need
to
show
you.
The
first
is:
where
is
it
it's
called
fixtures
and
targets?
I
think
that
test.
B
Really,
oh
sorry,
targets
targets.test.ts.
This
is
a
super
important
file
in
this
in
this
in
this
in
this
project.
So,
basically
what
it
does
is
it
sets
up
a
it
sets
up
like
a
general
ability
of
any
particular
target
to
create
fixtures
against
those
base.
Fixtures
that
I
showed
you
before.
We
were
looking
at
that
one
fold.json,
so
there's
a
list
in
there.
Let's
look
at
this
of
like
oh,
how
many
does
it
do?
I
get
a
count
somewhere
how
many
files
this
is
whatever
this
is.
B
20
files,
15
files
in
every
single
client
there
are
there,
are
fixtures
matching
all
of
those
ones.
So
we
see
we
have
fold.swift.
Full.Swift
is
what
happens
when
you
take
full.json's
har
format
and
pass
it
through
the
swift
formatter
for
nsurl
session
client
right,
and
this
is
generated
automatically.
B
There's
no
code
like
I'll
get
to
the
client
test
for
for
that
client,
but
those
tests
are
generated
and
checked
automatically,
and
so
that's
what
this
does.
This
is
looking
at
all
available,
so
there's
a
function
for
listing
all
available
targets,
so
we
have
that
then
we
filter
them
based
on
so
there's
these
filter
lines
throughout
here
and
basically
what
it
is.
Is
it's
filtering.
B
It's
just
a
convenience
thing
if
you
want
to
just
look
at
node
fixtures
or
you
want
to
just
look
at
unirest
or
axios
or
whatever,
or
if
you
want
to
look
at
a
particular
fixture
test
which,
like
there's
one
called
multi-part
file,
for
example,
you
can
comment
these
lines
and
add
what
you
want.
It
will
only
generate
tests
for
those
things
while
you're
debugging,
but
you
know,
for
the
most
part,
they'll
usually
be
commented
out.
B
It's
there
just
to
help
people.
So
that's
what
these
filter
lines
are
for.
So
we
can
sort
of
delete.
We
can
sort
of
forget
about
these,
then
we're
for
eaching
through
all
the
available
targets,
we're
creating
test
suites
for
each
target
that
we're
creating.
If
we
go
down
here,
we're
creating
client
tests
for
each
client.
B
B
So
we
use
we
call
http's.
Thank
you
wallaby.
We
call
http
snippet
with
new.
We
pass
it
in
the
original
request,
the
har
request,
and
then
from
that
we
get
out
a
convert
function.
The
convert
function
can
convert
any
target
or
client,
but
we
pat,
we
tell
it.
We
want
this
target
and
this
and
this
client
and
then
it
gives
us
a
result
and
then
we
expect
that
result
to
be
equal
strictly
to
the
string
of
the
file
that
we
read
from
disk.
So
this
is
from
these
things.
B
So
three
lines
of
code
is
all
you
need
and
then
you
can
get.
Basically,
you
can
get
the
the
string
that
you
want
to
test
against
and
you
do
the
handling.
I
try
to
make
it
a
little
easier
for
people
and
I
left
a
long
message
for
saying
like
what
happens
if
they're
missing
a
file.
B
That's
basically
that's
basically
the
process.
So
then
you
might
be
asking
okay.
Well,
I'm
sorry,
I'm
going
fast,
I'm
not
really
giving
you
a
chance
to
talk,
but
I
want
to
get
to
the
review.
I
want
to
try
to
get
to
the
review
feedback,
but
maybe
it's
not
bad
to
have
like
a
video
that
is
an
overview
of
what
http
is
it's
good.
Then
you
say:
okay,
what
if
you
want
to
write
so
that's
cool
for
the
pre-built
fixture
tests,
that
every
target
and
every
client
has
to
have
to
have
tests
for?
B
But
what,
if
I
want
to
you
know,
make
something
more
specific,
or
I
have
some
specific
option
that
I
want
to
test.
So
this
has
like
timeout,
isn't
is
a
is
an
option
that
you
can
pass
to
this
client
and
it
does
whatever
it
does.
It
does
something
with
timeout.
B
What
we
do
here
is,
I
have
this
thing
called
run
custom
fixtures-
and
this
is
very
similar.
It's
something
that
generates
tests
in
a
very,
very,
very
similar
fashion,
and
all
you
have
to
do.
Is
you
pass
it
this
structure
here
for
tests
and
you
give
it
a
title,
and
you
say
you
have
an
input.
B
You
can
pass
one
raw
here
or
you
can
just
use
many.
Almost
all
of
these
already
used
some
of
the
other
fixtures,
because
really
what
they're
testing
is?
What
happens
when
you
set
an
option,
then
we
have
the
name
for
the
fixture
file,
so
this
one
is
called
indent
option,
swift,
so
indent
option.
Swift
is
like
there's,
no
indent
option,
dot,
ruby
or
something
or
whatever.
The
extension
is.
This
is
just
specific.
This
fixture
here
is
only
for
swift
and
what
happens
is
this
is
testing
the
output
intended
output
when
we
have
a
different
indentation.
B
So
this
is,
let's
take
a
look
indent
option,
so
this
is
this
is
with
four
indents
and
then,
if
we
look
at
the
one
with
this
is
for
short,
it
looks
like
it's
short,
so
we
can
switch
back
and
back
and
forth
between
short
and
in-depth
in
that
option
and
we'll
see
that
it's
the
same
thing,
it's
just
passing
it's
just
passing
different.
Where
are
we
here?
B
B
So
if
you
want
to
write
a
input
test
like
that,
all
you
really
need
to
do
is
is
is
have
this
run
custom
fixtures.
This
is
the
only
thing
in
this
file
right.
It's
just
this
function.
Call
you
tell
it
the
target.
You
tell
it
the
client
that
you
want
to
test
for
and
then
you
do
this
and
then,
when
just
goes
and
runs
tests,
it's
going
to
do
this
stuff
automatically
passing
in
your
options,
so
there's
no
boiler
plate
to
run,
because
this
is
like
super
duper
common.
B
This
run
custom
fixtures
thing
oops
is
used
a
lot
in
the
project.
There's
a
you
know,
there's
a
couple
places
where
there
are
custom
fixtures.
I
want
to
highlight
that
what
happened
before
to
do
this,
like
was
really
I
mean
I
don't
want
to
get
too
stuck
in
the
past,
but
it's
hard
not
to
it's
hard,
not
to
show
how
bad
this
was.
If
you
wanted
to
write
a
fixture
test,
here's
an
example
of
what
you
would
do
ready
like
here's
one.
B
B
Just
changing
you
know
the
the
actual
thing
here,
the
request
and
changing
some
options
and
then
look
at
this
nastiness.
It's
so
bad.
Replacing
this
is
saying,
replace
all
new
lines
globally,
with
nothing
so
they're
taking
out
new
lines.
And
if
you
look
here,
you
see
that
these
are
really.
These
are
really
long
strings
that
contain
the
the
data.
For
that
particular
question.
B
That's
like
super
super
super
rough
to
work
with.
That's
it's
a
very
bad
user
experience.
In
my
opinion,
I
don't
know
why
I
wish
I
could.
I
would
love
to
know
if
somebody
can
tell
me,
but
I
don't
know
why
it
was
done
this
way
in
the
past,
but
for
for
better
for
worse.
This
is
the
way
this
is
the
way
that
it
was,
and
that's
not
like
that
anymore.
This
thing
is
now
its
own
separate
file.
B
This
this
is
indent
option,
so
this
thing
was
the
same
before
they
effectively
took
all
like,
took
all
new
lines
and
removed
them.
So
it
looked
like
like
this
okay,
so
that's
that
okay,
any
questions
about
like
overall
architecture,
how
you
so
everything
is
co-located
is
the
point
I
was
just
trying
to
make
there.
So
if
you
want
to
do
a
kotlin
client,
all
of
your
custom
fixtures
and
all
this,
the
out-of-the-box
fixtures
are
in
the
same
place.
The
tests
are
in
the
same
place.
B
C
It's
really
cool,
I
guess
you
revamped
revamped
or
this
project
with
some
new
new
patterns
and
new
ideas.
That's
really
cool,
it's
my
first
time
to
be
on
the
stream
like
in
my
life,
so
a
little
bit
careful
and
also
I'll,
be
more
listening
this
time
than
talking
my
first
time
so
yeah.
B
B
So
there
was
a
review
left
here,
I'm
gonna!
I
want
to
talk
about
some
of
these
reviews.
Some
review
feedback,
okay,
so
the
first
one
here
is
for
what
it's
worth.
We
looked
at
the
at
read
me:
what
is
this.
B
Maybe
does
it
say
if
it
doesn't
read
me
yeah,
okay,
so
he's
saying
at
my
at
my
place
of
employment,
we
looked
into
this
at
the
cost
of
including
prettier
in
bundles
is
too
high.
It's
prohibitively
expensive.
Okay,
that
makes
sense.
So
what
I
was
saying
was
what
I
would
love
to
do
is
I
would
love
to
use
prettier
for
formatting
the
outputs
and
then
testing
against
that,
so
that
we
can
make
sure
that
the
outputs
that
we're
generating
match
standard
like
prettier
formatting,
I
kind
of
hate
prettier.
B
By
the
way
I
have
never
appreciated
pre
prettier
the
ways
others
seem
to
appreciate
it,
but
I
know,
but
that's
not
what
being
a
team
player
is
all
about?
This
project
does
use
prettier.
B
I
set
it
up
begrudgingly,
but
you
know
it
is
what
it
is
and
people
are
used
to
it,
and
this
is
it's
not
the
dimitri
show
here,
so
I'm
not
afraid
of
incorporating
printer,
and
I
would
actually
like
to
use
it
for
this,
because
it's
something
the
nice
thing
about
prettier
for
a
library
like
this
is
that
if
people
have
a
problem
with
how
we
chose
to
do
things,
we
can
say:
well,
it
wasn't
our
choice,
that's
what
prettier
does
go
go
argue
with
them
and
if
you
go
argue
with
prettier,
basically,
nothing
will
ever
happen
because
they're
not
going
to
change
they
do
from
time
to
time.
B
B
Oh
yeah,
maybe
if
nothing
else,
we
can
have
a
dev
dependency
internally
in
our
own
test,
suite
that
we
can
make
sure
that
the
strings
we're
generating
happen
to
match
prettier
formatting,
but
that
we're
not
including
prettier
in
the
bundle
somebody's
somebody
commented
here
on.
Where
would
this
be
from
on?
Oh
on
twitch,
this
looks
to
be
speak,
easy
v5.
This
looks
to
be
an
issue
about
resulting
bundle
size,
though
maybe
yeah
exactly
yep
exactly
he
said
there.
You
go
sorry.
B
If
there's
like
a
delay,
there's
a,
I
think,
like
a
five
or
ten
second
delay.
So
thanks
for
chiming
in
yeah,
I
think
I
think
we're
gonna
probably
do
that
and
then,
as
long
as
the
resulting
output
happens
to
match
what
prettier
would
have
done
anyway,
then
it's
as
if
we
wrote
prettier,
because
this
is
like
you
know-
input
output,
pure
functional
strings,
so
I'll
keep
that
in
mind
in
the
future.
B
B
It
would
never
yeah
it
would
just
be
in
the
test
side
of
the
code
base,
but
never
anywhere
else.
Okay,
great!
What's
the
reasoning
for
supporting
node
14.?
This
was
a
mistake.
I
think
I,
the
reasoning
is
I'm
like
I'm
liking
a
like
update
your
evangelist,
and
I
sometimes
get
I
get
pushy
about
that
and
that
this
leaked
out.
So
this
is
this
needs
to
be
fixed
this.
This
is
it's
not
appropriate
for
this
to
be
less
than
14.
Well,
we
can
meet
in
the
middle
node
lts.
B
What
is
the
re?
What
is
the
current
lts
like
6.,
14.,
14.19?
Okay,
so
we're
going
to
say,
like
14.19,
current
lts
14,
you
know
like
not
well
known
fact
but
like
14.2
is
not
supported.
There
are
cves
in
14.2,
so
we're
not
going
to
support
that,
but
major
like
everyone
can
stay
within
the
like
recent
major
version.
It's
I
like
pushing
people.
B
When
I
make
libraries,
I
always
try
to
nudge
people
a
little
bit
because
it's,
I
think,
it's
helpful
if
we
stay
abreast
of
things
changing
in
the
world,
but
you
know
yeah.
I
need
to
like
study
this
board,
so
I
know
exactly.
I
know
exactly
that.
Evil
laugh
where
is
that
one,
dr
evil?
Okay,
so
very
nice,
yep.
B
So
I
need
to
I
need
to
remember
to
change
that
because
it's
I'm
so
I'm
not
going
to
resolve
this
because
that
that
does
need
to
that
does
need
to
change.
I
think
I
put
it
in
like
16
yeah,
I
put
it
in
the
package
json.
I'm
not
gonna.
Do
that
right
this
moment
on
the
stream.
I
don't
think
I
don't
think
this
fixture
is
used
anywhere.
Oh
interesting,
rest
method,
fixtures,
rest
method,
echo,
oh,
where
did
this
come
from
then?
B
Well,
let's
take
a
look.
Let's
take
a
look
targets,
it
would
be
in
oh
yeah
right.
I
was
in
the
right
spot
test
targets.
Express
method
is
power.
Shell.
B
Maybe
I
forgot
something:
it's
nothing
it's
nowhere.
So
where
did
it
get
added?
Okay?
So
then
we
have
to
go
to
a
completely
separate
place.
Fixtures
is
it
requests
or
output?
I
can
never
ever
remember.
I
think
it's
output,
yeah
powershell
quest
method,
echo.
C
B
That's
pretty
spooky,
oh,
you
know
what
I
know
what
this
is.
I'm
not
even
gonna
comment,
I'm
just
a
dingus
I
was
trying
to
like
echo
some.
I
was
doing
some
subscript
thing,
okay,
so
the
one
thing
that
was
really
tough
about
these
fixtures
is
that
prettier
came
like
busted
through
or
actually
get.
Git
has
a
functionality
in
it
for
windows,
compatibility
where
it
will
take
all
crlf,
clear,
clear,
like
windows,
line,
formatting
and
endings,
and
change
them
to
lf.
B
B
Add
cursor
line
ends
no
line
and
I
must
have
removed
it.
I
had
an
extension
that
I
used
the
issue
with
that
is,
and
this
is
a
first
in
my
career,
it's
very
rare
that
you
actually
need
to
have
both
I've
never
seen
a
situation
where
you
need
to
have
both
crlf
and
lf,
but
actually
these
fixtures
contain
those
examples
for
eight
raw
http,
because
for
compatibility
reasons
and
yada
yada
yada
in
the
past.
B
It's
all
20
years
ago,
30
years
ago,
whatever
http
spec
specifies
that
crlf
are
used
to
separate
lines
of
the
headers
and
then
an
extra
crlf
here
to
before
the
body,
and
then
the
body
contains
can
contain
lf,
but
it
can
also
contain
escaped
crlfs
and
other
things.
B
That
means
that
this
file
like
watch
this.
If
I
save
this
file
right
now,
if
I
make
a
change
or
like
let's,
let's
just
make
a
change,
and
then
I
save
it
probably
gonna
show
up
here.
No,
it's
not
gonna
show
up
here
what
okay
application
json!
B
Oh,
oh,
I'm
sorry
because
I
exempted
these
files
out
later.
Okay,
so
I
did
something
in
the
git
ignore
that,
let's,
let's
get
this
stuff
away
from
here,
get
attributes,
so
I
created
a
special
rule
for
these
fixtures
that
tells
git
to
treat
them
as
text,
which
means
it
won't
munch
like
they
won't
play
around
with
the
lines.
B
That's
what
that
is
yep
yep!
I
deleted
it
great
catch.
I
would
never
have
caught
that.
So
thank
you,
john
for
catching
that,
okay,
this
one.
If
you
change
this
very
to
javascript,
you
shouldn't
need
to
cast
the
object
as
unknown.
So
the
problem
with
that
is
the
let's
go
here.
B
Custom
target
the
problem
with
that
is
that
the
the
way
that
I
did
these
targets
is
that
it's
a
target
info
is
has
a
key
of
target
id
and
target
id
is
a
key
of
targets
so,
like
literally
it
knows
in
advance
and
from
a
typescript
perspective.
This
is
okay,
because
if
you
use
a
client,
it's
you're,
gonna
you're
gonna
be
forcing
it
anyway,
because
the
client
has
a
cast.
B
This
is
there's
a
I'm
being
vague,
but
there's
an
ad
target
function,
let's
find
it.
Where
is
it
add,
target,
add
client
and
yeah?
The
the
add
target
and
add
fun.
You
know
thing
here
is
gonna
is
gonna
catch
that
so
there's
like
look
at
all
these
all
these
tests
here,
it's
gonna,
it's
gonna
catch,
making
sure
that
it
has
that
it
doesn't
have
a
duplicate.
Also,
is
what
I
think
that
it
wasn't
testing
before.
B
So
I
added
a
couple
things
in
here
like
a
couple
checks,
but
it's
going
to
basically
add
the
new
target
to
the
targets
list
at
runtime.
This
test
is
creating
a
test
like
if
I
did
yeah
it's
true
that
if
I
fix
this
to
javascript,
it
would
solve
the
type
error,
but
actually
the
type
error
is
right
like
what
I
could
do
is.
I
could
write
a
thing
here.
We
could
say
like
js
variant
and
then
yeah
I
mean.
Maybe
I
should
do
this
like.
B
Let's,
let's
do
target
custom
target
equals
string
or
I'm
sorry.
This
is
extends
string.
Actually
we
want
to
do
equals
see.
This
is
gets
weird
because
then
I
don't
want
to.
I
don't
want
to
have
a
situation
where
someone
needs
to
put
it
in
that
they
didn't.
But
let's
just
see
what
this
would
look
like
real,
real,
real,
quick.
It.
B
And
then
oops
I
need
to
put
another
and
then
target
id
and
I
guess
would
be
or
target,
and
this
is
going
to
create
other
errors,
so
this
is
going
to
say,
like
property
does
not
exist
in
target,
I
mean
I
think
I
went
through
this
before
and
I
decided
like.
I
don't
want
there
to
be,
because
this
is
defaulting
to
something
like.
B
I
don't
want
it
to
be
mandatory,
but
I
don't
have
a
default
with
which
to
put
it
in
so
like,
then
that
means
that
anytime
anybody
uses
target
they're
going
to
have
to
specify
that
that
could
be.
Okay,
like
let's
find
out
like
a
real
life
example,
so
like
python
here,
so
that
I
would
need
to
say
like
python,
it's
just
nice
if
it
can
infer
it
and
it
can
infer
it
if
I
do
it
the
way
that
it
was
being
done.
So
that's
the
reason,
but
I'm
open
to
feedback.
B
If
anyone
has
suggestions
on
like
a
way
to
do
this,
that's
nicer,
I
wouldn't
mind
hearing
it.
I
just
don't.
I
don't
know
if
it's
really
going
to
be
a
big
value.
Add
it's
kind
of
a
it's
kind
of
nice
like
makes
it
easier
if
you
can
just
use,
you
know,
as
is
because
this
is
the
this
is
the
line
that
it's
angry
about,
because
it
knows
statically
what
the
targets
are,
because
it
looked
at
this
object
and
it
looked
at
the
keys
of
this
javascript
object
and
said:
hey.
C
B
Is
just
for
the
fixture
yep?
This
is
just
for
a
fixture
test.
This
is
not.
This
is
testing
like
this
is
for
tests
regarding
adding
custom
custom
targets,
okay,
so
I'll
respond
to
that
in
more
deep
depth
later
so,
okay
apis
have
changed
slightly
with
a
new
add
target.
Add
on
the
main
entry
point:
oh
oh
interesting,.
B
A
B
B
B
You
see,
and
the
reality
is,
is
that
this
part
didn't
change,
because
what
changed
was
actually
this
like?
If
you
want
to
make
them
equivalent,
you
could
do
this,
you
could
do
export
star
as
http
snippet
and
then
you
would
have
to
say
http
snippet.http,
snippet
and
then
here
it
would
be
the
same
as
it
was
before.
So
I
I
I
hear
the
feedback
like
I
get.
What
the
point
is,
but
it's
not
I
mean
it's
not
exactly.
This
part
is
not
exactly
different.
B
It's
just
that,
because
this
changed
and
that
and
that
I
did
call
out,
I
mean
I
did
call
out
that
it's
no
longer
a
default
export
like
really
what
we
did
is
we
dropped
this
thing
down
a
level
this
one
down
a
level
as
a
named
export,
and
that
has
the
effect
of
making
it
feel
like
because
it
felt
like
this
was
like
a
method
on
a
class
or
something,
but
I
mean
it
wasn't.
It
was
just
a
function
that
was
exported.
B
It
didn't
have
anything
to
do
with
the
class.
In
fact,
it
was
in
the
same
file
and
I
moved
it
from
that
file
in
the
past.
So
yeah,
there's
there's
that
so,
okay
I'll
I'll
respond
about
that.
Maybe
I'll
just
link
to
this
video,
it's
easier
to
do
that,
so
I'll,
wait
until
the
video's
up
and
that'll.
Do
it
okay,
thoughts
on
renaming
it
to
jessie
it
to
be
more
jesty,
so
this
is
in
custom
fixtures.
We
can't
here's
the
answer.
B
Let
me
show
you
so
the
feedback
is,
and
it's
a
good
one.
Where
is
it,
runs
custom
pictures
hey
in
this
type
here:
what
if
we
rename
this
to
it,
because
then
it's
gonna
be
like
it's
a
nicer
ap.
It
is
a
nicer
api
and
I
wanted
to
do
that,
but
we
we
creates
a
different
problem.
Let's
find
a
thing
that
has
like
a
client:
oh
actually
run
custom.
B
Okay,
so
then,
instead
of
title
we
would
say
it
right.
So
that's
good!
That's
all
good
and
well,
but
then
here
we
would
have
an
issue
that
I
think
would
get
confusing,
or
I
thought
maybe
I'm
wrong.
I
thought
it
would
get
confusing
where
I
would
have
to
say
it
like
title
and
then
and
then
everything
would
work
so
there's
two:
it's
here,
there's
the
it
the
global
and
then
there's
the
it
that
comes
from
this
thing
that
I
have
to
rename
to
title,
and
I
thought
that
that
would
be
confusing.
B
I
don't
know
mark
what
do
you
think,
which
would
you
which
find
it
confusing
too?
Well,
I
mean
you
know
now
that
I'm
looking
at
it.
The
idea
is
that,
like
this
makes
it
really
clear,
this
is
easier
for
the
end
user,
and
this
is
and
the
way
that
I
had
it
before
is
easier
for
the
person
writing
looking
at
this
file.
B
B
Let's,
let's
fix
this,
let's
commit
what
we
have
just
to
just
to
do
it
whipped
I'll.
Come
back
and
rename
these
later
and
then.
B
Hit
it
there
and
then
all
these
got
changed.
They
all
got
changed.
We've
never
run
the
tests.
We're
like
out
of
time.
I
didn't
even
wow.
Look
at
the
time.
Do
we
have
another
meeting
after
this?
This
is
going
time
flies
when
you're
having
fun.
We
do
have
another
meeting
on
the
insomnia
team.
We
have
a
triage
meeting,
okay.
Well,
let's,
let's
wrap
this
up.
So
let's
run
the
tests
just
a
yarn
test.
B
Great
they
all
passed
and
let's,
let's
actually
run
it
verbose,
so
I
can
show
you
kind
of
like
what
different
things
are,
that
it
runs.
There's
all
the
lists
like
more
than
a
thousand
lives.
No,
it's
not
okay!
So
here
we
are.
We
have
the
code
builder
test.
Some
some
helper
function
tests
blah
blah
blah.
Then
we
have
see
these
are
going
through
all
the
custom
fixture
tests,
custom
fixtures.
Four.
B
This
was
happening
before
there's
two
exactly
two
tests
for
one
client
for
this
closure:
http
client
that
we're
missing
in
the
past,
there's
like
a
bug
with
them,
and
I
didn't
fix
that
it
was
exempted
out
in
the
past
as
well.
Then
we
get
into
these.
These
are
the
val.
These
are
like
the
custom,
like
validation
tests
running
all
of
those,
so
everything
works
and
it
renames
yep.
I
think
that's
good
feedback
and
it
makes
it
really
it
should
not.
It
should
not
use
course
yeah.
I
think
it's
better.
B
That
way,
it
does
add
some
weird
shadowing
stuff
in
the
file
but
like
if
it
comes
at
the
expense
of
making
it
easier
for
end
users.
B
B
And
then
that's
gonna
be
where
we're
gonna
have
to
stop
for
today,
I'm
gonna,
I
don't
think
we're
gonna,
probably
look
at
this
again
on
the
stream.
Let's,
let's,
let's
try
to.
B
Here
I
always
like
to
put
the
commit
that
I
that
I
change
something
that
way
people
can
tell
me
if,
like
no,
you
didn't
actually
fix
it
on
speakeasy
v5
on
twitch
set.
I
would
optimize
dev
experience
as
opposed
to
details,
internal
details
too
yep,
upon
being
confronted
with
that
reality.
I
agree.
This
is
great
code
builder,
it's
no
longer
using
the
util
thing.
This
was
actually
not
a
goal
of
mine.
I
don't
didn't
think
about
bundle
size
and
I
don't
frankly
care
about
bundle
size
that
much.
B
I
just
hated
the
complexity
that
it
added
with
those
percent
s
strings,
and
there
was
a
couple
percent
d's
throughout
the
project
too,
which
are
weird,
but
I'm
really
happy.
I'm
super
duper
happy
that
that
module
is
gone
now.
This
is
something
specific
to
form
we're
getting
into
typescript
errors
want
to
move
this
to
the
top
yeah.
Probably
I
don't
know
why
it's!
Oh,
oh!
It's
like
the
sort
order
of
the
things.
B
Yep
probably
should
what's
the
error
here,
a
type
error
on
this
line
is
strange:
yeah,
it's
because
yeah.
I
agree
that
it's
strange
for
whatever
reason,
and
they
really
were
using
this.
The
client
for
http
for
shell
curl
allows
gel
curl
client
test.
It
allows
for
indents
that
are
strings,
and
it
also
allowed
for
indents
that
are
numbers,
and
this
was
like
that.
We
could
write.
B
Right
yeah,
it
also
allowed
for
I
don't
know
it
allowed
for
both
is
what
it
basically
comes
down
to,
and
this
got
a
little
tricky
because
it's
going
to
say,
if
I,
if
I
take
this
off
here,
it's
going
to
say:
hey,
wait.
A
second
string
and
boolean
have
oh
it
allowed
for
booleans.
That's
right,
not
for
numbers
it
allowed
for
brilliance.
We
could
do
invent
moving
too
fast
because
we're
out
of
time.
So
it
said
it
allows
for
indent
false.
B
But
it's
saying
hey
you
told
me
indents
always
going
to
be
a
string,
but
then
there's
this
other
thing
saying
it
could
be
a
string
or
a
boolean
that
doesn't
make
sense
and
I'm
like
yeah
you're
right.
It
doesn't
make
sense,
but
I
have
to
just
ignore
it
for
now.
I'm
sure
there
is
a
solution,
but
that's
a
specific
thing
to
that.
B
One
really
weird
yeah
one
of
the
things
that
I
think
almost
none
of
these
clients
were
written
with
the
knowledge
of
is
that
it
is
possible
if
you
use
a
the
log
format
that
we
saw
in
the
very
beginning.
B
It
is
possible
for
these
things
to
get
a
an
array
of
requests,
and
that
means
that,
for
I'm
sorry,
not
just
requests
but
an
array
of
parameters,
not
just
a
string
and
there's
a
lot
of
functionality,
deep,
dark
inside
of
http
snippet
to
allow
for
this,
and
I
don't
think
that
anybody
wrote
any
of
these
targets.
With
that
in
mind,
like
they're
treating
things
as
though
they're
calling
meth,
this
will
fail.
I
mean
they're
calling
methods
that
will
create
runtime
type
errors.
B
If
you
get
something
that
has
a
different
format,
and
I
don't
I
need
to
look
into
that
more.
But
I
didn't
want
to
change
that,
because
the
point
of
this
particular
project
is
not
to
do
bug
fixes
today,
but
if
we
uncover
them,
that's
cool
sorry
about
this.
This
is
the
the
thing
imaging
we
were
looking
at.
Before,
don't
be
sorry,
I
I
have
made
many
findings,
and
this
is
probably
the
worst
one,
but
there
were
others
that
were
really
bad
and
were
very
fixable.
B
This
one
just
happened
to
not
be
super
easy
to
fix,
but
we'll
get
there.
I
don't
think
anyone
has
responsibility,
if
that's
what
you
say
so
yeah
well
anyway,
that's
the
a
lot
of
talking.
I
need.
I
need
a
lot
of
water.
Well,
thank
you
for
coming
everyone,
sorry
for
going
a
few
minutes
over,
but
hopefully
this
was
helpful.
B
I
guess
I'll,
probably
post
this
somewhere
in
the
readme,
maybe
of
http
snippet
until
the
day
comes
that
we
do
another
one,
that
we
explain
what
the
project
is,
and
you
know,
or
at
least
I'll
post.
The
first
part
I
mean
the
first
clip
of
this
talk.
You
know
walking
through
it
and
then
maybe
in
the
future.
We
can
do
this
in
a
couple
months
again
when
things
are
better.
I
have
a
lot
of
aspirations
for
things.
I
want
to
fix
like
that.
B
Ap,
like
the
api
for
the
binary
thing
for
the
boundary,
but
also
I
want
to
add
more
clients.
I
would
love
to
have
a
rust
client.
I
would
love
to
have
a
couple
other
things
and
I
would
love
to
modernize
the
code
a
little
bit
oops
so
anyway
mark
thank
you
for
joining.
It
was
very
helpful
to
have
a
sounding
board
and
yeah.
I
will
I'll
see
you
I'll
see
everyone
next
time.
Let's
go
yeah.