►
From YouTube: GitLab 13.3 Kickoff - Create:Editor
Description
Details on the upcoming GitLab 13.3 Release from the Create:Editor group.
Snippets with Multiple Files: https://gitlab.com/groups/gitlab-org/-/epics/2829
Custom JSON Schema in the Web IDE: https://gitlab.com/gitlab-org/gitlab/-/issues/226982
Publishing GitLab Workflow to Open VSX: https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/205
If you have feedback you'd like to provide on how you use the Web Editor or the Web IDE, please don't hesitate to reach out to me via https://calendly.com/gitlabkai
A
Hi,
my
name
is
kai
armstrong,
I'm
the
product
manager
for
the
editor
group
and
the
create
stage
here
at
gitlab,
and
I'm
here
today
to
talk
about
the
upcoming
gitlab
13.3
release
and
what
the
editor
group
will
be
working
on.
So
I'm
going
to
share
my
screen,
we'll
step
through
a
few
things
and
then
I'll
make
sure
that
we've
got
some
notes
down
below
this
video
and
if
you've
got
any
questions
or
feedback.
Always
please
feel
free
to
reach
out
to
me.
So,
let's
get
started
here,
kicking
it
off.
A
You'll
notice,
there's
quite
a
few
things
in
the
board.
A
lot
of
this
is
sort
of
multiple
steps
in
a
continued
work
stream
that
we've
talked
about
many
times
before
and
then
there's
some
new
things
that
I
wanted
to
highlight
here.
So
first
thing
we'll
talk
about
is
snippets
with
multiple
files.
The
team
is
continuing
to
burn
through
and
work
down
on
snippets
with
multiple
files.
A
The
back-end
work
to
enable
this
a
lot
of
that
work
has
progressed
and
we're
in
a
really
good
spot.
The
front-end
work
there's
a
lot
more
front-end,
that's
going
into
this,
and
so
it's
taking
some
more
time
to
get
through
and
we're
working
through
that.
What
we'll
be
focusing
on
in
13.3
is
allowing
you
to
add
and
remove
snippet
files
from
the
edit
view.
So
when
you're
editing
snippets,
we
will
now
have
multiple
files
and
so
you'll
need
a
mechanism
to
add
an
additional
file
and
delete
those
files.
A
One
of
the
other
things
I'm
really
excited
about
that
we're
working
on
in
13
3
is
support
for
custom.
Json
schema
validation
in
the
web
id.
So
in
13.2
we
will
be
releasing
gitlab
ci
based
schema
validation
in
the
web
id.
So,
if
you're
editing
editing
a
gitlabci.yaml
file,
we'll
provide
some
feedback,
while
you
edit
that
file
about
different
configurations
that
may
or
may
not
be
correct
or
will
help
you
auto
complete
those
things.
A
We'll
now
have
a
list
of
sort
of
the
dictionary
words
that
you
might
use
to
complete
those
things
which
is
great
when
you're
editing
that
what
we
want
to
do
is
we
want
to
take
this
sort
of
ability
to
create
a
map
or
schema
file
for
a
bunch
of
different
files
and
and
layer
that
in
and
let
people
customize
and
extend
it
to
their
project
and
their
use
cases,
and
so
we'll
be
implementing
a
way
to
add
a
custom
schema
in
13.3
you'll,
be
able
to
we'll
define
this
in
a
the
gitlab
web
id
yaml
file
and
you'll
define
a
where
the
scheme
is
located,
so
a
path
to
schema
and
then
sort
of
what
the
match
is
for
files
that
that
schema
should
be
applied
to
you'll
notice.
A
Most
of
the
examples
here
for
the
release
post
will
actually
be
immediately
using
this
for
the
release
post.
One
of
my
colleagues
has
already
developed
a
schema
file
for
that
and
so
we'll
be
able
to
prototype
and
do
this
for
our
own
phone
things
very
quickly
as
well,
so
really
excited
about
this
one.
A
The
last
one
that
I
want
to
talk
about
is
our
vs
code
extension,
so
git
lab
recently
took
over
ownership
of
the
gitlab
workflow
via
code
extension.
We've
been
publishing,
updates
to
that
as
we've
gotten.
Some
things
in
order
moved
over
the
publisher
accounts
released
version
3,
which
included
a
number
of
fixes,
some
other
bugs-
and
you
know
minor
things
that
we've
been
working
on
and
one
of
the
requests
that
we
want
to
take
a
look
at
is
publishing
the
extension
to
the
openvsx
registry.
A
So
openvsx
registry
is
a
registry
that
is
exists
for
sort
of
vs
code-like
alternatives,
so
like
vs
codium,
which
is
a
completely
free
and
open
source
version
of
vs
code
built
from
source
and
then
there's
other
things
like
theia,
which
is
a
sort
of
vs
code,
web-based
alternative,
there's
code
server
and
other
things
that
leverage
this
openvsx
registry
to
get
vs
code
extensions
inside
of
those
editing
environments,
and
so
we're
going
to
enable
the
gitlab
workflow
extension
to
be
published,
though
so
that
way
we
support
sort
of
all
these
users
across
the
board.
A
So
we're
really
excited
to
you
know,
have
taken
over
the
extension
and
then
getting
it
out
to
more
users.
So
that
way,
more
users
can
benefit
from
all
the
great
things
in
there.
While
we
continue
to
sort
of
do
everything
that
we
want
to
do
to
make
the
extension
better
overall
so
really
excited
about
this
one
as
well.