►
From YouTube: Growth - Lightning Talks - Rails Routing
A
A
So
in
order
to
use
this
project
ID
as
the
usually
what
you
would
use
for
a
show
as
an
ID
right
on
a
on
a
controller,
but
the
idea
in
this
case
is
the
project
ID
and
so
we're
nested
inside
of
it.
So
the
only
way
to
that
is
being
used
before
was-
and
this
just
recently
changed
from
a
it
used
to
be
Index
this
that
Mr
got
merged.
That
I
did
to
change
it
to
a
show,
so
it
used
to
be
a
an
index
action
there
in
that
index.
A
Action
was
merely
using
project
ID
as
a
parameter
to
find
the
project,
which
was
the
thing
you
were
nested
inside
of
already
so
as
far
as
restful
routing
goes,
that
really
felt
like
it
should
have
been
a
show,
a
member
function
of
of
the
thing
you're
nested.
Inside
of
so
that's
the
change
that
was
made
there
and
we
can
see
it
show
up.
A
Let's
see
if
I
can
find
the
right.
One
right
here,
so
this
was
the
one
for
the
show
action,
as
you
can
see,
it's
using
the
project
ID-
and
it's
saying
right
here
as
part
of
it,
is
to
she's
using
a
project
idea
from
it.
So
it
shows
up
as
as
just
the
learn,
git
lab
inside
of
the
project
as
the
show
action
now.
What
we
wanted
to
do
was
we
were
moving.
I
wanted
to
move,
continuous,
onboarding
and
so
right
here.
A
I
have
this
line
here
is
for
a
deprecation
overall
in
case
there's
any
when
we
roll
out
this
issue
in
case
there's
any
this
merge
request
in
case
there's
any
current
instances
that
may
be,
or
people's
browsers,
which
may
be
sitting
on
the
continuous
on
the
on
one
of
our
pages
and
they
might
go
to
the
old
round.
So
it
needs
to
be
there
to
redirect
for
a
you
know
at
least
a
release,
or
so
you
know
a
release
of
uh.com
or
so
so.
That's
why
this
one
is
here.
A
As
a
member
function,
so
it's
a
member
function
because
we
were
able
to
say
the
traditional
param
here
is
ID
by
default,
so
we
were
able
to
change
it
to
ID
or
to
project
ID,
and
so
when
we
do
it
like
that,
it'll
quack,
exactly
like
we
want
it
to
and
give
us
this
right
here
and
so
now.
This
gives
us
a
restful
route
where
we
can
go
in
the
UI
and
say:
okay
I'm,
going
to
learn
gitlab
I'm
inside
this
project,
so
you'll
have
your
namespace
name.
A
A
A
A
A
Why
can't
I
so
I
was
banging
my
head
up
against
I
want
to
use
resource,
but
if
I
use
resources
which
would
give
me
index
show
you
know
everything
like
that
and
I
could
use
show
then,
but
it'd
be
the
only
show.
The
problem
is
that
you
know
now.
This
turned
this.
This
had
to
be
learned.
Git,
labs
and
I'm
like
I.
Don't
want
my
URL
to
look
like
that.
I,
don't
want
to
have
an
s
on
there
because
it
doesn't
make
any
sense
and
so
I.
A
A
Let
me
give
it
a
try
here
and
we
have
a
few
other
instances
in
the
app
where
people
use
it.
I
haven't
seen
it
used
yet
for
project
ID
by
cease
on
something
like
name
and
something
else.
You
can
look
in
our
routes,
routing
files,
so
I
put
it
there
and
I'm
like
this,
makes
a
lot
of
sense
to
me
now.
It
feels
really
good
because
it's
like
it
has
nothing
learn.
Gitlab
is
nothing
without
the
project
that
it's
inside
of.
So
it's
really
inside
of
the
project.
A
It's
really
about
the
progress
of
you
know.
Technically
it's
about
the
progress
of
the
namespace,
because
that's
what
the
onboarding
is
about,
but
we're
basing
it
off
of
a
project
you
have
to
be
inside
a
project
to
show
learn
git
lab.
So
it
really
made
sense
to
me
that
this
was
not
trying
to
find
another
container,
even
though,
and
be
resourceful
inside
of
the
resource
that
was
already
inside
of.