►
From YouTube: Insomnia Stream 2022 03 29
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
So
I'm
james
working
on
the
insomnia
team
and
with
me
I
have
dimitri
you're,
also
james,
by
the
way
on
the
window,
at
least
in
my
window,.
B
A
Cool
all
right,
so
what
do
you
think
we
should
work
for
today?
I
saw
a
couple
of
interesting
pr's
on
github
that
have
the
label
insomnia
stream.
B
A
Yeah,
I
don't
think
they
did
yeah
all
right
so.
B
B
A
From
all
these,
like,
I
took
a
very
quick
look
and
for
me
I
think
the
most
important
one
is
trying
to
figure
out
if
we
can
merge
this
guy,
like
support
open
api
303
in
in
the
open
api
to
conc.
A
It
seems
like
it's
a
hard
one,
because
because
there's
like
this
expectation
from
people
to
also
have
support
for
3.1,
but
it's.
A
B
A
Oh
all
right,
do
you
want
to
show
some
love
for
this
pr
focused
on
typescript
yeah?
I
think
typescript
is
gonna.
Help
us
merge
this
easier,
so
I'm
all
in
cool.
So
there's
some
changes
here.
A
I'm
pretty
sure
we're
gonna
have
to
figure
out
what's
going
on,
but
let's
just
give
it
a
quick
look
on
what
this
vr
is
trying
to
do,
replace
for
your
parser
yeah,
with
yaml
module
as
there's
a
breaking
chains
and
nx
again,
some
replacement
of
of
a
class
thingy
and
a
test
case
for
three
or
three
and
there's
the
issue
which
has
been,
I
think,
transformed
into
a
discussion.
A
Let's
go
to
discussion.
Was
that
what
I
was
looking
for,
yeah
all
right.
A
B
B
A
B
Like
like
this,
this
this
author
added
the
yaml
dependency,
where
it
wasn't
there
before
in
order
to
update
the
swagger
parser
and
not
use
their
bug,
is
that
okay
wait?
Here's
a
question
we
should
be
asking
because
it's
been
like
a
year
and
a
half.
Is
that?
Oh,
it's
a
breaking
change
I
was
gonna
say:
is
the
bug
still
there,
but
oh
wow
they
haven't
pushed
it's
still.
10.0.0
is
the
latest
for
swagger
parser,
so
they
haven't,
they
removed
the
yaml
export
and
they
recommend
using
stoplight
yaml
instead.
A
B
Yeah,
so,
while
james
is
setting
that
up
to
show
people
what
I'm
talking
about
so
the
the
this
is
the
swagger
parser
so
like.
Essentially,
we
need
to
update
the
swagger
parser
to
support
3.0.3,
we're
on
version
8
and
we
need
to
upgrade
to
version
10.,
but
when
they
did
that
they
removed
the
yaml
export,
which
is
the
thing
we
were
depending
on
to
parse
the
ammo
in
the
first
place.
So
we
have
to
introduce
like
a
separate
yama
parser,
which
answers
my
question.
Actually
I
was
asking:
why
would
they
do
that?
B
In
the
first
place
it
seems
like
they
agree,
because
they
resembled
it
but
yeah
that
that's
the
whole
reason
for
that.
We
have
the
ammo
parser.
I
think
we
just
used
the
yaml
npm
anyway.
It
was
already
in
the
package
and
it
should
still
be
there
so
yeah.
That's
the
that's
the
whole
reason,
and
it
should
be
pretty
simple
after
that,
but
all
the
same.
A
Yeah,
let
me
pull
the
latest.
A
Dev
and
check
out
this
full
request.
B
A
Okay,
so
you
mean
like
just
making
new
brands
copy
pasta,
whatever
we
have
on
this
vr
and
just
put
it
in.
A
This
thing
is
this
thing
is
not
an
easy
update.
I
guess
all.
B
A
Mean,
let's
cancel
rebasing.
A
A
A
And
let's
see
what
we
updated
in
the
pr,
so
I
don't
think
we
care
so
much
about
this.
We
definitely
care
about
the
swagger
pump
in
open
api
to
kong.
B
A
B
Oh,
it
opened
in
the
number.
I
don't
know.
If
I
I
can't
decide
if
I
hate
when
it
does
that
or
if
I
the
ps4
live,
share,
opens
and
like
browser,
but
anyway
it
seems
to
work
hashtag,
the
future,
all
right,
so
I'm
gonna
grab
the
fixture
and
I'll
work
on
that.
Let's
make
sure
that
the
ammo
dependency
is
still
in
our
project,
it
might
not
be
it
might
not
be
there
anymore.
I
don't
know.
B
That's
interesting,
I
wonder
why
it
doesn't
show
up
on
npm
like
or
on
on
github.
So,
like
you
know,
you
just
saw
it.
I
showed
on
github
the
releases
and
they
don't
have
the
patch
releases.
So
I
wonder
if
they
don't
publish
patch
releases
to
github
and
they
only
do
with
npm,
which
is
kind
of
weird
and
non-standard,
but
that's
definitely
interesting.
A
Yeah,
so
if
you
yeah
yeah,
if
you
look
at
the
at
the
website,
they
have
on
the
packets,
it
says
the
npm
103
thingy,
so
yeah.
A
I
guess
I'll
just
run
an
npm
install
and
check
what's
going
on,
but
this
is
not
gonna
work.
I
don't
just
need
to
run
an
npm
install
since
this.
This
is
inside
packages,
so
I
just
need
to
run
npm
run
bootstrap.
B
A
A
B
Do
you
think
it
matters
if
we
have
terminating
new
lines
in
the
in
the
fixtures
the
original
tests
didn't,
but
maybe
it
doesn't
care,
it
probably
doesn't
care,
I'm
going
to
add
them
anyway,
just
to
be
safe.
B
A
A
B
A
I
think
is
like
minimal,
but
from
what
I
see
here,
yeah.
A
So
the
only
change
is
swagger
parser
gets
updated,
which
means
we
get
the
support
for
free,
because
swagger
parser
supports
the
format
and
then
because
they
deprecated
the
yaml
parse.
We
just
need
to
do
it
on
our
own
and
that's
all
seems
like
pretty
straightforward,
at
least
from
a
solution.
A
B
A
Yeah
because
now
the
thing
has
changed
like
the
that,
ultimately.
B
B
A
All
right,
yeah.
B
A
So,
let's
try
to
test
it,
because
that's
even
better,
if
we
just
need
to
add
a
test
case
and
just
bump
the
version,
and
it
should
work
expected
yamo.
B
Sure
does
yes
a
little
while
ago
it
was
a
bit
of
a
judgment.
Call
I
split
up
the
fixtures
to
run
like
there's.
Two
paths
basically
like
one
is
the
open
api
to
kong
path,
and
one
is
the
I'm
sorry,
one
is
the
declarative,
config
path
and
one
is
the
kubernetes
path
and
they
both
have
their
own
separate
fixtures.
It
was
originally
written
to
be
generic,
so
that,
like
you,
could
put
anything
in
there
yeah,
but
the
thing
is
like
I
wanted
to.
B
There
are
really
different
concerns
like
taking
an
open
api,
config
and
converting
it
to
you,
know:
conquer
kubernetes
versus
declarative,
config,
there's
like
nothing
in
common,
so
I
split
it
up
yeah.
Also
in
the
past,
there
were
no
fixture
tests
for
kubernetes
and
I
at
least
added
one.
So
that
was
the
other
reason.
Yeah.
A
Right,
that's
super
cool
because
that
means
we
just
have
to
run
the
tests
to
verify
the
thing
right
right.
So
if
I
go
into
this
package
station
we
have
a
test.
A
So
I'm
trying
to
remember
by
heart
what's
the
learner
comment,
but
I
think
it's
like
learn
exact
or
run
to
run
its
creep
inside
this.
The
specifics
scraped
inside,
I
think,
let's
see,
learn
around
build
blah
blah
blah.
B
You
can
do
the
like.
Oh
do
we
have
a
live
share.
Wait.
Are
we
sharing
yeah?
We
are
sharing
z,
shell,
you
use
z,
shell
yeah.
You
gotta
show
me
how
to
use
these
shell,
I'm
not
cool
enough.
Yet
do
I
have?
Can
you
see
me
typing
in
here?
Oh,
it's
a
read-only
terminal.
Well,
anyway,
you
can
do
the
prefix,
like
mpm,
run
prefix
package
packages
open
api
kong
like.
A
B
Yeah
exactly
do
I
need
an
equals.
I
never
put
one.
Maybe
you
do
on
mac
you're
on
mac,
right
yeah.
I
don't.
B
You
can
just
tab
should
complete,
and
then
you
can
just
write
test
and
it
should
should
do
it
for,
like
the
space
test,
yeah
exactly.
A
B
That's
the
hack,
but
the
reason
this
is
good
over
the
reason.
Lerna
is
really
terrible,
and
this
is
way
better
is
because,
just
as
doing
all
this
stuff
to
like
you
know,
oh
okay,
you
know
what
this
could
be.
Some
things
have
changed
in
the
meantime,
since
this
test
was
made,
we've
we've
like
added,
tagged,
stuff
and
other
things,
so
we
probably
need
to
update
the
fixture.
That's
good,
all
right.
Let's
look
at
those
changes,
though,
because
I
want
to
make
sure
we're
not
like
actually
coding
in
above.
You
know.
B
A
B
Oh,
you
know
what
it
could
also
have
been.
I
think
when
I
updated
updated
the
fixtures
10
months
ago.
I
also
changed
it
to
use
the
like
strict
equality
check
instead
of
the
contains
object
which
it
was
doing
before,
which
meant
that
you
could
skip
properties
that
were
previously
like
missing
from
the
expected.
B
A
B
B
A
Before
we
got
like
this
extra
stuff,
we
got
the
host
the
bath
board
whatever.
Now
I
put
them
there
because
you
know
that's
what
happens
when
you
pass
this
thing
through
them,
but
it's
still
not
giving
us
back
these.
B
Maybe
that's
maybe
that's
correct.
Let's
look
at
some
of
these
other
yeah
like
if
you
look
at
some
of
these
other
expected.
Okay,
that's
what
you
were
doing.
Sorry
I
didn't
understand,
but
if
you
look
at
these
other
expected
ones
like
none
of
them
have
an
upstream,
oh
one
of
them.
Does
the
http
http
bin
has
an
upstream
imaging
yeah.
I
wonder
I
wonder
what
causes
that.
B
A
A
B
Know
what
you
mean
then.
B
Know
see,
I
don't
know
we
have
to
ask
twice,
I
mean
I
don't
know
enough
about
the
the
declarative,
config
intended
result
to
say
one
way
or
the
other.
B
B
Oh
james,
by
the
way
the
oh
see,
maybe
we
can
move
that.
Can
you
move
your
oops?
I
think
only
you
can
do
it.
The
overlay,
for
we
got
a
chat
message
that
the
overlay
for
the
your
name
covers
up
your
covers
up
your
terminal.
I
think
you
can
click
on
the
where
it
says
james
and
restream
and
move
it
over.
A
Right,
I
can,
I
can
hack
this
just
do
that:
okay,.
A
B
So
we
need
to
figure
out
we're
gonna
have
to
get
into
the
weeds
a
little
bit
to
answer
this
question.
We
need
to
figure
out
if
the
declarative
config
expects.
It
depends
on
that
upstream
section
from
being
there.
A
B
So
it
looks
to
me
like
the
upstream.
The
information
from
the
upstream
comes
from
like
on
x-com
upstream
defaults,
like
that
seems
like
it's
pretty
close
to
what
is
being
generated
in
the
output
yeah.
It
has
like
hash.
I
hash
on
health
checks,
it's
basically
yeah.
I
mean
it's
basically,
that
you
know
I'm
gonna
search,
insomnia's
repo,
because
I
remember
working
on
this
with
something
something
with
upstreams.
B
B
A
B
So
what
we
should?
Okay,
we
can
cross
check
this
x,
kong
upstream
defaults.
B
So
we
should
see
that
the
three
fixtures
that
have
upstreams
generated
also
have
x-com
upstream
defaults
that
one
we
were
looking
at
does,
but
I
think
the
other
two
do
not
maybe
there's
another.
Maybe
there's
one
more
way
you
can
get
other
than
that
over
that
xcom
override
tag.
Let's
look
at
the
source
code
here.
A
B
Okay,
these
unit
tests
should
give
us
all
the
information
we
need.
So
I
think
it's
like
line
300
thereabouts,
yeah
right.
So
given
no
super
yeah,
this
is
that's
great.
Given
no
server
url
should
have
no
upstreams
got
it.
Given
one
superior
url,
it
should
have
no
upstreams.
That's
exactly
the
case.
We're
hitting
giving
one
super
url
and
an
xcom
defaults.
It
should
have
the
upstream.
That's
the
case
that
we're
hitting
in
the
api
with
examples
thing
correct
the
server
urls.
A
Awesome
so
that
means
just
because
we
have
one
url.
We
shouldn't
have
an
app
stream
generated,
so
we're
good
if
we
had
an
extra
one.
Let's,
let's
just
run
the
test,
see
what's.
B
A
Yeah,
okay,
so
now
we
got
app
streams,
yeah,
which
is
great-
I
mean
that's
stuff
than
matt,
but
who
cares?
The
name
is
like
generated.
So
probably
we
changed
how
the
names
get
generated
and
extra
stuff
that
we
don't
care,
since
this
is
just
the
test.
So
this
one
covers
303
support.
At
least
there
might
be
details
that
we
don't
know
so
you
know
we're
gonna
have
to
test
this
a
bit
more,
but
I
think
it's
definitely
a
great
step
forward.
I'm
highly
confident
we
can
probably
mess
this.
A
B
Yeah
well
we're
releasing
so
okay,
that's
that's
another
point
to
bring
up
for
anyone.
Listening
we've
been
it's
not
super
official,
so
you're
getting
it's
a
you're
getting
this
ahead
of
the
ahead
of
the
stream
there
for
a
bit
or
ahead
of
the
the
pipeline,
but
we're
trying
to
release
betas
every
thursday
now
and
if
we
can
merge
this
today,
that
means
that
this
will
be
in
the
next
beta
or
like,
or
it's
most
likely
to
be
in
the
next
page.
B
Sometimes
we
cherry
pick
stuff,
so
I
don't
want
to
make
a
promise
on
that,
but
it'll
definitely
be
in
the
one
after
that.
So
that
means
that
whoever's
trying
to
test
the
open
api
3.03
stuff
can
test
it
on
that
beta,
which
would
be
sweet.
B
A
A
A
Correct
so,
while
I'm
doing
that
I'll
be
pushing
that
and
making
a
pr.
B
B
Okay
cool,
so
here
we
are
full
screen
this.
B
I
don't
know
why
it
showed
our
discussions,
but
let's
go
back
so
this
is
what
I
do
to
find
the
stream
I
scroll
down
and
I
click
the
the
little
pill
there
and
then
it
shows
me
all
the
things
that
we
have
on
the
stream.
So
we
look
at
pull
requests
first,
I
think
there
may
be
some
issues
that
are
tagged
for
this
to
look
at
during
the
stream,
but
pull
requests
always
have
highest
priority,
so
reclaim
focus
on
address
bar
after
focus
is
lost
by
curl
import.
B
Oh
interesting,
I
didn't
know
this
was
a
bug
yikes.
I
that
curl
import
feature
is
a
really
important
one
and
insomnia.
Actually
at
least
I
think
it
is
because
I
use
it
a
lot.
This
implementation
reclaims
focus
on
the
address
bar
every
time.
It
loses
focus
due
to
the
key
of
the
component,
changing
more
about
key
changing
this
message.
B
B
B
This
is
this
is
exciting
that
somebody
fixed
it
but
depressing
that
what
we
have
to
do
to
fix
it.
I'm
very
gracious
for
this
change,
but
it's
like
we
already
have
these
code
smells
in
here
like
we
have
this
we're
comparing
preview,
props,
uniqueness,
keys
and
we've.
This
has
been
like
the
bane
of
our
existence
and
it
has
been
so
painful
in
the
app
to
deal
with
we're
trying
really
hard
to
like
improve
this.
B
But
it's
the
problem
is,
is
that
things
are
a
little
janky
at
the
moment,
and
it's
useful
like
like
it's
so
useful
that
this
person
found
it
and
is
using
it
so
so
they're
using
the
ref
to
set
whether
or
not
it
had
focus
so
here's
a
question.
I
would
immediately
ask:
why
does
this
need
to
be
a
class
member?
Couldn't
I
just
grab
it?
Where
does
it
actually
get
used?
So
couldn't
I
take?
B
Yeah
this
is
this
is
going
to
be
interesting.
B
I
don't
know.
Oh
it's
a
draft
pr
as
well.
Okay,
so
maybe
they're
okay,
I
shouldn't
be
too
critical,
then
maybe
they're
not
intending
for
us
to
actually
look
at
it.
Yet
sometimes
that's,
but
sometimes
people
do
that
or
sometimes
they
you
know
like.
They
just
want
to
hear
our
thoughts
before
like
asking
for
us
to
do
anything,
it's
hard
to
say
sometimes
with
draft
pr's,
but
philippe
ran
it
and
it
it
works
thanks
for
doing
that,
philippe.
B
Let's
look
at
this
related
issue,
so
after
june
17th
2021.
So
this
is
this
is
fairly
long
ago
after
creating
a
red
request
by
pasting,
a
curl
to
the
address
bar
the
cursor
will
lose
focus
after
pressing
the
backspace
key.
So
let
me
show
people
like
what
what
this
is
talking
about.
Can
I
open
insomnia.
A
It's
a
hard
one,
it's
a
bit
of
a
tough
one.
I
I
gave
a
look
at
it
a
couple
of
months
ago
and
it's
not
like
so
straightforward
what
the
change
to
support
this.
B
Yeah
and
we
updated
some
stuff
in
our
stack,
and
you
know
on
that
side
of
things
as
well
recently,
so
I
want
to
show
people
like
a
example
of
why
this
matters
and
like
even
if
we
don't
find
a
solution
today,
just
in
a
few
minutes,
I
can
explain,
explain
why
this
feature
of
insomnia
is
so
critical
to
some
use
cases.
So,
like
I'm
gonna
take
you
know,
I
don't
know
what
this
is
okay.
This
is
like
some
some
thing
that
I
have
from
an
you
know.
B
B
Some
can
somebody
impersonate
me
now
that
I
screamed
this
probably
not
probably
not
well
yeah,
actually,
definitely
because
they
have
my
session
cookie,
all
right.
Well,
I'm
gonna
log
out
and
log
back
in
after
this
no
big
deal,
but
what
you
can
do
is
you
can
copy
as
curl
and
like
let
me
let
me
pull
up
a
text
editor
and
show
like
what
that
amounts
to.
So
then
I
have
all
this
stuff.
B
You
see,
there's
my
user
session
I'll
log
out
in
a
second,
but
anyway
you
can
take
all
of
this
stuff
and
then
I
already
have
it
copied
my
clipboard.
I
don't
need
to
copy
it
again
and
then
you
can
come
over
to
insomnia
and
right
here
in
the
url
bar.
You
can
paste
and
check
out
what
happened.
It's
just
the
url
now
and
look
at
that.
All
these
stupid
headers
are
here.
I
can
click
send
and
it
works
like
it's.
B
B
And-
and
that's
that's
really
really
cool.
It's
like
one
of
my
favorite,
all-time
favorite
features
of
insomnia
is
the
fact
that
you
can
do
that
with
a
crow
request
and
it
becomes
really
critical.
If
you
have
like
something
that
you
like
some
long
thing
you
can
just
come
over
here,
make
the
request
like
log
in
and
make
the
speaking
of,
which
I'm
going
to
log
out
now.
How
do
I
do
that
sign
out
there
session
invalidated.
B
Take
that
red
hats,
but
anyway
it
can
be.
It
can
be
pretty
important
if
you're,
if
you're,
trying
to
debug
something
to
to
use
that
kind
of
code
path
and
insomnia
does
a
really
good
job.
I
don't
know,
if
does
postman,
do
that,
I
I
don't
know
if
other
tools
have
that
feature,
but
the
paste
as
curl
thing
is
super
cool
all
right,
how's
it
going
I'll
log
back
in
here.
A
B
That's
good
to
me:
do
you
want
to
do
you
want
to
pick
a
new
one,
or
I
I
can
say,
probably
we're
not
going
to
get
anywhere
with
the
one
we
were
just
looking
at
because
we
need
to
like.
We
need
to
think
a
little
bit
like
about
what
we're
gonna
do
there,
I'm
glad
that
it's
it's
got
brought
up
and
like
I
can
post
the
link
to
the
stream
to
the
people
that
are
listening
on
that
issue,
and
they
can
see
some
of
our
rationale
about
it.
B
It's
been
an
issue
lately
we
added
some
stuff
onboarding
recently,
which
focuses
the
url
bar
as
soon
as
you
start
insomnia
for
the
very
first
time,
and
that
was
supposed
to
be
easy
and
it
ended
up
being
like
like
soul-crushingly
difficult,
we
made
it,
we
got
it
working,
but
it
was
a
lot
of
hacks.
It
took
to
get
to
the
finish
line
and
it
made
us
really
take
a
step
back
and
say:
okay,
we
need
to
take
a
bigger
look
at
how
we
do
focus
management
because
focus
management
is
like
a.
I
mean.
A
Yeah
also,
if
you
have
to
support
weird
devices
like
I
don't
know,
hybrid
devices
where
they're
like
have
that
screen,
but
it
can
also
be
moved
to
whatever
it's
getting
harder
and
harder
to
to.
You
know
properly
support
these
things
and
I'm
pretty
sure
you
can
go
far
with
css
and
some
stuff,
but
at
some
point
you
just
need
javascript
to
make
sure
you
can
support
some
features.
B
Do
you
wanna
we'll
handle
the
open
api?
I
was
gonna
say
we
can
close
the
other
like
the
prior
pr
from
api
sync,
but
we'll
do
that
later
or
like
link
to
the
new
one
yeah
yeah,
you
wanna,
you
wanna
drive,
and
then
we
can
pick
a
new
one.
We
got
10
minutes.
A
Yeah
we
can,
we
can
start
something
else.
Let
me
share
my
screen
again
all
right.
So
what
else
do
we
have
so
this
guy
thanks
and
almost
done
so
now
we
have
like
a
couple
left.
A
B
A
Let's
read
it,
I'm
just
taking
a
look
behind
because
I
see
felipe
already
approved
on
january.
Oh,
I
see
okay,
there's
some
disgusting,
oh
god,
okay,.
B
What
did
I
say?
Yo?
Yes,
this
one?
Okay,
we
could
always
do
this.
I
feel
bad
about
this
sergey
if
you're
watching
or
listening,
I'm
sorry
we
keep.
We
did
look
at
this
two
streams
ago.
I
think
also
adding
some
tests.
We
just
need
to
add
like
a
lot
of
tests
for
every
code
path
here,
because
a
lot
of
codepaths
were
updated.
B
It
looks
like
they're
all
right,
I
mean
it
looks
like
they're
all
correct,
it's
it's
not
that
it's
just
that
this
is
something
we
didn't
have
any
test
coverage
for
before,
and
we
really
want
to
have
coverage
for
this,
so
we
were
in
the
process
of
writing
tests
for
it.
I
think
yeah
james.
You
were
here
for
that.
We
were
yeah.
A
A
And
then
that's
another
one,
swagger2
importer,
so,
okay,
let's
see
the
working
progress
one.
Perhaps
we
can
talk
about
it,
it's
in
depth.
This
pull
request
ensures
the
regeneration
of
the
base
environment
when
importing
a
collection,
okay
into
an
existing
modifying
the
export
type
without
losing
all
the
exported
environments.
A
Yeah
I
mean
that's
the
that's
the
thing
why
everyone
is
like
saying
think
about
yourself
in
six
months
from
now.
B
A
Okay,
opener
made
some
comments
that
this
might
not
be
a
regression.
B
B
A
Yeah,
okay,
so
the
solution,
then
that
we
see
here
at
least
the
work
in
progress.
One
is
regenerate
the
base
environment
id
when
importing
a
collection.
A
A
A
No,
no,
this
pace.click
stuff,
I
think
it's
playwright.
Oh
it.
B
A
B
A
Those
are
not
like
in
here:
okay
got
it,
so
all
this
thing
is
doing
all
I
mean
you
know
it's
not
so.
B
A
Yeah:
hey:
how
are
you
doing
man,
okay?
So
what
what
seems
to
be
happening
here
is
yeah,
it's
taking
the
resource
type.
A
B
I
think
I
get
it
like
it's
what's
happening.
The
bug
is,
you
can
import
the
environment,
but
the
workspace
that
it
was
imported
to
doesn't
exist
anymore,
and
so
they
don't
line
up
like
see
this,
like
parent
id,
equals
base
environment
id
key
yeah,
yeah
yeah.
That's
that's
the
thing.
So
it's
saying
like
if
it's,
if
it's
a,
if
it's
an
export
type
environment
and
the
the
parent
id
doesn't
exist
or
doesn't
match.
B
Then
do
that
then
do
it
then
force
it?
I
mean
like
this
is
a
real
problem
because
like
well,
I
mean
what
else
is
the
app
supposed
to
do
if
the
you
know
like,
if
you
have
the
environment
there,
otherwise
it
so.
This
is
a
thing
that
I
wish
insomnia
had
a
better
solution,
for
it
is
very
possible
to
have
so-called
orphan
database
entities
where
they're
there
in
the
they're
there
on
the
disk
they're
there
in
the
database.
B
Insomnia
is
can
access
them,
but
because
they
don't
have
the
associated
like
the
foreign
key
associative
relationship
match
to
their
parents,
they're
not
actually
accessible
in
the
ui.
Despite
the
fact
that
the
the
entities
are
there-
and
you
know
when
things
are
screwed
up
from
time
to
time,
they
can
happen,
and
this
is
sort
of
an
example
of
that,
where
we're
trying
to
graft
one
environment
into
another
by
means
of
an
import,
then
we
get
this.
A
B
Preferably
also
a
test
that
fails
that
shows
what
the
existing
bug
is
would
be
the
best
thing
like
a
commit
with
a
test
that
fails
and
then
another
commit
with
this
code
that
makes
it
pass.
That
would
be
like
the
best
that
this
would
get
quickly
merged.
Probably
if
that
was
the
case,
because
then
we
can
have
some
cons
like
we
can
have
some
faith,
that
not
only
does
this
fix
work
but
that
it
won't
break
in
the
future.
B
A
All
right
that
seems
like.
A
No,
I
think,
we're
good.
This
one
is
already
like
making
my
brain
melt,
trying
to
understand
all
the
relationships.
A
A
Yeah
for
now
I
would
try
to
put
something
on
a
worker
process,
but
I'm
guessing.
If
we
move
forward
with
you
know,
changing
a
lot
of
insomnia's
architecture.
A
A
All
right
all
right,
cool
thanks
everyone
for
watching
thanks,
dimitri
for
everything
on
the
stream
and
see
you
in
the
next.