►
From YouTube: WG API Expression Bi-Weekly Meeting for 20201013
Description
WG API Expression Bi-Weekly Meeting for 20201013
A
B
B
Yeah
yeah
yeah,
yes,
and
we
don't
know
exactly
what
to
do
for
the
nine
panel
fields,
because
built-in
types
can
differentiate
between
an
unset
field
a
and
a
zero
value
field.
When
it's
another
bino
and
clds
can,
and
they
don't
behave
the
same
way
and
from
the
open
api.
We
don't
know
if
it's
a
9.0
or
not.
B
B
A
A
Well,
I,
while
I
have
it
here
from
from
last
music,
we
discussed
how
to
continue
with
telescoping
and
I
I
started
a
document
and
I'm
still
trying
to
to
figure
out
what
I
did
over
the
last
half
year
and
what
we
decided
was
bad
and
why
we
got
stuck
on
those
I'm
pulling
it
apart.
I'm
doing
a
document
right
now
that
I
explained
the
problem
again
and
I'm
I'm
pulling
apart
the
I
think
four
pr's.
C
A
Yeah,
I
I
think
everybody
saw
it.
I
created
this
document
and
there's
not
much
in
it
right
now,
just
a
few
things
we
we
discussed,
I
don't
know
if
we
should
go
over
it
now
and
add
stuff
we
discussed
or
if
we
should
make
a
dedicated
meeting
for
it,
whatever
you
prefer
like
how
we
or
we
just
update
it
as
synchronously
everybody
looks
at
it.
I
think
you
had
some
talks
on
the
side
about
it.
B
A
E
A
A
A
A
B
B
B
C
Hey,
yes,
I
did
some
progress
there
right
now.
I'm
gonna
try
to
solve
this
with
the
default
field
manager
and
using
the
field
manager
of
the
main
resource
to
try
and
change
the
match
field,
but
yeah
there
might
be
other
solution
possible
like
this
is
just
one
of
them
so
happy
to
get
start
a
conversation
there.
B
Thank
you
so
much
for
doing
that.
Andrea
is.
We
need
to
look
at
how
is
the
field
manager
world
and
how
is
the
subresource
created
so
that
we
can
wire
the
proper
field
manager
in
there,
because
I
don't
think
we'll
ever
need
to
use
the
scale
the
scale
manager,
because
it's
pointless,
we
don't
actually
operate
on
the
scale
objects.
B
B
Yes,
yeah,
I
think
it's
very
useful
that
you
post
these
code
links
and
we
can
look
at
it
and
comment
on
these.
I
think
it's
working
very
well
and
you
don't
have
to
make
the
change
if
you
suspect
you
want
to
make
a
specific
change,
feel
free
to
just
send
a
link
and
say
I'm
planning
to
change
that.
So
I
think
this
is
where
we
need
to
make
the
change.
We
can
also
comment
on
that
and
I
think
it's
very
useful.
Thank
you.
A
F
B
B
A
A
E
Yeah,
oh,
hey,
so
I've
got
a
working
prototype
of
the
generated
client
in
kidsgates
and
I
think
when
I
I
wanted
to
do
a
couple
other
detailing
on
it,
and
then
I
I
think
it's
probably
makes
sense
for
me
to
go
sync
up
with
go
to
like
a
coup
builder
or
controller
runtime
meeting
and
start
to
show
it
to
people.
I
also
think
I
should
just
take
one
of
the
small
controllers
and
just
go
over
to
show
that
happening.
E
So
I'm
going
to
keep
working
on
that
you'll
probably
hear
more
from
me
about.
It
was
kind
of
heads
down
just
keeping
it
working
initially,
but
I
think
I'll
transition
over
and
start
making
a
little
more
noise.
I
actually
need
to
start
writing
a
cap
at
some
point.
We're
obviously
not
going
to
do
it
for
this
cycle,
but
for
the
next
cycle.
I
think
I'd
like
to
come
out.
B
E
E
There
was
another
issue
that
was
open,
trying
to
make
some
kind
of
change
that
could
have
picked
this
up,
so
I
made
sure
that
they
knew
that
this
was
available
now
yeah,
but
that's
kind
of
I'm
going
to
kind
of
let
them
on
their
own.
At
this
point
they
weren't
very
responsive
to
stuff
on
their
pr.
So
if
they
drop
their
pr,
then.
B
B
A
B
B
Later
no,
but
my
fix
is
different.
My
fix
is
that
I
mean
possibly
it
would
fix
that,
but
it's
kind
of
odd,
but
my
fix
would
change
if
you
have
a
quantity,
for
example,
which
is
canonicalized
in
a
different
form,
so
the
600
would
become
600
m
or
something,
and
it
would
become
a
string
because
of
the
quantity
becoming
a
string
when
it's
canonicalized,
and
here
it
it
doesn't
even
do
that
the
number
stays
a
number
and
when
you
get
the
results
from
the
api
server,
you
have
the
exact
same
thing.
A
B
A
A
G
Is
yeah
go
ahead?
Sully!
Is
this
strictly
true,
according
to
the
code
of
so
like
this
came
up
in
controller
runtime
or
on
controller
tools
rather,
and
it
was
pointed
out
that
quantity
is
not
in
fact,
an
entry
string.
Quantity
is
an
inter
string
or
float
like
code
for
parsing
quantity
accepts
float
as
well,
and
then
normalizes
the
float
before
it
gets
parsed,
which
is
the
only
way
that
it
can
be
valid
asterisk.
G
B
G
Yeah
not
that
I
wouldn't
rather
improve
this,
and
I
think
this
is
a
good,
potentially
good
step
in
the
right
direction,
but
like
either.
We
need
to
make
a
decision
on
the
floatness
of
quantity
or,
like
figure
out
a
way,
maybe
like
add
a
new
type
to
to
that
to
structural
schema,
that's
into
our
string
or
float
or
or
make
quantity,
a
valid
format
option
in
and
of
itself
or
something.
B
B
B
Because
I
I
wrote
the
client-side
validation
from
foreign
and
I've
done
my
own
sauce.
I
mean
I
interpreted
the
stand
out
the
way
I
wanted
at
this
point
and
in
very
wrong
ways,
and
so
I
that's.
There
are
two
things
right:
the
clients
that
actually
look
at
the
open
api
and
use
the
right
validation
and
there
is
cubecode
who
does
it
something.