►
From YouTube: WG Component Standard Office Hours 20200728
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
Okay,
okay,
good
morning,
everyone
welcome
to
the
tuesday
july
28
2020
working
group
component
centered
office
hours.
This
is
our
hour
for
folks
to
drop
in
and
ask
questions
and
get
help
with
what
they're
working
on
all
right.
I
mean.
How
can
I
help
you.
A
Awesome,
let's
take
a
look.
Let
me
give
you
co-host,
you
can
share
your
screen
here,
okay
and
then,
of
course,
the
reminder
close
any
tabs
or
anything
that
you
might
not
want
on
the
recording.
A
It
should
be
like
a
green
button
right
in
the
middle
of
the
bottom
right.
New
yeah.
B
B
So
I'm
gonna
start
with
the
function
that
does
all
the
magic
I
think's
the
best
place
to
start
with
this
pr,
okay,
so
the
idea
of
having
the
instance
the
internal
values
working
now
we
have
the
dynamic
serialization
after
the
config
file
loading,
okay
and
then
we
start
with
the
internal
configuration.
A
A
Okay,
so
then
we
load
the
instance
configuration
with
the
so
okay.
So
we
we
can.
I
think
what
we
said
we
were
gonna.
Do
we
can
we're
gonna
construct
an
instance
configuration
we're
gonna
copy,
any
duplicate
values
from
the
shared
into
the
instance,
then
we're
gonna
unmarshal
the
file
into
the
instance
that
we
just
defaulted
based
on
those
duplicate
values
and
then
we're
going
to
copy
the
duplicate
values
back
over
the
shared.
Is
that
right,
exactly
okay,
great,
let's
walk
through
it's.
B
So
here
I
have
the
generate
external
config.
We
can
change
the
names
later
but
sure
the
idea
is
to
start
with
the
external
and
get
this
internal
one
and
convert
the
external,
the
internal
to
external.
A
Okay,
so
this
is
going
from,
I
think
we
want
we
we
just.
We
could
just
do
two
two
separate
internal
types
right.
We
don't
need
to.
A
A
A
A
B
B
B
Now
we
convert
them
back
in
the
internal
both
sides
and
do
the
cubelet
config
flag,
precedence,
merge
this
configuration.
That's
the
real
merger
of
the
internal
got
it
because
they're
merging
the
instance
configuration
into
the
sharing,
so
they
have
the
same
values
and
then
apply
the
right
feature.
The
future
gates,
yeah,
okay,
they're.
A
Okay,
I
think
that
looks
pretty
good.
I
guess
the
only
question
I
had
was
why
we
have
to
go
through
the
external
to
get
the
def
like
we
could,
because
what
we
could
do.
A
I
think
the
advantage
of
that
is,
it's
maybe
a
little
simpler
from
an
implementation
perspective,
because
we
don't
need
to
re-implement
that
external
merge
every
time
a
version
changes,
but
the
disadvantage
of
it
is
that,
if
like
for
some
reason,
we
wanted
to
change
how
values
were
merged
between
them
in
a
future
api
version
like
we
would
have
to
go
back
to
what
you
just
did
here.
That's
said
like
today,
I
don't
see
any
merge
behavior.
A
B
B
Yeah
right,
so
this
value
here
needs
to
be
copied
to
the
instance
one
so
when
we
load
the
config
file
instance,
if
we
don't
have
anything
here,
it's
just
get
this
value.
A
We
can
what,
if
we
lo
so
load
load,
config
instance
file
is
just
like
load
like
load,
the
other
loader
right,
so
it
returns
an
internal
type.
It
returns.
B
An
external
type
for
this
case:
okay-
and
it
gets
this
object
and
gets
all
the
the
values
from
this
object
and
dumps
from
from
the
external
types,
okay
yeah.
So
we
are
copying
the
values
from
the
sharing.
This
way,
you
can
marshal
the
the
file
on
top
of
the
shared
values,
yeah.
A
You're
right
because
we'd
have
to
go
okay,
so
we
would
have
to
if
we
wanted
the
merges
to
only
be
on
internal
we'd
have
to
construct
the
instance
external
default.
It
convert
it
to
the
internal
copy,
the
val,
the
duplicate
values
over
the
internal
then
reconvert
it
back
to
the
external
so
that
we
can
unmarshal
on
top
of
it
and
then
re-default
it
yeah.
So
it
gets
super
complicated,
either
way
so
yeah.
This
is,
I
guess
this
is
probably
fine.
A
I'll,
probably
like
take
a
look
at
it
and
try
to
think
through.
You
know
different
edge
cases
of
it,
but
yeah
this.
I
think
this
will
be
roughly
roughly
equivalent
in
complexity.
B
Okay,
I
have
set
up
some
initial
tests
for
this
function,
with
the
possible
combinations
that
we
expect
like
which
did
the
four
values
in
both
instances
and
overwrite
with
flags
and
passing
a
shared
address
from
the
file,
and
you
we
set
analyze.
This
file
cool
goes
on
with
some
some
combinations.
Probably
I'm
missing
something,
but
most
of
them
are
here.
A
Cool,
it's
super
exciting,
to
see
this
coming
together.
Did
you
have
any
other
questions
while
you
were
implementing
it?
No
every
other
suggestion
was
working
great
all
right.
Well,
I
need
I
need
to
take
some
time
to
give
you
a
real
review,
then,
and
then
maybe,
let's
sync
up,
I
can
get
that
done
sometime
this
week
and
then,
let's
sync
up
next
week
on
that
and
then
hopefully
I
think
you
know
we
get
everything
sort
of
ship
shape
and
then
we
can
go
update.
A
The
cap
use
this
as
the
example
get
the
ket
merged
and
get
this
merged.
B
A
That's
a
good
idea.
I
would
probably
do
a
separate
pr
for
that.
Q
proxy
is
very
different.
Yeah
yeah.
B
B
Maybe
the
other
part
of
this
could
be
bring
some
meat
to
eat
this.
B
A
Some
we
can.
We
can
definitely
what
I
would
do
probably
is
update
the
end-to-end
tests
to
start
using
the
instance.
Configuration
file
as
well
and
that'll
give
us
some
signal
that
it's
been
tested
all
the
way
through.
A
A
Cool
yeah
awesome,
so
yeah,
let's
feel
free
to
take
some
time
looking
at
cube
proxy
this
week,
I'll
take
some
time
to
review
this
this
week
and
then
we'll
sync
up
next
week.