►
From YouTube: UI to Code monthly meeting: 03/29/23
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
so
I
guess
I'm
doing
the
intro
to
this
is
the
UI
to
code
meeting
or
what's
today,
March
11th
2023.
A
So
the
point
that
I
have
is
that
we
should
stop
using
the
data
prop
that
we're
using
for
our
components.
I
think
we
can
all
agree:
oh
yeah,
29,
sorry,
March
29th,
but
yeah
I
think
we
can
all
agree
that
the
data
prop
is
not
great
or
our
components
since
it
obscures
what
the
component
is
expecting
and.
A
A
So,
for
example,
this
component
that
I
was
working
on
yesterday.
It's
the
agenda
for
the
new
CD
events
or
the
world
tour,
and
here
you
can
see
it
expects
a
complex
object.
So
if
we
use
the
data
prop,
we
would
have
to
go
either
through
the
template
or
go
to
the
yaml
file
and
see
what
we're
passing
to
for
the
component
and
how
we
can
use
it.
A
Also
with
the
interface
intellescence
works
much
better.
So
if
I
come
for
example,
here
with
both
autocomplete,
what
whatever?
Oh
just
when
I
want
to
show
it.
A
It
had
been
working
with
it
does
not
a
complete
you'll
have
to
trust
me
and-
and
it
shows
you
the
options
that
you
have
based
on
whatever
you
declared
here
in
the
interface.
A
It
also
works
with
great
when
looping
through
something
so,
for
example,
here
I'm
looping
through
the
events
in
the
agenda
and
the
items
that
go
through
the
loop
will
also
support
the
autocomplete,
so
yeah
I
think
it's
just
such
an
improvement
and
the
way
we're
doing
it
right
now
is
we're
just
saying
passing
the
data
we're
doing
data
and
whatever
comes
from
the
ammo
file,
but
we
can
do
basically
the
same
with
bevind.
A
We
can
spread
the
props,
and
this
will
make
it
so
that
every
property
in
this
object
is
a
separate
prop
or
the
component.
So
we
don't
have
to
pass
manually,
separate
props
and
for
those
pages
that
we
already
have
like
this
setup,
for
example
Solutions,
where
we
have
this
setup
where
just
pass
data
like
this,
we
can
also
use
B,
bind
and
pass
the
same
data
so,
for
example,
you're,
rebind
and
component.data,
and
then
for
whatever
component
that
comes
in
this
template
that
uses
the
data
prop.
A
It
will
have
it
and
then,
whatever
new
component
we
create
that
does
have
separate
props.
It
will
use
the
prop
spread.
Also,
we
can
export
interfaces
and
share
them
across
components,
so
I
created
this
file.
Interfaces
just
have
one
right
now,
because
I
need
to
use
the
breadcrumbs
and
we
can
import
this
cross
components
so
that
we
don't
have
to
declare
them
over
and
over.
So
it's
not
big
changes,
I
think,
but
it
can
be
a
big
Improvement
for
us.
B
I,
don't
have
any
objections.
I've
you've
talked
to
me
a
little
bit
about
this
and
I've
been
doing
this
myself
and
I
do
find
it
to
be
an
improvement.
It
also
kind
of
leads
to
better,
like
type
checking
for
data
files
in
general,
so
that,
like
you,
can't
just
pass
it
like
whatever
and
it'll
just
be
like
sure
like
we'll
just
take
that
and
ingest
that
right
up
and
have
your
templates
like
just
fail
so
yeah
I'm
in
favor
of
that
change,.
C
Actually,
that's
kind
of
an
interesting
point
of
like
I,
like
it
too,
as
people
other
teams
make
changes
to
Pages
if
they
like
change
our
yaml
files
into
such
a
data
structure
that
it
won't
render
properly
do
you
know
how
it
looks
when
it
kind
of
errors
out
or
what
people
would
see
like
I
assume
pipeline
would
fail
and
blank
pages.
You
know
that
sort
of
thing.
A
A
For
example,
here
so
all
right,
so
I'm
using
an
image
somewhere
around
here
there.
So
let
me
see
an
image
and
I
have
already
declared
this
enter
interface,
so
it
comes
optional.
Prop
then
image
and
then
the
search
is
a
string,
so
we
as
devs
this
mostly
improves
our
Dev
experience.
So
if
I
just
remove
this,
it
will
immediately
know
that
something's
wrong.
Let
us
know
before
we
get
to
the
point
where
that
would
be
a
problem.
A
I
think
the.
If
the
content
changes
we
would
still
have
to
handle
the
error
ourselves
like
have,
for
example
this.
If
this
speaker
does
not
come,
then
don't
render
this,
but
it
will
also
show
this,
for
example,
so
I
remove
this,
and
it
will
show
the
warning
like
this
my.com
over
here,
because
it
is
declared
as
an
optional
rub
here
in
the
interface.
So
we'll
throw
the
warning
like
be
careful,
they
might
not
pass
this
and
it
will
break
that's
how
it
will
help
us
I.
Think.
B
Well,
I
have
the
next
Point
pretty
much
all
of
this.
What
I'm
talking
about
here
is
just
like
trying
to
Not
Duplicate
ammo
content
between
like
a
root,
index.yaml
page
and
their
child
pages,
and
so
that's
like
pretty
much
talking
about
like
for
some
of
these
ammo
files.
They've
been
like
in
place
since,
like
essentially
from
WWW,
where
we've
inherited
them
somehow
or
they've,
existed
in
processes
that
have
existed
before
our
team,
and
so
what
I'm
suggesting
is
that
we
use
like
the
content
module
to
treat
the
content
within
our
Repository.
B
More
API,
like
so
essentially,
for
example,
like
what
I'm,
showing
in
the
Mr
that's
different
from
what
we've
done
before.
Is
that
we're
querying
for
all
of
the
content
of
the
child
pages
and
then
calling
the
content
that
we
need,
and
so
then,
like,
for
instance,
that
like
for
you,
know
I'm
reworking
on
trying
to
do
the
topics
pages,
and
so
then
are
the
topics
like
header
page,
and
so
then.
B
What
needs
to
be
shown
is
like
the
actual
topics
pages
that
list
out
to
all
of
the
pages
and
instead
of
having
a
yaml
file.
That
says,
like
hey
here,
are
the
existing
topics
pages
that
exist,
that
are
child
pages,
that
link
out
to
this
and
that
what
we
would
do
is
we
would
look
at
the
content
directory
look
at
all
of
the
child's
Pages
there
and
then
pull
all
of
that
all
all
of
the
titles
and
the
URLs
for
that
stuff.
There.
Essentially
it's
like
not
having
to
have
stakeholders
duplicate.
B
B
Another
aspect
of
of
that
is
also
like
the
stakeholders,
because
a
lot
of
the
stakeholders
are
the
ones
who
are
actually
updating
the
ammo
files
and
making
sure
that,
like
those
sorts
of
changes,
work
for
them
and
that
they're
like
a
line
that
that
would
be
helpful
to
them
in
some
way.
So
they
don't
have
to
update
multiple
spots
and
also
keeping
them
in
the
loop
that,
like
hey,
like
we're,
removing
this.
But
that's
because
you
know
you
shouldn't
need
to
update
multiple
things
at
once
anymore,
yada,
yada
yeah.
B
That
was
just
something
as
I
was
like
working
with.
That
thought
could
be
good
for
us
as
a
team
to
like
try
to
be
like
more
aware
about
and
like
realizing
that
we
can
do
that,
because
that's
something
that,
like
kind
of
for
me
personally,
I
started
to
like
put
so
and
so
together
that
we
can
like
use
like
their
next
Tools
in
that
way,
to
help
us
make
the
site
better
and
so
I
just
wanted
to
call
it
out.
B
D
There's
nothing
else:
I'll
jump
in
I
was
wondering
if
Megan
could
just
talk
a
bit
about
the
blocker
or
moving
the
product
form
onto
the
marketing
page,
because
I
wasn't
quite
sure
the
specifics
of
it
yeah.
So
for
context.
We
were
building
like
a
new
free
trial
page
and
it
would
be
ideal
to
have
that
form
live
on
our
marketing
site.
D
D
And
this
is
the
the
product
page
and
like
in
code,
you
can
see
where
this
form
is
it's
posting
or
sending
data
to
whatever
this
is
their
API,
that
I
assume
lives
in
the
product.
It
wasn't
easy
for
me
to
find
where
this
form
was
in
the
product
code.
There's
no
fancy
abuse
source
button,
because
I
didn't
get
a
chance
to
look
at
it
too
closely,
but
just
like
everything
else
in
the
product,
I
have
a
feeling
it's
built
in,
like
Ruby
or
Ruby
on
Rails
or
a
combination
of
things
like
that.
D
So
it's
not
easily
like
cut
and
paste
onto
our
site,
just
kind
of
glancing
through
this
there's
like
hidden
fields
that
I
assume
there's
some
kind
of
logic.
That's
I
think
like
making
these
tokens.
D
If
all
of
that
was
in
the
product
and
I,
think
for
us
to
just
like
copy
and
paste,
it
isn't
possible.
I
think
we
have
to
make
our
own
solution
rather
like
the
chatting
with
Justin
before
and
even
if
we
have
something.
You
know
this
page
might
change,
but
where
you
enter
your
email
here
and
by
clicking
it,
you
are
taken
to
that
form
in
your
email
or
name,
it's
filled
out
already.
D
You
just
have
to
fill
out
the
rest
of
it,
just
like
some
kind
of
like
bait
I
hate
to
use
that
word,
but,
like
start
filling
up
the
form
on
on
our
landing
page,
and
it's
like
a
seamless
experience
that
transfers
you
to
the
next
step
in
the
in
the
form
which
might
live
on
the
product,
but
it
was
like
so
fast
I.
Don't
know
well
for
us
to
make
a
form
like
that.
D
We
should
definitely
I
think
maybe
just
a
game
changer
to
to
have
something
like
that
on
our
on
our
site.
But
it's
going
to
take
some
time
and
collaboration
with
I
know
Gail
from
the
growth
team.
Had
some
interest
in
this
and
I
assume
some
some
product
teams,
but
if
we
had
some
time
to
kind
of
scope
out
a
project
like
this
man,
we
could
achieve
so
much
with
this
living
on
our
side.
A
We
tried
looking
for
a
way
to
get
the
field
information
and
then
control
the
form
on
our
site,
because
we
saw
that
Marketo
does
have
like
a
submit
method
that
we
could
use.
It
just
expect
the
object.
So
if
we
can
build
that
object,
we
can
theoretically
build
our
forums
and
control
them,
but
we
couldn't
find
a
way
to
get
all
the
info
we
needed
or
to
create
the
form
just
from
the
form
ID
that
we
get.
D
It's
interesting
I'm,
not
sure
if
Marketo
has
anything
to
do
with
the
product
form,
it's
like
the
sign
up
form
itself,
but
on
the
topic
of
like
making
kind
of
like
a
an
initial
form
on
our
side
that
collects
just
initial
data.
I
wonder
if
we
could
use
Marketo
for
something
like
that
and
who
knows
what
the
what
product
API
is
doing
like?
D
Is
it
doing
something
like
we're
pinging
it
with
the
form
data
to
the
product?
Is
it
doing
something
in
Salesforce?
Is
it
doing
something
in
some
tools?
I'm,
not
even
aware
of,
and
it's
I,
don't
think
we
could
just
make
a
post
request
to
the
product
API
from
our
site
just
for
security
reasons,
but
yeah
I,
wonder
that
would
be
pretty
cool
if
we
could
use
Marketo
to
do
some
kind
of
like
middle
middleman
between
the
two.
B
On
the
topic
of
rendering
funds
in
Marketo,
I
can
talk
a
little
bit
about
what
we
ran
into
so
there's
a
the
market.
Api
has
a
couple
endpoints
one
is
for
getting
like
the
form
fields
that
exist
so
it'd,
be
like
the
name
like
last
name
like
email
get
all
of
that
stuff.
B
Another
API
form
that
they
have
is
just
give
me
a
Marketo
form.
That's
pretty
styled
that
gives
me.
You
know
the
form
itself
and
it'll
return
a
Dom
element
with
all
of
that
information.
That's
what
we've
been
using
for
rendering
our
forms.
That's
why
we
have
like
all
of
these
like
crazy.
You
know
CSS
overrides
and
all
this
shindig
to
try
to
like
make
it
better.
They
don't
have
any
other
API
endpoint
to
grab
all
of
the
data.
B
If
we
wanted
to
go
that
direction
in
having
like
a
custom,
Marketo
form
on
our
site,
like
that's
what
that
would
take
unless
there's
another
API
endpoint
that
we're
not
aware
of
but
according
to
their
docs,
that
was
what
we
ran
into
things
that
starts
to
become
trouble
is
like
in
particular
like
where
you're
talking
about
like
location,
so
like
country
and
like
State
I,
know,
there's
like
a
lot
of
work
on
there
and
to
you
know,
keep
up
to
date
like
we
don't
do
like
China
and
Russia
and
all
that
stuff.
B
So
it's
like
there's
like
some
privacy
stuff
there
and
like
I,
don't
I
don't
want
to
yeah
anything,
that's
a
drop
down
essentially,
and
that's
I'm
sure
it's
own
Rabbit
Hole.
So,
but
if,
if
we
wanted
to
go
that
direction
of
rendering
our
own
Marketo
forms
like,
we
I
think
we
technically
could.
If
we
wanted
to
I,
don't
know
what
it
would
take
from
our
side,
but
I
think
we
like
it's
possible
I,
don't
know
how
like
how
well
that
would
work,
but
it
could
work.
E
You're
given
Marcato
a
little
too
much
credit,
they're
they're,
so
bad,
yes,
there's
there
is
a
paying
points.
If
you,
if
you
have
access
to
like
the
actual
dashboard,
you
can
get
op
tokens
and
you
can
actually
create
custom
forms
that
ping
their
bring
this
up.
They
don't
have
that
documentation
public.
You
have
to
have
like
a
login,
it's
like
the
login
version
of
that.
So
all
that
is
possible.
E
E
What
makes
Marketo
really
nice
for
certain
people
is
the
whole
CMS
aspect
of
it
is
that
when
they
want
to
add
a
new
field,
they
just
do
it
on
the
back
end
and
when
they
hit
submit,
like
you
know,
the
Dom
element's
already
updated
like
we
don't
have
to
do
anything,
so
we
wouldn't
want
to
have
to
be
in
the
the
business
of
like
creating
all
these
forms
every
single
time
they
want
to
make
an
update
or
do
something
we
had
to
like
update
all
the
forms
across
our
site.
E
It
would
just
be
like
one
form
that
doesn't
change,
maybe
does
that
the
here's
your
email
hit
submit
and
then
it
goes
to
another
pipeline
process,
but
like
that
might
be
something
we
could
do,
but
totally
is
doable,
not
a
super
pain
in
the
ass.
It's
actually
relatively
okay,
but
it
that's
something
you
need
to
take
it
in
account
like
we
wouldn't
want
to
build
something.
D
I
want
to
mention
to
I,
don't
know
if
it
was
just
like
a
nice
to
have
on
the
on
the
design
itself,
or
we
actually
use
this
elsewhere,
but
just
I
know
on
the
assignment
form
we
had
signing
with
Google
and
GitHub.
That
would
be
really
cool
to
have
too.
D
Even
if
we
we
have
like
a
sign
up
form
Solution
on
our
site
and
like
the
second
iteration,
it
could
be
adding
like
oauth
I,
think
that
would
be
really
cool
for
us
to
investigate,
adding
to
our
marketing
site,
not
sure
how
gaming
Keys
like
that
works
like
procuring.
Something
like
that
for
us
and
how
the
security
stuff
works,
but
I
think
adding
like
a
sign
in
via
Google
would
also
just
be
a
experience.
Enhancer.
D
That's
the
tricky
part
I'm,
not
100
sure,
but
if
you
go
to
just
like
their
main
sign
on
I,
think
it's
Google
and
GitHub.
But
then,
if
you
like
from
like
to
sign
up
rather
than
if
you
go
to
sign
in
later,
they
have
like
six
options.
So
I
don't
know
how
you
get
to
some
of
those,
but
I
do
know
they're
in
some
way
available.
E
E
Theoretically,
like
we
could
post
that,
but
they
would
have
to
modify
their
security
parameters
in
rails
to
allow
that
to
happen,
and
then
theoretically,
we
could
just
create
like
a
basic
form
post
it
there,
and
it
should
shed
quite
about
work.
But
rails
has
like
a
lot
of
security
in
inherently
built
into
it.
That
tries
to
like
not
let
that
happen
and
I.
Think
that's
the
bigger
thing
too.
C
Yeah
I
haven't
looked
at
that
form
in
ages,
but
I
know
that,
like
depending
on
yeah,
if
we
were
able
to
use
the
post
method
to
send
all
of
that
data
directly
to
wherever
gitlabs
currently
sending
it
like.
I,
don't
know
if
we
also
collect
like
personally
identifiable
information,
and
you
know
credit
card
data
and
being
compliant
and
all
of
that
sort
of
stuff.
We
don't
want
to
own
that
I
mean.
C
E
E
D
And
anytime
I
hit
the
continue
with
SAS
button
and
it
takes
me
to
the
free
trial
sign
up
page.
It
knows
my
first
name
last
name
company,
it's
not
in
the
URL,
so
like
they're
grabbing
that
from
something
so
I
feel
like
you
should
be
able
to
play
off
that
isn't
happening
even
if
you
go
like
incognito
or
is
it
just
because.
D
A
D
Now
I
see
the
register
of
Google
and
GitHub
completely
different
screen
than
if
I'm
not
incognito,.