►
From YouTube: BE Pairing - 20230317 - Hooking into Devise cookies
Description
In this session we continue a problem that was brought up in a past BE pairing -adding a cookie that can be read from about.gitlab.com whenever the user is signed in.
A
B
B
A
A
B
So,
if
only
the
remember
easy
token
is
there
like
this
cookie
will
appear
it's
a
desert
and
then
just
pushing
up
all
my
works.
I
didn't
have
to
think
about
it.
If
my
computer
load
I
ran
into
this
era
in
like
two
tests
and
I've
come
across
this
no
method
there
for
strip
before
and
the
only
thing
I
had
to
do
was
stub
my
test
and
it
cleared
it
out,
but
that
is
working.
Yeah
I
am
stuck
here
because
strip
doesn't
exist
anywhere.
Yeah.
A
A
A
B
A
B
A
A
C
A
Know
have
you
have
you
ever
run?
Do
you
do
you
run
spring
at
all,
so
anytime,
I
run
our
spec
I'll
do
bundle
exec,
oh
nice,
so
it's
working
out
spring
R
spec
and
it
increases
creases
the
run
time
because
spring
is
like
a
server.
That's
always
running
the
background
and
caches
some
like
Ruby
stuff.
It
reads
so
it's
like,
rather
than
if
you
just
run
R
spec.
It's
running
it
has
to
read
through
all
the
Ruby
stuff
brand
new.
A
A
A
A
A
B
C
B
A
C
A
A
We
could
pass
through,
like
the
request
domain,
just
to
hear
temporarily.
You
know
what
I'm
saying
no
somehow
I
think
we
can
get
the
domain
from
the
request
itself.
Okay,
I!
Don't
know
how
to
do
that
and
I'm
really
tempted
to
just
ask
chat
gbt,
but
it's
probably
not
going
to
give
me
the
right
answer,
but
I
am
going
to
ask
it
anyways
and
rails.
How
do
I
get
the
domain
from
the
request?
B
B
B
A
C
C
A
C
A
A
A
B
A
C
A
A
A
A
C
A
C
A
A
C
A
A
B
C
B
A
B
A
B
B
C
C
A
B
B
But
then
would
they
necessarily
hat
like,
even
though
they
had
the
same
expired
time?
I,
don't
think
they
would
still
expire
at
the
same
time,
because
this
remembered
user
cookie
would
have
an
expiration
that
doesn't
necessarily
mean
that
it
started
at
the
same
time
as
the
remember
user
token
that
expiration
didn't
start
until
you
actually
clicked
the
Box.
A
A
A
A
C
B
A
A
A
A
I
mean
that's,
that's
the
and
I
think
also
like
evaluating
the
the
criticalness
of
consistency
like
if
it's
very
critical
that
we're
consistent,
then
yeah.
Probably
this
we
need
to
figure
out
what's
actually
setting
this,
but
if
it's
not
super
critical
and
like
if,
for
some
reason,
these
things
are
off
a
little
bit,
then
maybe
that
maybe
it's
acceptable
to
to
just
do
it
at
this
time.
B
C
A
B
C
A
A
C
C
B
B
A
B
A
A
A
A
A
A
B
B
C
A
B
B
A
A
A
A
C
A
B
A
C
B
A
B
B
A
I
was
it
was
worth
a
shot,
yeah
I,
don't
think
our
our
approach
is
gonna
work,
the
speaking
of
iteration
like
we
could
just
move
forward
with
this
approach,
and
it
just
works
a
little
bit
and
then
try
to
improve
it.
It'll
work,
if
you
haven't
clicked.
Remember
me
but
it'd
be
great
to
get.
Remember
me
working
so
it
does
seem
like
we
need
to
hook
into
whatever
recreates
that
get
lab
session
thing
is
we
need
to
hook
into
that
and
that'd
be
great,
because
then
we
only
get
one
cookie.
B
A
A
A
B
A
C
A
B
A
C
A
A
C
B
C
A
B
A
C
B
B
A
A
B
B
C
A
A
C
B
B
C
A
A
A
Can
we
go
back
to
the
vs
code
and
go
ahead
and
let's
move
our
our
eye,
shell,
we
can
get
rid
of
line
29
and
let's
try
moving
the
binding
price
shell
into
the
active
session
set
because
I
see
that
we
pass
in
the
off
dot
request
thing
there.
It
says
that
this
thing
gets
a
reference
to
the
request,
so
just
anywhere
in
here,
I
think
if
we
could
do
the
binding
price
shell
I
want
to
see
what
other
things
are
on
that
request.
A
B
A
C
A
A
A
A
A
A
A
A
A
On
line
28,
there's
off.request,
is
there
an
off.response
or
something
like
that?
I
really
don't
know
or
like
at
this
level?
Is
there
another
kind
of
parameter
we
need
to
be
passing
into
active
session
set
so
that
we
can
do
this
I,
don't
know,
but
being
able
to
act
being
able
to
write
cookies
from
here
is
the
goal
and
I'm
not
really
entirely
sure
how
to
do
that.
You
can
even
share
this
line
of
code,
so
you're
not
like
super
just
waiting
on
it's
really.
Even
if
you
share
this
line
of.
C
A
A
About
that,
no
I
would
even
just
leave
a
a
question
to
this
line
of
code
on
the
development
Channel
or
the
back-end
channel
of
like
hey.
If
I
need
to
write
a
cookie
from
here,
how
can
I
do
that
and
someone
has
all
the
knowledge
to
be
able
to
do
this,
but
yeah
Jesse
would
probably
be
able
to
definitely
help
too
so
yeah.
Hopefully.
Hopefully
this
is
an
iterative
iterative
improvement
but
yeah
sorry,
we
hadn't
been
able
to
solve
the
problem
yet.
B
B
A
Currently,
as
it
stands,
we're
writing
both
cookies
nicely.
We
have
the
expiration
for
that
at
one,
but
that
doesn't
ever
update.
So
it's
not
gonna
work
out.
This
is
where
we'd
be
able
to
get
it
to
figure
out,
be
able
to
hook
into
it,
updating,
but
maybe
even
just
pushing
up
what
you
have
and
sharing
that
with
Jesse
she'll
be
able
to
figure
out
what's
wrong,
so
cool
thanks
for
bringing
the
problem
and
yeah
thanks
for
patiently
debugging
and
throwing
things
at
the
wall
with
me
as
we
try
to
figure
it
out.