►
From YouTube: Create:Editor - Solution Validation VS Code Web IDE
A
Hi
there,
my
name
is
michael
lee
of
the
editor
group
and
today
I'll
be
going
through
the
flow
for
the
solution,
validation
and
review
of
the
insights
that
we
found
from
our
tests.
So
what
we
wanted
to
look
at
for
the
solution.
Validation
was
the
initial
impression
of
users
when
they
landed
on
the
web,
id
and
visual
studio
code
web
id
coming
in
from
gitlab,
and
then
vice
versa,
going
from
a
merge
request
or
mr
to
the
web
id
and
seeing
that
whole
flow
and
seeing
opportunities
or
pain
points
along
the
way.
A
A
A
We
asked
them
how
they
would
go
from
here
into
the
merge
request
so
going
in
from
here
clicking
into
here
opening
up
the
web
id,
and
here
we
wanted
to
see
if
they
noticed
the
gitlab
workflow
and
more
especially
what
they
expected
to
see
once
they
landed
into
here.
What
kind
of
files?
How?
How
would
that?
How
would
those
files
be
presented
to
them
and
let's
go
through
the
insights
of
what
we
learned
so
overall?
A
A
So
the
commit
flow
itself
was
new
to
participants.
Even
if
visual
studio
code
was
their
primary
id
because
11
out
of
19
participants
actually
use
the
terminal
to
go
through
their
commit
flow.
So
they
would
enter
git
commands
through
the
terminal
and
handle
things
like
that.
So
seeing
the
visual
wave
handling
commits
and
going
through
that
with
visual
studio
code
was
a
new
thing
for
them,
even
with
that
they
were
able
to
succeed.
A
Going
through
the
commit
flow,
when
we
suggested
that
the
update
message
was
update,
this
file
like
a
simple
message,
they
were
looking
for
ways
to
add
the
issue
ticket,
be
it
from
jira
or
gitlab
to
the
titles
of
the
commits
or
the
merge
request.
Titles.
So
that's
something
that
we
should
keep
an
eye
out
for
in
the
future.
A
A
So,
within
the
figma
prototype,
there's
hover
states
on
these
icons,
but
there
are
no
tooltips
on
the
icons
so
for
certain
people
and
they
weren't
sure
which
button
was
commit,
whether
that's
the
check
mark
or
the
plus
sign.
So
there
was
a
lot
of
guessing
during
this
the
step
and
some
people
suggested,
perhaps
adding
them
to
it.
We
know
that
in
reality,
visual
studio
code
does
allow
us
to
add
tooltips
to
this.
So
if
we
do
proceed
with
icons
in
the
in
the
source
control
view
that
we
add
tooltips.
A
So
the
gitlab
workflow,
which
is
something
that's
introduced
through
the
gitlab
extension
and
visual
studio
code
extension
that
allows
you
to
view
issues
and
merge
requests
directly
within
visual
studio
code.
So
our
idea
here
was
that
if
we
navigate
people
to
this
view,
when
they're
looking
at
a
merge
request,
they
can
start
getting
familiar
with
the
workflow
and
understanding
how
to
review,
merge
requests
directly
from
visual
studio
code
and
perhaps
using
this
as
a
starting
point.
A
People
were
intrigued
about
the
layout,
but
no
one
in
this
section.
This
set
of
participants
were
familiar
with
the
whole
workflow
extension.
So
that's
something
to
take
a
note
of
that,
even
though
the
extension
has
been
around
I'm
not.
Everyone
is
familiar
with
it
and
it
was
noted
as
a
positive
thing
that
we
directed
people
into
here.
A
When
coming
from
a
merge
request,
the
view
that
users
expect
to
see
is
a
way
to
view
the
diff
of
change
files,
so
a
list
of
change
files
and
a
way
to
see
the
differences
between
them
within
the
prototype
itself.
That
was
a
oversight
on
my
side,
where
I
didn't
include
that
view,
but
it
prompted
and
this
kind
of
discussion-
and
we
know
that
within
the
visual
studio
code,
we're
able
to
view
diffs
of
files.
So
this
is
something
that
we
will
connect
in
the
final
flow.
A
So
the
notification
that
popped
up
helped
people
navigate
to
the
create
a
merge
request
view
one
participant
was
not
successful
because
the
notification
was
hidden
in
the
window,
be
it
the
visual
studio
code.
Web
ide
will
be
inside
the
browser,
that's
something
to
consider
that
sometimes
there
might
be
things
overlaid
on
top
that
might
hide
in
that
experience,
yeah
and
other
users.
Here's
mentioned
that,
usually
when
they
see
these
types
of
notifications
that
they'll
close
it
without
thinking
too
much
about
it.