►
From YouTube: Reload and Apply MR Settings Feedback
Description
Thinking through what I'd like to see and experience with exploring reloading and applying settings in a merge request.
A
Sort
of
explain
further
my
comments
about
requiring
a
reload
and
whether
or
not
that
was
possible,
and
this
might
be
easier
just
to
do
in
a
quick,
video
and
I'll
sort
of
talk
through.
What
I
was
thinking
would
happen,
we'll
see
so
I'm
gonna
share
my
screen.
This
is
an
mr
and
it's
got
like
30
changes,
which
is
big
bit,
but
not
incredibly
large,
and
there
is
some
collapsed
files.
A
A
If
I
click
this
tree
view,
I
click
and
there's
sort
of
that
noticeable
pause
feeling
in
there
like
it,
doesn't
feel
instant.
It's
pretty
quick
and
it
happens.
There's
really
no
like
user
feedback
that
that's
gonna
happen,
and
I
don't
the
reload
and
apply
might
not
be
the
right
solution.
Maybe
we
should
just
show
like
a
spinner
when
that
happens,
because
those,
I
think
that
makes
it
feel
slow
and
clunky.
A
The
same
thing
happens
if
we,
let's
close
the
file
tree,
so
we
can
see
this
a
little
bit
bigger,
even
like
just
sort
of
like
toggling.
These
things
in
and
out
just
feel
a
little
slower.
Let
me
do
this
so
right
now
we're
in
side
by
side
diff.
So
if
we
change
this
to
inline
like
nothing,
nothing
there,
it
goes
nothing,
nothing,
nothing,
nothing,
nothing,
nothing!
Nothing!
Nothing!
Nothing,
nothing
there.
A
The
other
thought
is
like
data
reductions,
and
I
know
for
at
least
for
side
by
side
and
inlines.
We
have
unified
diff
and
so
like
there's
not
much
data
reduction,
probably
there,
but
show
one
file
at
a
time
that
also
feels
slow
to
get
in
and
out
of
that,
whereas,
like
potentially,
we
could
re-request
one
and
then
sort
of
like,
as
you
click
next,
maybe
maybe
click.
I
don't
know
this.
A
A
That
feels
faster
because,
like
I
clicked
it
and
then
like
I
know,
the
application
is
still
working,
and
so
I
think
what
I
was
after
with
the
original
issue
was
more
of
how
do
we
tell
users
that,
like
something
has
to
happen
and
provide
that
user
feedback?
In
that
experience,
and
I
think,
applying
and
reload
gives
you
the
ability
to
sort
of
like
one,
if
I
were
to
change
multiple
settings
in
that
drop
down
to
do
two
requests
at
once
like
so?
A
Maybe
we
change
from
side
by
side
to
diff
and
one
file
at
a
time
all
at
the
same
time,
or
something
like
that,
so
it
gives
us
an
ability
to
sort
of
like
batch
that
event
happening.
It
also
gives
us
a
way
to
like
provide
user
feedback,
and
maybe
we
don't
need
the
apply
and
reload.
Maybe
we
just
need
to
go
to
a
model
where
we
like
show
the
spinners
for
that.
A
A
So
maybe
that's
like
another
piece
to
this
is
like
click.
The
drop
down
drop
down
goes
away,
spinner
comes
up
on
the
screen
and
like
at
least
you
know,
something
happened
or
your
event
was
taken
because
right
now
we
just
sort
of
have
this
like
outlining
of
the
buttons,
and
I
don't
think
that's
a
great
experience.
So
that's
really
what
I
was
thinking
about.
A
There
is
trying
to
make
it
so
that
it,
the
user,
feels
like
the
app
is
doing
something
because
I
think
the
user
feeling
like
the
app
is
doing
something
makes
the
app
feel
responsive
versus
what
it
feels
like
today
is
like
I
clicked
on
something
I
don't
know
if
anything's
happening,
and
so
it
doesn't
feel
responsive.
Even
if
those
measurements
are
the
same,
or
maybe
it's
actually
like
slightly
longer
of
an
experience
and
with
a
spinner,
I
as
a
user,
I
think,
would
feel
like
the
application
did
something.