►
Description
In this session we pair up in replacing an existing component to use gl-form-fields.
00:00:00 - Intro talking about gl-form-fields and possible usage in Achievements
00:05:45 - Start working on admin_emails_form.vue
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119789
B
So
now
we've
got
geoform
filled,
so
I'm
hoping
we
can
create
a
a
cruddy
form
or
crowd
forms
for
achievements,
no
SNES,
but
because
achievements
hasn't
got
a
UI.
Yet
we
we
need
something
real
basic.
That
start
with
some
I.
Don't
know
what
you
want
to
call
it.
An
entry
point
amount
points,
something
like
that.
So
it's
sort
of
almost
Unleashed
another
can
of
worms
would
have
kind
of
like
okay.
So
to
get
us
something
to.
B
B
B
D
These
boys
are
played
between
rails
and
view
is
really
something
that
at
least
myself.
It
puts
me
off
when
I
am
starting
a
project.
Oh
I
am
very
lazy
to
a
star,
because
I
know
all
these
type
of
things
that
I
I
would
like
to
to
dump
directly
interview.
But
I
I
had
to
do
this
between
brothers
and
you.
B
B
Able
to
start
building
a
new
view
component.
If
we
find
it's
going
to
be
a
bit
a
bit
more
long-winded
than
I
expected
it
to.
We
can
either
cheat
and
we
can
just
mount
a
few
components
somewhere
where
it
completely
doesn't
belong,
or
you
can
or
maybe
divert
on
something
else
that
you
want
to
work
on
for
a
wee
bit
while
I
get
this
in
place,
but
I'm
hoping
I'm
hoping
you
know,
we've
got
our
resource.
We've
got
a
controller.
E
B
A
A
Well,
let's
see
it,
let's
see
if
we
can
replace
if,
if
you're
cool
with
it,
let's
see
I
think
Peter
had
somewhere
in
the
code
that
that
was
pretty
simple.
We
could
use
sort
of
try
out
geoform
Fields,
let's
see
if
we
can
replace
existing
form
usage
with
geoform
fields
and
then
I,
don't
think
that'll
take
a
long
time
and
then
we
can
go
back
to
achievements.
Does.
C
C
B
E
A
E
B
A
A
E
E
A
B
B
B
A
B
A
D
B
A
D
B
A
E
A
A
C
A
A
A
E
E
B
A
B
A
A
C
B
B
F
A
F
B
D
A
E
E
F
C
E
A
C
A
B
A
B
D
A
F
A
A
A
F
As
far
as
I'm
aware,
the
package.json
only
resolves
like
one
main
entry
point
and
when
we
compile
all
of
gitlab
UI,
it
goes
into
the
disk,
folder
so
I'm
sure
like
importing
gitlab
UI
maps
to
dist
index
yeah.
But
if
we
want
to
import
from
anything
else
in
that
folder,
we
have
to
be
specific.
Oh
nice.
B
A
E
B
A
A
A
C
B
B
A
B
B
B
A
A
I'm,
looking
at
this
yeah
key
is
used
as
both
the
ID
and
name,
but
it
looks
like
we
don't
need
the
ID.
It
says:
that's
just
used
for
the
label
matching
up
the
validation
stuff.
We're
already
we're
we're
handling
state
is
what
we're
handling
yeah.
All
that's
great
I,
think
I
think
we
have
that
so
I
think
we
can
get
rid
of
that
first
form
group.
A
A
B
A
A
Yes,
thank
you
Andrew.
We
need
to
input
the
input
and
blur
the
blurb,
but
those
are
those
are
at
inputs
and
app
blurs
yeah
and
and
Peter
had
an
interesting
idea
of
like
what.
If
we
grouped
the
like
of
States,
we
need
to
bind
and
events
we
need
to
bind
into
rather
than
having
it
all
spread.
In
one
level
we
could
have
like
events
and
States
so
I
could
just
do.
V
bind
state,
Beyond
events
and
that
might
be
kind
of
cool,
sounds.
B
A
B
B
A
A
B
E
A
B
D
C
C
A
F
A
B
A
D
A
B
B
B
D
A
One
thing
we
won't
be
able
to
do
right
now:
is
you
see
how
the
alert
is
before
the
form
group?
That's
not
something
we're
going
to
be
able
to
do,
but
we
could
do
it
inside
the
form
group
and
see
how
that
works
and
try
to
hit
trigger
that
failure,
but
we
should
be
able
to
copy
this
somewhat,
as
is
so,
we
need
another
scope,
slot.
B
D
E
B
C
C
A
A
A
A
E
E
B
C
B
C
B
D
A
E
C
A
C
B
A
B
C
A
A
B
Hopefully
this
video
will
serve
a
really
good
purpose,
but
you
know
maybe
we
some
some
eyes
in
a
little
bit
to
try
and
understand
some
of
the
wires
and
if
there's
any
way,
I
think
it's
unavoidable
when
we're
using
the
slots
that
you
just
have
to.
But
then
you
were
saying
that
you
had
an
idea
of
of
kind
of
lumping
these
together
in
a
sort
of
event,
handlers
and
something
else.
A
B
E
A
A
C
A
A
C
A
E
A
A
And
that's
all
of
our
computers,
I
think
this
is
going
to.
Let
us
remove
a
number,
a
good
amount
of
code
which
I'm
kind
of
excited
about.
It's,
not
that
difficult
of
an
abstraction
for
a
lot
of
code,
removal
that
I'm
really
interested
to
see
how
it
affects
our
tests
too,
because
maybe
it's
also
a
lot
of
test
removal.
F
E
E
A
A
F
A
F
B
E
B
A
C
E
A
E
A
A
C
A
F
A
B
A
B
A
E
A
E
D
A
B
A
A
F
B
D
B
C
B
D
A
A
A
D
A
A
D
F
B
C
F
F
A
A
C
A
C
A
F
A
D
D
F
A
D
B
A
B
A
A
I'm,
almost
wanting
to
like
pass
render
function
like
that
would
be
so
interesting
if
we
did
it
here
instead
of
in
the
time,
but
I
know
that
that
that's
me
thinking
in
react
way
and
we're
not
there.
So
that's
just
something
to
think
about,
but
maybe
we
could
talk
about
in
the
Mr
of
ways.
We
could
make
the
template
a
little
simpler.