►
From YouTube: Monitor Respond Live Stream Coding 05.10
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Okay,
so
we're
live
so
this
session
is
oh
I'm
just
going
to
mute
it.
Let's
hear
myself
again
so
this
session
is
the
monitor,
respond
front.
End
live
coding
session,
so
our
plan
is
to
do
this
every
week
around
the
same
time,
Tristan
and
I
are
both
front-end
Engineers
on
monitor
respond.
B
So
our
goal
is
to
work
through
our
normal
workflow
and
talk
a
little
bit
more
about
the
thought
processes.
How
we
do
things
why
we
do
things
in
that
way,
so
yeah
applying
this
sort
of
this
every
week
same
time,
so
yeah.
B
B
B
What
you
call
it
tag
teaming
on
this
so
because
I'm
in
Europe,
interested
in.
B
Zealand
I've
been
working
on
it
during
my
day,
Tristan's
been
working
on
it
during
his
day
and
we've
made
comments
on
the
issue
and
you
can
see
the
issue
read
the
comments
read
the
Handover.
No,
it's
mostly
been
on
there.
So
that's
been
also
an
interesting
way
to
work
so
yeah.
B
Actually
someone
mentioned
recently
that
this
this
interesting
way
of
working
was
of
of
interest
to
some
people.
So
if
you
want
to
ask
questions
on
that,
you
can
ask
on
this.
Youtube
video
I
guess
answer
that,
but
yeah
so
to
start
with
Tristan.
Maybe
you
could
catch
me
up
to
date
on
this,
because
I
haven't
been
able
to
focus
on
this
issue
this
week.
So
maybe
you
could
update
me
on
where
we're
at
and
then
we'll
pair
program
and
I'll
drive
and
you'll
navigate
foreign.
C
Yeah
sounds
good.
I
can
share
my
screen
yeah,
but
just
to
show
yeah
just
to
show
a
little
bit.
C
Yeah
so
I'm,
looking
at
the
commits
of
the
issue
just
to
show
what
what
has
changed,
which
isn't
much
just
a
couple
of
commits
one
thing:
I
added
this
was
kind
of
interesting,
so
I
don't
know
if
you
notice,
but
normally
when
we
we
sort
of
put
this
router
and
so
that
the
browser
would
sit
based
on
like
whatever
you
supplied
it,
and
because
it's
in
like
a
guitar
and
a
Setter
for
a
computer
property,
it's
always
like
it
always
has
to
have
a
value.
C
So
when
you
first
load
the
page,
this
set
actually
gets
run
once
and
it
sets
it
it
pushes
it
actually.
Just
pushes
like
say
you
just
go
to
like
get
into
them.
C
It
will
push
the
same
route
that
it
already
has
because
you're
not
trying
to
change
the
tab
or
anything
you're,
just
like
loading
for
the
first
time,
okay,
but
that
actually
causes
an
error
which
was
interesting
like
an
error
in
the
console
and
I
dug
into
it
and
I
found
that
it's
basically
like
view,
router
version
3
Behavior,
not
even
necessarily
behavior,
that
that
everyone's
super
pleased
with
because
yeah,
because
it's
not
like
you
could
think.
C
Maybe
it
should
be
like
a
warning
living
type
thing,
but
effectively
what
the
warning,
what
the
error
is
telling
you
is
that.
A
C
Yeah,
so
that
was
actually
causing
a
problem
in
our
tests,
because
artists
have
a
role
on
them
that
you
can't
generate
a
console
error
during
the
test
or
it
files
the
tips
yeah.
So
I
added
this
this
little
thing
and
you
can
probably
see
it's
slightly
not
very
efficient
because
of
life,
set
a
new
tab
to
this
value
and
then
I'm
calculating
that
value
again.
We're
actually
just
use
new
tab.
That
was,
and
that's
actually
the
my
seeking
commit.
Okay.
A
C
Did
when
I
realized
it
that
it
wasn't
very
efficient,
so
yeah
that
was
like
a
slight
change
to
fix
both
to
fix
the
tests,
but
also
to
avoid
having
to
recalculate
the
route
a
second
time,
and
particularly
in
our
case,
because
we're
doing
some
custom
stuff
like
hiding
elements
on
the
page
that
we
we
actually
don't
want
to
do
that
twice.
It's
not
destructive.
A
C
It
doesn't
cause
any
problems,
but
it's
just
also
not
good
to
do
and
I
refactored
the
tests
a
bit
in
order
to
add
so
I
changed
the
method
signature
because
I
wanted
to
add
like
instead
of
parameter.
C
Yes,
I
hear
I
just
changed
what
what
the
arguments
are
so
previously,
Mount
component
took
two
arguments.
A
C
Dad's
name
options
is
named
and
there's
a
third
one
which
is
Mount,
because
sometimes
we
want
to
mount.
We
want
a
shallow
mount
and
sometimes
we're
up
to
like
deep
Mount,
I
guess,
yeah
full
mount.
B
I
was
looking
at
this
recently
somewhere
else
and
I
had
thought
it
would
make
sense
if
you
say
like,
is
shallow,
mount
true
or
false
and
then
check
that
billion,
but
why?
Why
pass
the
like?
Why
pass
amount
extended
to
the
Mount
component
function.
A
C
I
guess
it
no
they're
pretty
much
the
same
yeah,
not
a
huge
difference.
I
would
say
five
questions
very
either.
So
slightly
prefer
this
way,
because
there's
fewer
lines
of
code
I
think
in
fewer.
C
Good
makes
us
slightly
more
readable
for
someone
who's
looking
at
it
for
the
first
time
that,
like
if
you're,
not
worried
about
what
Mount
does
that's
fine,
but
if
this
whole
thing
was,
let's
look
at
the
actual
currency
of
the
stuff
like
if
this,
if
I
had
that
conditional,
this
whole
thing
would
be
a
bit
like
nested
and
additional
level.
B
C
C
It
would
be
like
a
bunch
yeah
yeah,
just
about
how
to
read,
because
every
time
you
sort
of
pass
this
method
with
your
brain,
you
would
at
least
for
me
I,
would
like
stop
on
the
conditional
and
be
like,
oh
what's
that
doing,
but
a
lot
of
the
time
you're
not
actually
worried
about
that,
because
you're
looking
at
something
else,
yeah-
and
this
just
also,
if
you've
like
looked
at
a
hundred
of
these
like
Mount
components,
I
think
this
is
how
the
team
tend
to
do
it.
So
it's
also
following
the
convention.
C
I
totally
could
have
done
it
that
way
and
it
would
have
still
worked
yeah
yeah
and
that
that
was
in
order
to
add
these
two
tests
that
use
the
mount
extended
because
they're
doing
something
slightly
funkier
that
we
we
don't
always
condone,
which
is
said
relying
on
the
internals
of
an
external
component
a
little
bit.
B
C
C
So
the
external
component,
in
this
case,
is
the
tabs
component
in
bootstrap,
View,
okay
and
we're
relying
on
the
fat
debts
on
two
things.
I
left
a
comment
about
something
else:
you've
actually
in
case,
because
I
thought
it
might
be
kind
of
an
interesting
discussion
as
well
is.
C
Oh
dinner,
yeah
yeah
yeah,
so
we're
relying
on
the
fact
that
when
you
click
a
tab,
Fireside
events
and
you
know,
changes,
Tab
and
stuff,
which
I
think
is
kind
of
fair
to
rely
on,
like
that's
not
probably
going
to
change,
and
then
the
other
property
we
rely
on
is
that
the
currently
selected
tab
has
the
class
active,
which
also
probably
won't
change,
but
it
is
a
little
bit
naughty
to
rely
on
that,
but
yeah.
Basically,
that
was
the
only
way.
C
It
was
the
only
way
that
the
tabs
differed
at
all,
like
all
of
the
implementation
inside
incident.
Tabs
basically
relies
on
that
class
and
yeah
yeah
on
that.
B
C
Class
to
determine
the
behavior
so
like
one
one
interesting
thing:
it's
quite
normally
and
with
few
text
utils
we'll
check
will
want
to
like
check
if
a
component
exists
or
not
so
if
it's
like
mounted
or
not,
but
for
all
of
the
tabs.
All
of
like
the
contents
of
all
the
tabs
is
already
mounted
yeah,
but
it's
just
hidden,
okay,
so
then
the
next
obvious
thing
would
be,
and
the
utsc
Tells
there's
also
like
that
is
visible
check,
which.
A
B
C
A
C
Yeah,
the
best
behavior
would
actually
be.
We
load
the
contents
of
each
tab
when
you
navigate
to
it
first,
but
then,
then,
that
con
all
of
the
contents
remains
there.
C
That
would
be
the
best
for
performance,
because
the
sacrifice
here
is
that
it's
loading
like
all
of
the
timeline
data
when,
when
you
first
load,
which
could
potentially
be
quite
a
lot
and
that
tab
isn't
necessarily
invisible
yeah.
So
that's
something
where,
if
we
use
we're
out
of
you
to
control
the
showing
of
the
tabs,
that
might
be
a
little
bit
more
efficient
because
I
believe
router
viewed
lets.
You
say
only
now
this
when
it
first
become
visible
right
based
on
the
route
yeah
yeah,
so
we're
relying
on
those
properties.
C
The
button
click
Behavior
here
and
then
find
active
tabs
of
use
that
to
basically
filter
all
of
the
tab
buttons
down
to
the
one
that
is
active
and.
B
A
C
A
C
That's
kind
of
like
saying
now:
we
know
which
tab
is
selected.
Okay,
yes,
so
we
can
do
a
test
where
we
click
one
of
the
tabs
and
then
check
that
detail.
We
want
is
selected
and
also
check
that
the
route
is
correct
and
now
sort
of
like
connected
those
things
together
and
verified
that
like,
if,
if
one
of
those
things
breaks,
then
then
the
tab,
switching
behavior
is
probably
broken
or
yeah
at
least
needs
to
be
looked
at.
So
that's
why
that
test
exists.
Yeah.
C
A
C
C
Where,
like
you,
could
write
a
unit
test
but
I
think
I
wouldn't
necessarily
have
like
a
good
enough
coverage.
You
have
to
catch
stuff
in
things
like
this,
where
we're
like.
Integrating
with
a
third
party
Library
like
router
I,
think
we
want
to
have
more
of
an
integration
test
to
be
makes
sense
to
be
safer
yeah
and
it's
unlikely
there.
This
Behavior
and
the
test
component
is
going
to
change.
B
So,
are
we
also
able
to
use
this
to
test
like
what
happens
on
load?
You
know
like
when
you
load
the
page
and
the
URL
has
slash
timeline.
It's
going
to
render
timeline.
C
Yeah
I
did
think
about
that
actually
about
adding
a
test
for
that.
The.
C
The
yeah
the
way
to
do
that
you
would
need
to
sit
if
we
ever
look
at
the
the
code
of
the
actual
timeline.
C
I
was
here
actually
a
bit
of
tab
index
yeah,
and
it
says
if.
C
If
around
doc
params
has
been
sent,
then
the
active
tab
as
yeah
find
the
tab
based.
C
In
the
parents
yeah
so
you'd
need
to
set
this
early
before
the
before
you
mount.
The
component
I
think
would
be
the
way
to
do
that.
Oh.
B
C
Okay,
you
yeah,
which
does
the
way
the
tests
are
set
up.
The
router
get
set
up
before
it's
in
that
before
each
so
you
do
have
access
to
that.
So.
C
Dot
sit
but
actually
now
that
I'm
thinking
about
it
I,
don't
know
if
that's
exactly
how
the
router
works.
Maybe
you
go
router
dot
push,
so
you
push
beforehand
and
then
you
mount
the
component
yeah,
but
it's
it's
a
little
bit
of
a
weird
test
because
that's
not
exactly
what
happens
in
the
real
thing
yeah.
So
it's
not
like
one-to-one,
but
it
is.
C
It
is
exercising
like
an
extra
line
of
code,
so
there
is
value
to
that,
because
otherwise,
that
that,
like
active
tab,
conditional
power,
wouldn't
be
all
right
all
right
now,
I'm,
looking
at
the
commitment,
okay,
yeah!
Normally
you
wouldn't
go
down
this
branch
unload
so
yeah.
That
is,
it
is
checking
another
Branch,
oh
because
route.prams
is
null
initially.
B
C
B
C
Other
way
that
the
other
way
to
do
it-
which
you'd
probably
want
to
do
anyway,
is
to
so
we
could
potentially
skip
the
unit
test
version
of
this,
because
we
know
it's
going
to
be
tested
on
a
feature
test
as
to
add
effective
tests,
so
that
would
be
in
rails,
using
Kevin
Barrow
to
to
load
the
specific
path.
C
Yep
straight
out
of
the
gate
and
then
check
that
after
everything's
loaded
check
that
the
tab,
the
timeline
content
is
there
and
visible
and
yeah,
unlike
if
you
test
utils,
which
in
this
case
doesn't
no
there's
something
physical
or
not
like
it.
Thanks
to
every
all,
the
tabs
are
visible
over
in
capybara
land.
It
does
know
that
because
it's
actually
voting
in
a
full
Starship
and
it's
loading
running
all
the
JavaScript
and
it
has
it
real
gone.
C
So
it
knows
that
at
some
point
in
the
hierarchy
that
display
none
was
getting
sick
yeah.
So
today,
there's
a
few
things
we
could
do.
We
could
like
I,
saw
that
there's
like
a
spec
failing,
so
we
could
make
this
one
pass
or
we
could
add
a
feature
spec
or
workers.
A
B
Was
a
problem
you
brought
up
before
that?
You
were
saying
that
when
we
load
when
because
we
rewrote
how
the
routing
works,
if
you
load
any
issue,
it
now
changes
the
URL
to
like
issue.
Slash
incident
yeah.
A
C
Problem
I
read
it:
it.
A
C
Yeah
that
one
I
didn't
want
to
mention
that
one,
because
that's
kind
of
a
really
specific
issue
that
might
not
teach
much,
although
on
the
other
hand,
it's.
C
C
Yeah,
let's
start
yeah
cool,
so
this
this
stems
from
a
piece
of
tech,
deck
that
exists
for
incidents
only
so
essentially
when
we
created
that
the
concept
of
incidents
in
gitlab,
we
made
a
new
controller,
so
yeah,
that's
a
rails
concept.
That
rails
has
controllers
and
yeah
that
it's
essentially
like
the
the
controller
is
the
entry
point
from
the
route.
C
So
once
the
when
the
rail
service
running
and
the
route
gets
hit,
By
Request
there's
like
this
giant
routes,
file
that
defines
all
of
the
different
routes
that
the
server
can
respond
to
and
then
that
points
the
request
to
a
controller.
C
C
Like
nearly
a
thousand
lines,
long
where
it's
there's
a
few
different
ways
like
a
few
different
kinds
of
syntax
to
Define
stuff.
But
if
we
look
at
the
timeline,
one.
C
C
When
you
go
like
project
slash
issues,
slash
incident,
slash
in
the
idea
of
the
incident,
it
will
go
to
the
incidence,
controller
and
use
the
show
and
I
believe
the
concert
and
terminology
for
that
is
resource.
C
We'll
go
and
find
like
the
yeah,
it
will
display
the
show
page
of
incidents,
and
then
this
is
the
costs
that
it
will
create
for
them
so
further
on
and
like
in
the
controller
and
stuff.
If
you
like,
read
the
path
like
the
URL,
you
can
access
this
property.
C
It
gets
like
auto-generated
and
it'll,
generate
like
the
URL,
like
a
relative
URL
and
an
absolute
URL,
and
things
like
that
for
you,
but
you
just
have
to
give
the
part
the
name
I
could
be
totally
wrong
on
some
of
these
concepts
by
the
way.
This
is
just
how
I
understand
it,
but
I'm
not
a
rails
div.
So
there's
probably
a
lot
more
going
on
that
that
I'm,
not
explaining
yeah,
so
we
can
see
like
alert
management
is
similar
when
you
and
I
think
the
way
this
works
is
like.
C
A
C
C
Yeah
and
then
we
can
look
at
that
instance,
controller
to
see
where
that
stuff
lands,
so
in
here
there's
like
some
public
stuff
and
some
private
stuff,
so
everything
below
here
is
private
and
used
by
the
public
was
exposed
publicly.
C
So,
for
example,
it
will
load
the
incident.
I
believe
this
is
like
fixing
up
to
the
database
and
stuff,
but
only
on
show
so
going
back
to
that
back
to
where
we
were.
C
C
And
this
is
the
bit
of
code
that
says
when
you
have
an
ID
go
to
the
show
page
so
that
that's
how
that
sort
of
connects
together
to
me.
It's
like
a
little
bit
of
black
magic
because
I'm
not
yeah
any
expert
at
rounds
or
anything.
So
I,
don't
know
enough
to
like
necessarily
like
maybe
refactor
some
of
this
to
make
make
it
better
or
like
no
I,
don't
know
all
the
ways
you
can.
C
This
is
also
where
we
add
feature
Flags
in
front
end,
and
also
we
would
do
something
like
oh
yeah,
so
the
other
thing
I
should
mention
is
all
of
the
stuff
and
the
control
look
is
accessed
by
the
Hamel
template,
so
the
Hamilton
blade
will
have
like
a
reference
to
the
incident
where
it
like
loads.
The
incident
in
as
like
a
HTML
data
attribute
or
something
like
that,
and
then
that
gets
possible
trunking.
C
So
if
we
we
can
look
at
that
as
well
to
kind
of
complete
the
picture.
C
Transcendants
and
there's
a
corresponding
show
dot
html.ml.
So
I
guess
we
know
that's
what's
getting
loaded.
C
And
the
equivalent
like
show
for
issues
yeah
and
it's
adding,
like
instance,
to
the
brief
crumbs,
which
are
like
the
like
project,
slash
incident
stuff.
All
right,
I'll
just
show
that.
C
I
just
go
to
like
a
random
issue.
Oh
these
are
all
like
private
here's
one
yeah.
So
this
is
the
breadcrumb.
It's
like
the
section
of
the
page.
So
if
you
were
to
look
at
an
incident,
it
would
say
incident
yeah,
okay,
right,
because
we
see
that
and
add
some
breadcrumbs
yeah.
A
C
So
that
this
is
some
stuff,
that's
going
on
there
yeah
it's
also
like
loading
the
CSS
through
this
helper
yeah
and
the
so
that
that's
kind
of
a
little
bit
about
the
template,
the
controller
and
the
route
and
how
they
all
relate
to
each
other
and
then
back
to
us.
There's
a
problem.
C
When
we
first
created
incidents,
we
made
a
new
controller
and
it
basically
just
delegates
to
the
issues
controller,
because
we
still
want
to
load
everything
that
a
normal
issue
well,
most
things
that
a
normal
issue
have
has.
C
But
there's
the
interesting
thing
with
incidents
is
that
you
can
also
load
an
incident
with
just
the
issues:
controller
without
the
incidence,
controller,
yeah
and
I
think
I
think
that's
typical
dip
because
we
wanted
to
unify
it
so
that
it
was
only
look
using
the
incidence
control
of
incidents,
any
issues
controlled
for
issues.
So
all
of
the
extra
stuff.
That's
in
the
incident
controller,
like
loading.
C
The
incident
also
exists
in
the
issues
controller,
so
we're
duplicating
a
lot
of
code
there,
okay
to
make
it
work
for
both
issues,
slash
black
and
instant,
slash
blog
when
you
like,
look
at
the
URL
for
a
specific
issue
for
a
specific
incident
yeah
and
that
I
think
it
was
done
that
way
because
incidents
show
up
in
the
issues
list,
so
you
can
collect
them
from
Ashley's
list
to
end
up
like
displays
the
issue
URL
long-term
I'm,
not
sure
exactly
how
we
want
to
handle
it.
C
Like
do
we
want
to
have
Just
One
controller
which
handles
incidents
and,
and
it
can
still
delegate
stuff
to
the
issues
controller,
and
that
would
mean
that
we
no
longer
need
to
put
incident
stuff
in
the
issues.
Controller
and
I
I.
Think
that
would
be
like
a
plenty
of
work.
Doing
things
we're
not
going
to
solve
that
issue
as
part
of
this,
but.
C
Yeah
and
then
the
specific
issue
that
I
found
here
was
that,
where
supplying
a
path
to
the
router
to
tell
it
which
URL
to
attach
to
and
it's
we're
supplying
the
incidents
one
and
what
I
didn't
realize,
that
kind
of
makes
sense
is
that
it,
if
you
give
it
a
URL
that
has
like
extra
stuff
in
it,
dinner
overwrites
what's
there.
C
So,
when
you
put
in
like
a
base
path,
it
has
the
slash
insta
in
it.
Even
when
you
just
go
and
look
at
the
incident
from
the
issues
list
which
shouldn't
have
sessions
in
it,
the
router
is
adding
it
when
the
page
loads.
C
A
B
C
Yes
and
it
doesn't,
it
doesn't
display
any
differently
if
the
URL
is
different.
C
A
B
C
C
So
we
want
those
issues
to
still
behave
like
issues
if
people
aren't
like
in
the
instant,
if
they're
looking
at
them
from
like
an
issue
perspective
and
they're
not
like
in
the
incident
management
team
yeah
if
you're,
just
like
a
regular
person
looking
at
issues
or
also
because
you
can
like
promote
an
issue
to
an
incident-
and
we
didn't
want
to
like-
have
that
action
for
a
movement
from
the
issues
us,
because
that
could.
C
C
So
all
that
still
has
to
work,
even
if
you
change
the
issue
to
an
uncertain
yeah.
So
definitely
we
want
to
like
maintain
that
URL
and
then,
if
they
navigate
to
it,
there's
no
reason
to
add
incident
to
the
URL
yeah.
A
C
A
C
That's
a
good
question
like
it
is
something
that
it's
kind
of
strange
behavior
differently
without
without
any
context
you
as
a
user,
like
you,
wouldn't
necessarily
realize
all
of
the
stuff.
That's
going
on
I've
heard
yeah
yeah,
but
yeah
for
the
purposes
of
this
you
know
I,
don't
think
we
want
to
change
their
behavior,
but
it
is
something
we
could
discuss
separately,
maybe
with
but
product
or
ux
people.
C
And
also,
we
should
probably
make
an
issue
to
unify
the
controllers
or
like
to
at
least
to
move
that
incident
stuff
out
of
the
issue
controller,
because
there's
this
code
duplication
until
we
do
that.
A
C
Here,
like
the
issues
controller,
has
this
helper
that
does
a
thing
called
like
load
initial
data.
C
This
is
like
data
that
is
present
on
the
page
when
the
HTML
is
like
initially
returned
to
the
client,
so
that
stuff,
like
the
ID
of
the
issue
that
you're
looking
at
and
then
the
page,
can
use
that
to
make
like
further
requests.
So
this
is
kind
of
like
this
is
what
we
want
to
be
loaded
right
at
the
start
when
they
first
look
at
the
page,
so
that-
and
we
don't
want
this
stuff
to
require
like
a
separate
request
to
the
back
end.
Okay,
if
that
makes
sense.
C
So
it's
things
that
would
maybe
add
like
Jank
to
the
page
if
they
happen
later
so
an
example
of
that
is
like
loading,
the
loading
the
tabs
like,
as
that
happened
much
later,
like
after
a
separate
request,
someone
might
already
be
clicking
trying
to
click
something
on
the
page
and
they're
all
like
jumps
so
yeah,
so
all
the
tab
stuff.
We
want
to
be
there
ahead
of
time,
yeah
and
I've
added
the
base
path
which
gets
loaded
into
the
router,
and
then
it's
also
been
added
to
that
this
helper.
C
That
runs
on
the
instant
page
yeah.
So
it's
on
both
so
that
both
controllers
can
have
access
to
the
the
right
data.
C
But
this
duplication
is
annoying
because
we
never
want
to
like
to
prepare
card.
There's
always
a
risk
that
if
someone
changes
it,
they
forget
one
of
the
locations
and
then
now
it
doesn't
work
all
the
time
and
stuff
so
yeah.
That's
why
it
would
be
good
to
moves
the
incident
stuff
out
of
the
issues
controller
and
to
like
the
instance,
one
and
always
use
the
incidence
controller.
When
we
have
an
incident.
A
C
Adding
not
enough!
No,
because
I
was
naive
when
I
entered
this
I
just
added
the
incident
path,
because
I
forgot
that
there
were
two
routes
and.
A
C
I'm,
adding
the
same
path
in
the
issues,
controller.
A
C
B
But
some
of
our
tests
are
broken
at
the
moment.
You
said.
C
Yeah
and
it's
actually
related
to
what
we've
just
been
looking
at
there's
a
test
that
verifies
the
data,
that's
being
added
by
the
helpline
to
the
controller
verifies.
C
Like
extra
line
that
I've
added
in
the
issues,
helper
data
tests
that
checks
the
output
of
the
helper
as
found
because
we've
changed
the
helper
without
changing
the
tests,
this
is
the
aspect
test
yes
yeah.
So
this
is
the
failure
yeah.
It's
saying:
incidents,
helper
incident,
data
method,
Returns
the
correct
set
of
data
and
the
there's
an
additional
blind
there.
That
didn't
expect,
which
is
the
incident
path
and
there's
also.
B
B
Of
I've
lost
the
issue.
B
A
C
Okay,
that
is
in
there
that
okay
aren't
necessarily
like
failing.
C
Yeah,
there's
one
for
EU,
so
you'll
want
the
second
one
actually,
because
of
it,
this
isn't
not
Enterprise
Edition
coach.
C
B
I
don't
know
if
the
robo
rubber
thing
will
automatically
change
these
to
singles.
But
let's
see.
B
C
It
is
yeah
yeah,
okay
and
that's.
B
C
There,
if
you
go
right
up,
I,
think
there's
a
that
yeah
built,
stopped
I,
think
that's
what's
creating
better
sample
data,
so.
C
B
C
I'm
not
sure
and
that's
sort
of
thing
where
I
would
tend
to
to
get
it
working
and
then
and
push
it
and
then
either
either
I'll.
Ask
someone
in
the
banking
team
or
I
would
I
would
just
put
it
in
review
and
see
what
the
reviewer
says.
A
C
Yeah
because,
like
whoever
I
ask
I'm
gonna
point
to
the
email
anyway,
and
at
that
point
like
if
they,
if
they're
getting
familiar
with
that
team,
it's
probably
more
efficient
as
they're
a
reviewer
as
well
see
yeah,
oh
like,
rather
than
pulling
in
like
one
person
to
ask
the
question
turn
like
another
person.
A
A
C
Sometimes
better
just
to
combine
it
if
it's,
if
it's
not
going
to
be
like
a
long,
lengthy
discussion,
if
it's
just
like
a
single
question,
yeah
I'll
just
include
it
in
the
review
yeah,
because
you
know
it's
going
to
be
just
like
a
one-liner
to
fix
yeah.
A
B
Cool
okay,
I
have
oh
yeah,.
B
A
C
B
Path
contains
the
entities.
What
do
you
mean.
A
A
B
C
Yeah
but
I
actually
don't
know
how
to
do
that
and
Ruby
I
could
do
that
in
gist,
but
not
here.
B
So
yeah
yeah,
so
we're
getting
some
failures,
but
I
just
noticed
like
these
all
have
arrows
and
these
have
colons.
Maybe
you
need
to
move
up.
B
But
anyway,
reading
a
different
error:
undefined
can
create
group,
it
doesn't
seem
like
a
related
error.
Does
it.
C
Yeah,
but
it's
happening
what's
happening
here.
Actually,
oh
because
you're
only.
B
Yeah
I
can
work
on
this
next,
let's
see
if
I
can
get
this
running,
it's
probably
yeah.
Well,
it's
not.
A
A
C
C
Get
the
route
or
get
vegan
path
yeah
for
that
round,
so
we
could
do
that.
A
C
The
line,
maybe
underneath
issue
paths,
we're
going
to
elect
incident
path
and
then
project
yeah,
the
end
of
it
will
be
project
underscore
issues
underscore
incident,
underscore
path,
I
believe
like
this
yeah,
this
one
yeah
yeah
and
in
after
issues
in
the
middle
of
that
what
you
just
pasted,
sorry
so
proud.
You
see.
C
A
A
C
Oh
accepts
the
what's
being
passed
and
is
kind
of
reference.
It's
not
referenced
correctly,
oh
because
we
don't
have
social
wall,
but
that
is
the
project
yeah.
So
we
have
project,
so
you
can
remove
issueable.project
and
then.
C
So
we
net
so
at
this
point
we
were
writing
it.
We
actually
don't
have
an
issueable,
because
it's
way
at
the
top
of
the
test,
okay,
but
somewhere
in
there-
is
an
issue
being
created
and
then,
after
that,
we
could
copy
a
link
to
that.
The
reference
to
that
incident.
C
Yeah,
so
it's
saying,
like
bullet,
create
incident.
True
incident
further
down
context:
oh
okay!
Yeah!
No,
sorry,
that's
something
else!
That's
just
sitting
at
the
mission.
C
C
C
Yeah,
my
rails,
knowledge
isn't
yeah
and
know
how
to
get
the
reference
for
that.
But
I
wonder
if
it's.
If
you
take,
if
you
pull
create
incident
out
and
you
go
let
because,
presumably
when
you
create
an
incident,
it's
returning
a
reference
to
the
incident
which
is
what's
going
into
the
that
with
method.
C
So
you
could
possibly
break
that
out
to
say
yeah
and
let's
colon
incident
and
then
in
Brackets
create
incident.
C
B
C
This
will
be
a
great
a
great
time
to
for
someone
with
some
rails
more
rails,
not
like
seeing
us
to
have
a
look.
B
To
the
Friday
hair
programming,
front-end
pay
programming.
Oh
actually,
this
Friday
is
family
friends
day.
So.
C
C
B
Yeah
yeah
I
might
just
we
might
just
stop
it
here
and
then
yeah.
B
Yeah,
if
people
ask
if
we
can
point
to
it,
but
yeah
yeah
if
you've
got
questions,
feel
free
to
ask
either
on
the
YouTube
or
on
the
issue
itself:
yeah,
cool,
okay,
well,
I'll,
stop
sharing
and
I'll.