►
From YouTube: UX MR Review Example – Enabling switching between project-level and instance-level endpoints
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
Hello
there,
this
is
an
overview
of
a
merge
request
that
I'm
reviewing
from
the
ux
perspective,
so
the
merge
request
is
from
the
package
stage
enabling
switching
between
project
level
and
instance,
level
endpoints
when
viewing
the
npm
package
registry
setup
step.
Sorry
for
this
little
noise
in
the
background,
essentially
what
I
usually
do
when
I
get
to
merge
requests
the
first
thing
after
reading.
The
description
which
I
already
did
is
to
see.
If
there
is
a
review
app
running,
so
I
can
really
see
the
ui
exactly
like
it
is.
A
There
isn't
one
here
usually
when,
when
working
with
features
either
from
create
or
from
my
area
where
I
have
better
knowledge
of
the
setup,
I
I
sometimes
also
create
a
gitpod
instance,
but
in
this
case
since
I
have
never
set
up
packages
before,
I
think
that
would
be
a
bit
cumbersome.
So
let's
check
the
screenshots.
A
So
essentially,
what
this,
mr
is:
adding
is
a
radio
button
selector
to
allow
you
to
switch
between
setup
steps
for
a
project
level
package
and
an
instance
level
package
so
where,
before
you
would
set,
this
is
set
for
the
instance
level,
because
there's
no
project
name
here
now.
I
have
the
option,
for
instance,
level
and
project
level,
and
then
is
this.
The
video
yeah.
A
So
we
can
see
the
difference
here
in
the
url.
One
is
just
packages
the
others
packages,
slash
projects,
slash
packages
in
the
example,
and
it
also
adds
the
recommendation
is
already
there
all
right.
So,
from
my
perspective,
this
seems
to
make
sense
for
an
instant
there.
I
was
a
bit
in
doubt
if
these
two
were
the
same
thing,
but
no
this
show
npm
comments.
Box
drop
down;
it
only
show
changes
the
examples,
but
it
doesn't
really
change
anything
in
the
actual
workflow
itself.
A
A
A
Since
we're
adding
a
new
option
here
with
the
radio
buttons,
I
think
it
would
be
useful
to
to
have
a
wider.
Wider
range
is
not
the
right
term,
but
a
wider
way
to
point
the
user
to
the
documentation.
Because,
oh,
what
is
this
new
thing
here
on
the
page
right?
So
you
click
the
documentation
and
it
takes
you
there.
So
that's
more
or
less.
The
idea
behind
this
comment.