►
From YouTube: GitLab 13.9 Kickoff - Create:Editor
Description
Monthly kickoff video for the Editor group discussing upcoming work planned for GitLab 13.9.
See our planning issue for more details: https://gitlab.com/gitlab-org/create-stage/-/issues/12789
A
I
did
want
to
highlight
just
a
few
real,
quick
and
I'll
start
with
the
web
ide.
I
want
to
build
on
something
I
think
I
talked
about
in
the
last
kickoff,
which
was
in
13.8.
We
completed
a
proof
of
concept
for
using
editor
light,
which
is
an
abstraction,
a
thin
layer
around
the
monaco
code,
editor
that
we
use
for
web
ide,
and
we
want
to
replace
the
the
the
standard
implementation
of
monaco
that
we
use
on
the
web.
A
Ide
with
this
editor
light
library,
which
is
what
we
use
to
power
snippets
editor
and
in
a
couple
other
places
throughout
get
lab.
This
is
a
an
effort
that
we
hope
will
will
bring
sort
of
consolidation
and
consistency
to
the
editing
experience
across
git
lab
and
in
the
process
of
implementing
the
proof
of
concept.
We
also
found
that
there's
a
somewhere
between
a
15
and
20
percent
performance
increase
in
some
scenarios
as
well,
so
we're
we're
gaining
some
benefits
there.
A
So
in
thirteen
nine
we'll
go
ahead
and
move
forward
with
that
proof
of
concept
and
implement
that
in
the
web
ide
you
won't
see
much
difference
other
than
that
performance
increase
that
I
mentioned,
but
in
the
back
end
we'll
be
using
a
lot
of
a
lot
of
code
that
doesn't
need
to
be
duplicated
elsewhere.
A
This
is
a
issue
that
I
marked
as
stretch,
so
we
may
not
ship
this
in
13.9,
but
we're
hoping
to,
but
I
did
want
to
highlight
something
related
to
the
web
ide
that
came
up,
and
that
is
that
we
had
an
issue
in
13.8
where
we
wanted
to
change
the
behavior
of
the
single
file
editor.
So
it
was
consistent
with
the
web
ide
specifically
when
it
comes
to
how
it
handles
trailing
new
line,
characters
in
the
in
the
files
themselves.
A
The
single
file
editor
does
not
add
a
trailing
new
line
character,
nor
does
it
strip
the
character
if
it
exists,
it
kind
of
just
leaves
the
file,
as
is
the
web.
Ide
does
add
the
new
line
character
and
you
can
override
that
behavior
by
creating
an
editor,
config
file
and
storing
that,
in
your
repository
since
the
single
file,
editor
doesn't
respect
that
editor
config
file.
A
We
wouldn't
want
to
change
the
default
behavior
or
you
might
get
into
a
situation
where
you
are
unable
to
remove
a
new
line
character
if
that's
actually
what
you
wanted.
So
our
solution,
instead
of
changing
the
behavior
of
one
or
the
other,
was
to
build
in
a
an
extension
to
editor
light,
which
I
just
got
through
explaining.
It
will
now
be
a
shared
editing,
experience
across
snippets
web
ide
and
single
file
editor
to
pull
information
from
the
editor
config
file
and
give
you
a
consistent,
customized
editing
experience
across
all
those
categories.
A
Moving
on
to
the
navigation
and
settings
work
right
into
that,
there's
a
an
issue
that
we
just
validated
with
some
research
that
we
we've
saw
some
improvements
in
clarity
and
efficiency
when
it
came
to
interacting
with
the
user
menu.
So
that's
the
the
menu
in
the
top
right
here
when
you
click
on
your
little
avatar.
A
There's
a
few
places
that
look
like
links
that
aren't
links,
there's
a
few
things
that
could
be
named
differently
fairly
small
changes,
but
fairly
dramatic
improvements
in
in
navigating
around
your
user
profile.
So
we'll
be
picking
that
up
in
thirteen
nine,
and
you
can
see
the
proposed
changes
here,
where
your
name
and
your
your
handle
are
linking
to
your
profile
page
and
we've
clarified
the
the
links
for
setting
your
status.
Editing
your
profile
and
preferences
here.
A
When
it
comes
to
settings,
gitlab
has
quite
a
few,
and
one
of
the
improvements
that
we
were
hoping
to
make
was
something
we
were
researching
in
13
8
and
we
have
a
proof
of
concept,
actually
live
on
gitlab.com
here,
and
so
I
can
just
demo
it.
We
wanted
to
add
searchable
settings
to
individual
settings
views
so
right
now.
It's
only
implemented
on
the
project
general
view,
but
you
can
see
how
it
works
here.
So
if
I'm
looking
for
merge
requests,
you
can
see
it
starts
to
filter
in
and
highlights
any
applicable
results.
A
Changing
this
path,
for
example,
so
if,
if
I
just
type
in
path
I'll,
be
able
to
highlight
it,
so
this
pattern
we
think,
is
going
to
make
navigating
the
settings
within
git
lab
a
lot
more
efficient.
So
we're
going
to
go
ahead
and
apply
it
to
all
the
settings
pages.
It
is
worth
noting
that
this
is
searching
within
a
single
page
and
will
be
iterating
on
a
on
an
approach
that
could
search
across
multiple
settings,
pages
and
sort
of
globally
search
settings
values,
but
for
now
they're
scoped
to
the
page
that
they're
on.
A
So
we
have
an
epic
actually
three
epics
for
the
admin
settings
group
and
project
settings
and
user
settings
each
one
of
those
has
individual
issues
for
the
views
that
we
want
to
implement
the
search
across
they're,
all
very
straightforward.
We
hope
to
get
as
many
of
these
done
as
possible
in
13.9
and
turn
on
that
feature
flag.
So
everybody
can
start
using
the
search
bar
in
their
settings.
A
Experience
and
last
this
won't
ship
in
thirteen
nine,
but
likely
some
work
that
we'll
be
doing
in
1310
that
I
wanted
to
highlight.
We,
as
I
mentioned,
we
completed
some
some
validations
and
research
that
related
to
settings
and
navigation,
and
the
outcome
of
that
was
that
we
we
validated
that
an
approach
for
consolidated
top
navigation
experience
is
something
that
we
want
to
move
forward
with.
So
we'll
be
cleaning
up
this
proposal
and
working
on
issues
in
13.9
to
to
flesh
out
the
direction
and
come
up
with
an
iteration
plan
but
effectively.
A
What
we're
looking
at
here
is
a
single
navigation
item
on
the
top
nav
that
combines
your
projects,
groups
and
then
what
we
have
in
the
more
menu
is
is
brought
into
that
as
well,
and
the
behavior
is
very
similar,
but
it's
all
under
one
place
and
it
makes
it
a
lot
easier
to
navigate
between
projects
and
groups.
It
brings
visibility
to
these
instance.
Level
features
like
operations
and
security,
and
it
sets
us
up
for
a
much
more
flexible
future,
as
we
add
more
features
and
and
functionality
to
this
menu.
A
So
looking
forward
to
that
I'll
talk
more
about
that
in
the
1310
kickoff.
But
that
is
something
we're
very
excited
about
and
with
that
we
are
going
to
wrap
this
kickoff
video.
But
please
feel
free
to
visit
the
planning
issue.
Look
at
the
individual
issues
that
we
have
on
the
release
board
comment.
Give
me
feedback,
ask
questions
and
I'll
see
you
all
next
month
for
the
1310
kickoff.