►
From YouTube: SPFx JavaScript SIG 11th of May, 2017
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
Hello,
this
is
the
SharePoint
framework
at
javascript
special
interest
group
bi-weekly
meeting
for
May
eleventh,
two
thousand
seventeen
already
half
of
the
way
through
May
things
are
going
crazy.
We
got
build
going
on
out
in
Seattle,
which
is
really
exciting,
so
do
check
out
some
of
those
recordings.
Some
of
those
events,
as
they
come
online,
really
exciting
announcements
around
graph
around
AI.
Some
really
cool
stuff
happening
out
there,
of
course,
SharePoint
as
well
great
announcements,
but
so
do
check
that
stuff
out
really
encourage
you
to
watch
those
sessions
as
much
as
you
can.
A
It
really
talks
about
the
upcoming
Microsoft
ecosystem,
the
whole
thing
so
some
really
neat
stuff,
but
for
this
call
we're
here
to
talk
about
the
SharePoint
framework
and
JavaScript
client-side
development
in
general,
as
it
relates
to
SharePoint.
So
we
sit
under
the
larger
SharePoint
patterns
and
practices
program,
and
what
purpose
of
this
call
is
is
to
kind
of
reduce
the
scope
down
a
little
bit
and
have
a
discussion
specifically
around
SharePoint
framework
development,
SharePoint
framework,
best
practices
or
patterns,
and
then
client-side
development
in
general
and
as
well.
A
The
JavaScript
core
component
that
we
work
on
as
part
of
this
call
to
help
folks
out
with
their
SharePoint
related
client-side
development.
So
two
weeks
down
there
at
the
bottom,
the
first
one,
the
AKMs,
SP,
P
and
P
dash
community-
will
take
you
to
the
Microsoft
tech
community,
and
that
is
a
great
place
to
ask
questions
or
get
help
or
feedback
around
ideas
and
also
provide
us
feedback.
And
then
the
next
link,
dev
office,
comm,
slash
slash
SharePoint.
A
Is
your
one-stop
shop
for
all
things:
SharePoint
development,
whether
you're
doing
new
SharePoint
framework
development
and
want
to
learn
about
that?
There's
some
great
tutorials
and
walkthroughs
there,
and
also,
if
you're,
doing
a
ad
in
development
or
the
classic
sort
of
WSP
development
we're
moving
all
our
development
related
or
SharePoint
development
related
resources
to
that
landing
page.
That
will
be
your
launch
pad
for
all
things.
A
A
But
we'll
start
with
a
quick
update
on
the
JavaScript
core
component,
we'll
go
over
the
SharePoint
framework
latest
then
we'll
go
through
those
demos,
and
then
we
should
have
some
time
at
the
end
like
we
try
to
do
for
open
discussion,
and
we
can
always,
of
course
have
the
discussion
as
well
in
the
IM
window.
So
welcome
everybody
just
a
reminder
of
ways
to
participate
in
sort
of
this
call
and
in
the
sort
of
special
interest
group
sub
community
demo
web
part,
I
could
be
a
SharePoint
framework
web
part.
A
It
could
be
just
a
client-side
development
web
part,
something
JavaScript.
It
could
be
something
using
node
and
the
JavaScript
core
library
anything
around
that
kind
of
client-side
development
really
want
to
give
folks
an
opportunity
to
demo
on
this
call.
We've
had
some
great
demos
in
the
past
from
folks
in
the
community.
I
know
I've
learned
a
lot
from
those.
So
if
you
are
working
on
something
cool,
do
please
reach
out
to
us
would
love
to
give
you
a
platform
to
demo
your
work
and
I
really
think
everybody
in
the
community
benefits
from
that.
A
So
I
think
you
benefit
from
a
chance
to
present,
and
we
all
benefit
from
a
chance
to
learn
from
you.
So
do
reach
out.
Would
love
to
have
you
demo
something
on
this
call.
You
can
also
contribute
on
github,
so
you
can
contribute
through
pull
requests
submitting
issues.
You
know
all
those
sorts
of
things.
We
really
welcome.
A
So
click
update
here
on
the
John,
a
JavaScript
core
component,
the
205
release
went
out
Monday,
give
that
a
try
upgrade
if
you
haven't
in
a
while
I've
got
a
lot
of
people
are
still
on
one
six,
so
encourage
you
update
to
205,
give
it
a
spin.
Let
us
know
some
feedback
got
a
bug
reporter
this
morning.
So
we'll
take
a
look
at
that.
So
if
you
find
anything,
do
check
that
out.
A
Pardon
me
hi.
My
allergies
are
really
really
bad
the
last
couple
days.
So
again
we
are
looking
for
feedback
on
new
features
and
things.
That
would
be
helpful.
That's
really
what
drives
each
release
is
feedback
and
hearing
from
folks
about
what
would
be
useful,
for
example,
for
the
last
release
somebody
came
along
and
said:
why
don't
you
guys
support
the
static
utility
methods
such
as
send
email
and
things
like
that
and
I
said?
There's
no
reason
we
don't
so
we
did
and
we
do
now
in
the
205
release.
A
So
those
are
the
cop
things
we
love
to
hear
from
you
of
things
that
might
be
missing
or
things
we
can
make
easier.
Let
us
know,
starting
in
my
head
and
on
paper,
to
sketch
out
support
for
Graf
and
how
is
that
going
to
you
know,
sort
of
shape
up
I've
got
some
ideas.
There.
We've
got
a
great
thread
if
you
have
thoughts
as
well.
A
Please
do
share
those
in
thread
and,
let
us
know
exciting
growth
numbers
for
April
I'll
show
you
guys
some
graphs
here
in
a
second
for
the
core
library,
but
really
excited
to
see
the
numbers
keep
growing
and
the
number
of
requests
keep
growing
and
then
just
a
thing
for
me.
Please
please
please
reopen
issues
in
github
if
you're
continuing
the
discussions,
I,
don't
always
see
the
emails
I'm,
actually
an
admin
across
a
lot
of
our
repos,
so
I
get
tons
of
emails
and
I
don't
want
to
miss.
A
If
you
have
further
questions
or
want
to
keep
a
discussion
going,
I
definitely
don't
want
to
miss
that
I
want
to
be
able
to
respond,
and
let
other
folks
respond.
So
please,
please
PLEASE
reopen
those
issues
for
visibility,
so
they're,
just
not
missed,
nobody's
trying
to
ignore
anybody
I.
Just
it's
a
lot
of
streams.
So
just
reopen
issues
we'll
see
them
and
we
can
continue
those
discussions.
So
yep
SharePoint
community
links
down
at
the
bottom
again
gets
you
to
the
SharePoint
community
and
then
the
git
er,
a
channel
is
also
a
great
resource.
A
If
you're
looking
to
have
quick
questions
about
using
the
JavaScript
core
component
library
in
particular,
that's
a
great
place
to
you
know
just
get
some
quick
feedback
and
let
us
know
if
you
have
a
question
so
just
to
go
over
the
usage
numbers,
real,
quick.
We
did
make
an
update
to
the
report.
So
it's
now
a
time
sensitive.
A
So
we've
got
the
year
and
the
month,
so
you
can
see
the
nice
trend
and
I
want
to
go
kind
of
start
in
the
top
left
and
you
can
see
the
usage
for
March,
April
and
May,
and
so
we've
gone
up
from
14
million
requests
out
of
615
tenants
in
March
to
18
million
requests
out
of
871
tenants
in
April,
and
this
is
for
approximately
the
first
week
in
May.
We've
already
got
13
million
requests
out
of
610
tenants,
so
really
exciting
growth
and
I
want
to
say.
A
Thank
you
all
of
you
who
are
helping
to
drive
that
growth
and
are
using
the
library
and
projects
and
giving
us
the
feedback
on
how
that's
going
so
really
appreciate
that,
and
also
really
excited
to
see
that
this
is
something
folks
are
finding
useful,
so
do
check
it
out
if
you
haven't
below.
That
is
a
graph.
This
is
sort
of
over
time.
So
you
can
see
it's
been
a
steady
growth
and
I
think
a
fairly
impressive
growth.
A
As
we've
gone
from
August
we
reached
August
2016,
where
we
started
tracking
all
the
way
now
through
April
was
final
and
then,
like
I
said.
That's
just
the
first
week
in
May,
we're
already
just
about
at
the
March
numbers.
A
little
shy
so
really
excited
to
see
that
growth
and
that's
due
again
to
you
guys
in
the
community.
So
thank
you
very
much
for
helping
to
drive
that
and
I
also
wanted
to
include
on
the
right.
There
is
the
number
of
requests
by
country
and
I've
sorted
it
by
the
number
of
requests.
A
So,
instead
of
the
number
of
tenants
by
number
of
requests
which
I
thought
was
interesting
to
see,
Australia
is
leading
everybody
with
just
shy
of
Ora
raagas
3.6
million
spain's
3.5
million
out
of
just
18
tenants,
and
then
the
u.s.
can
only
muster
3.2
million
out
of
218
tenants.
So
I
thought
that
was
really
exciting
to
see
those
numbers
kind
of
spread
out
and
not
just
focused.
A
You
know
in
this
or
that
country
so
really
exciting
to
see
the
broad
usage
as
well
around
the
world
really
exciting
stuff,
and
you
know
again
thank
you
to
all
of
you
in
the
community
really
appreciate
it.
So
with
that,
I
believe
we're
ready
to
turn
this
over
to
Lisa,
and
we
will
let
him
give
us
a
quick
update
on
SharePoint
framework
Thank.
B
Yes
thanks,
Leo
and
David
as
well,
so
a
few
things
what
I
want
to
do
before
we
go
there
on
this
week,
Monday
we
released
a
nice
webcast
work-related
on
SharePoint
framework
and
how
to
call
external
API.
So
it's
kind
of
a
thinking.
Maybe
we
would
do
a
demo
on
this
one
and
for
this
week
up
next
we'll
do
that
for
following
special
interest
group,
because
we
have
something
exclusive
to
search.
B
But
this
is
actually
super
super
interesting
webcast
and
a
super
powerful
pattern,
because
it
is
actually
enabling
you
to
do
elevation
of
privileges
that
is
enabling
you
to
access
on-premises
this
enabling
you
to
do
whatever
you
want
in
SharePoint
Online
in
a
secure
way.
So
please
do
have
a
look
on
that
webcast.
B
The
SharePoint
framework
is
mainly
as
a
what
we're
delivering
from
engineering
ship
and
framework
is
a
UI
framework,
at
least
for
now,
and
then
quite
often,
you
need
to
pull
in
a
secure
wave,
your
custom
web
api
to
make
something
additional
happen
and
we'll
walk
through
that
one
without
and
one
key
point
to
mention
on
that
one
as
well,
without
a
deltas
or
MSA
all.
So
how
do
we
securely
call
that
channel
between
Shabazz
member
client,
side
of
export
and
usher
endpoints
now
have
a
look
on
the
webcast.
It
actually
works
through
things.
B
We
do
have
a
simplest
example
on
that
one
as
well.
It
is
missing
your
site
will
we'll
work
on
the
guidance
where
there's
articles
coming
up
on
this
one
as
well
slightly
later
now,
moving
on
on
other
things,
let's
see
my
screen
is
updating.
One
is
ended
up
dating
one
step
forward.
Now,
let's
actually
move
into
those
announcements
which
we
did
yesterday
and
apparently
the
styling
slightly.
Why
is
it
orange
anime?
B
So
now
what
we're
releasing
are
pretty
soon
to
Def
preview
and
what
we're
demoing
today
in
this
call
and
also
in
built,
is
the
SharePoint
framework
extensions,
and
this
is
good
example.
This
is
the
picture
which
is
in
a
blog
post
as
well,
showing
actually
those
extensions
life
or
in
the
end
screen
as
well,
so
you're
able
to
create
three
kind
of
extensions
or
customizers.
B
So
to
say
the
number
one
customizer
or
the
first
customizer
is
the
application
customizer
then
application
customizer
is
basically
the
same
as
use
a
custom
action
inside
collection
or
site
or
in
list
level
and
technically
from
an
API
perspective.
You
are
actually
we
are
taking
advantage
of
the
user
custom
action,
existing
user
custom
action,
eight
the
ice,
but
then
we
are
cooking
into
that
user.
Custom
action
to
a
application,
client
component
ID,
which
has
to
be
then
hosted
in
the
app
catalog.
So
essentially
the
process
is
exactly
the
same
as
client-side
web
parts.
B
If
you're
familiar
with
those,
you
need
to
first
deploy
your
customization
to
the
app
catalog
and
then,
after
that,
in
the
site's,
you
can
actually
reference
that
using
a
few
different
options.
The
second
customizer
is
common
steps.
Customizer.
This
is
more
around
hey.
I
want
to
have
a
button,
either
in
the
tool
box
or
in
the
context
menu
which
should
execute
code.
As
an
example,
you
want
to
open
up
a
let's
say,
a
pop-up
which
is
asking
if
you're
selecting
two
items
in
a
list.
B
You
want
to
set
up
a
pop-up
which
is
then
asking
something
related
to
items
or
whatever
is
your
use
case?
What
you
want
to
do
so,
and
so
that's
kind
of
a
more
on
the
on
the
bottom
extensions
and
the
third
one
which
isn't
super
visible
until
I
actually
show
them
and
explain
them
is
the
field
customizer
now
and
the
field
customers
are
refers
to
classic
chase
link
capabilities,
but
it's
implemented
again
in
a
slightly
different
way,
so
that
we
have
that
centralized
control
in
a
tenant.
B
When
we
are
deploying
these
customizations
of
customizations
to
chip,
one
and
SharePoint
Online,
and
what
it
essentially
means
is
that
you're
able
to
in
the
first
release
in
the
preview,
one
must
earn
it
only
actually
at
the
concert,
if
only
it's
valid,
when
we
are
in
a
read-only
mode,
but
we're
looking
into
getting
to
the
edit
mode
as
well
and
you're
able
to
essentially
control
how
the
field
value
is
being
rendered.
So
just
as
well,
you
could
actually
access
this.
If
the
field
value
is
not
a
let's
say
an
address,
you
could
show
a
map.
B
Is
it
something
else
you
can
say
whatever,
and
it's
actually
up
to
you?
What
I
want
to
render
don't
forget
some
customizer
with
sister
the
panel
which
again
with
just
marking
the
panel
on
top?
So
let's
be
clear
on
that
one
as
well,
so
you
do
not
have
to
do
UI
level
of
modifications.
It
could
be
a
Google
Analytics.
B
It
could
be
whatever
analytics
which
looking
into
the
sharepoint
online
sign,
so
it
could
be
a
Chava
script
which
is
not
visible
for
the
integer
or
you
can
actually
within
to
application
customize
that
you
can
call
a
request
from
a
SharePoint
framework.
The
page
give
me
an
instance
or
access
to
the
footer
section
or
header
section
and
then
shape
on
flavor
will
give
you
a
object,
which
is
the
header
section,
and
then
it's
up
to
you
whether
you
actually
want
to
render
over
there.
B
So
again,
you
have
full
control
on
that
deal
on
the
on
the
header
section,
when
we
start
we'll
start
with
a
header
section
and
hitter,
let's
say
marker
on
top,
but
we're
looking,
obviously
into
having
footers
left
side,
navigation,
curb
positions
and
all
of
those
additional
locations
as
well.
So
within
your
code,
you
can
easily
kind
of
a
hook
into
different
UI
elements
in
a
SharePoint
and
we'll
currency
that
those
elements
will
be
there
in
the
future
as
well,
regardless
of
the
UI
changes.
B
What
we're
making
and
that's
really
the
key
difference,
if
you
think
about
the
classic,
let's
say,
use
a
custom
action,
because
the
classic
use
a
custom
action
relied
on.
If
you
are
doing
UI
elements,
modifications
its
relied
on
Dom,
page
dome,
structure,
modifications
and
if
we
do
a
change
in
the
dome
structure
in
the
in
the
sharepoint
online,
your
customization
might
get
broken.
So
this
is
more
future-proof
way
of
doing
those
customizations
and
answering
on
Leo's
question
as
well.
B
So
these
are
absolutely
available
in
the
modern
experiences,
so
the
modern
list,
scrubs
modern
SharePoint
sites
and
all
of
that
inspiration
problem
and
when
we
start
we'll
start
with
a
in
the
field,
customizer
site,
we'll
start
with
the
read-only.
Now,
let's
say
manipulation.
We
are
absolutely
looking
having
that
field
customizer
to
be
able
to
override
to
editing
experience
as
well.
That's
related
on
Stefan's
question
under
underlined
window.
B
So
essentially,
the
whole
point
is
that
we
want
to
enable
those
typical
scenarios
with
where
you
were
using
test
link
user
custom
actions
to
modify
the
site
so
have
more
control
have
let's
say
top
header
sections
which
are
fully
customized,
footer
sections
in
the
future
and
so
on.
So
finally,
getting
out
of
the
limitations
with
the
groups
or
modern
SharePoint
site,
whatever
we
want
to
call
them,
and
this
is
meant
to
be
in
the
in
the
modern,
modern
experiences,
at
least
when
we
start
so
we're
looking
into
enabling
some
of
this
also
in
the
classic.
B
But
it
might
be
that
you
need
to
fall
back
on
the
classic
model
models
with
that
one.
When
we
start
it
will
be
only
in
the
modern,
modern
list,
experiences
and
model
group,
modern
experiences,
but
again
that's
a
start
as
a
big
preview.
And
then,
when
we
go
closer
to
the
g8,
the
capabilities
are
still
getting
changed
and
modifying
now
technically,
coming
back
on
the
classic
and
modern
experiences
as
well.
B
You
can
still
use
the
classic
space
link
in
the
classic
experience
and
then,
if
that
list
is
being
rendered
into
modern
experiences,
it
will
actually
flip
automatically
to
the
modern
extension.
That's
one
option
to
make
that
happen
as
well.
Now,
let's
actually
have
a
look
on
what
else
it'll
actually
have
done
this
one.
So
this
is
just
a
list
of
things
and
from
a
terminology
perspective,
so
we
do
have
an
application
customizer.
B
B
Cool,
let's
actually
have
this
one
alive,
I'm,
just
looking
into
Russell's
question:
will
we
be
able
to
set
global
math
by
an
application
customer
so
well
the
there's
no
override
of
the
existing
nav,
but
you
can
absolutely
render
a
cloak
on
navigation
across
all
of
your
site
collections
using
the
application
customers.
So
that's
absolutely
global.
B
Q
XO,
thank
you.
It's
definitely
got
it
and
it
went
across
the
world
as
well.
So
that's
that's
good
now,
where
do
we
actually
want
to
start?
Let's
actually
start
the
day,
the
one
thing
which
I
didn't
actually
have
a
slide,
so
one
thing
what
we're
putting
into
dev
preview
pretty
soon
as
well.
Naturally,
something
here
is
a
new
capability
related
on
our
web
parts
as
well,
so
as
part
of
the
day
preview,
which
will
start
pretty
soon
now
you're
able
to
create
connections
between
the
web
parts.
B
So
you
are
able
to
create
associations
like
a
list
and
details
list
or
details
experience.
So
let
me
create
a
nuclear
quick
base,
but
start
with
that
one
and
get
back
on
those
conditions
in
a
second,
so
create
a
new
page.
Let's
call
this
seek
demo
and
it's
actually
at
our
one
web
first
step
part
here,
which
is
our
training
lists
web
board.
So
training
with
nice
web
part
is
to
reactivate
quickforce,
which
is
listening
trainings
from
one
of
the
lists
within
the
within
this
time,
and
I
can
actually
feel
that
this
one.
B
So
if
I
want
to
do
rusting,
it
actually
filters
that
dynamically
or
forest
or
do
I,
have
a
desert
now
advanced,
Orion,
I'm
interested
on
that
Muslims.
No,
it
wouldn't
it
be
cool
if
I
would
be
able
to
have
multiple
webparts
on
a
page
and
then
when
I'm
selecting
one
of
these
I'm
going
to
be
able
to
percent
additional
details
and
that's
essentially
what
the
webpart
connections
are
giving
us.
B
So
let
me
add
that
additional
details
web
part
here
and
there
we
go
and
there's
my
additional
details
web
part
and
let's
save
the
page
and
we
can
actually
see
how
it
works
in
practice.
So
now,
if
I
list
or
let's
say
it's
arresting
and
Iraq
arresting
hello
inaudible
to
see
the
screen,
it
says
some
error
and
it
is
rejoined,
presentation,
okay.
So
that
seems
to
be
now
because
the
other
many
are
saying
that
it's
fine
for
them,
so
you
probably
need
to
would
be
cleared
to
restart.
B
And
if
that
does
not
still
work
of
this
example
at
there
could
be
app
Android
issue.
So
the
recording
of
this
one
will
be
alive
tomorrow
in
the
YouTube
channel.
So
we're
able
to
actually
have
a
look
on
that
after
that,
okay
good.
So
so,
if
I'm
out,
if
I'm
not
clicking
something
in
this
list
of
things,
I
can
see.
Actually
the
details
being
reflected
on
to
other
webparts,
so
you're
able
to
see
that
they're
moving
basically
in
two
locations,
so
the
map
is
moving.
Some
key
codes
are
moving
and
dimittis
and
moving.
B
So
let's
do
forests
and
click
that
one.
So
we
can
actually
see
that
this
is
managing
in
a
forest
experiment,
training
or
whatever,
so
where
this
actually
works.
Priority
Phillipe,
first
and
relatively
fluently
now
right
now
that
the
communications
is
being
done
using
code,
so
there's
no
UI
where
the
infuser
would
be
actually
doing
that
association
and
but
we're
looking
into
having
that
one
in
there
in
the
future,
as
well,
so
you're
able
to
as
an
end
user.
B
If
there's
web
parts
which
are
supporting
the
same,
let's
say
in
the
face
you're
able
to
do
those
by
yourself
and
those
updates
by
yourself
we're
also
looking
at
they
not
directly
as
part
of
SharePoint
framework
but
the
start
of
SharePoint
engineering.
We
are
absolutely
looking
into
addressing
the
classic
requests
and
plastic
challenge
around
modern
pages,
which
is
that
modern
Bates
has
only
one
canvas
as
others.
Webparts
has
to
be
always
from
doctor
button,
and
but
obviously
everybody
wants
to
have
multiple
columns
and
that's
coming
up
and
we're
building
on
on
that
one
as
well.
B
So
that's
in
a
roadmap
I
can't
give
you
an
exact
date
on
that.
Do
various
reasons,
but
you'll
see
announcements
on
that
one
later
on
good
on
this
one
just
quickly,
I
made
this
show
how
it's
being
done.
So
let
me
actually
get
to
those
webparts
there's
my
list
report,
and
this
is
and
really
nothing
more
than
doing
communications
between
these
two
webparts
and
I'm
looking
in
the
wrong
location,
because
it's
in
components
and
where
do
we
actually
have
that.
B
B
B
So
this
is
essentially
the
web
part,
which
is
saying
hey,
I've,
been
selected.
If
there's
anybody
on
a
page
who's
interested
on
this
particular
event.
Here's
the
data
which
were
selected
from
my
side
and
now
the
details
report
is
essentially
that
then
just
subscribing
those
events.
So
let
me
go
to
the
react
component
and
where
do
we
have
two
subscribing
a
seven
there
we
go
in
the
component.
It
mounts
we're,
saying,
hey
chef
and
framework
is
any
if
anybody
is
raising
this
kind
of
an
event
in
the
SharePoint
framework
side
or
in
the
page.
B
Please
call
this
endpoint
or
this
method,
and
it
would
give
to
this
one.
It's
nothing.
Just
a
typical
type
script
function
with
the
string
getting
the
data
object
as
part
of
it,
and
it
can
process
that
any
way,
it's
once
so
relatively
simple
process
for
now,
but
it's
actually
natively
supported
through
SharePoint
framework
as
we
move,
along
which
obviously
all
those
operational
scenarios
and
models
as
well.
B
Now,
let's
get
to
those
extensions,
so
I'm
going
to
click
back
on
the
on
the
process
now
and
I'm
going
to
use
my
pre
created
already
list,
which
has
a
lot
of
those
extensions
already
available
so-
and
this
is
say,
a
custom
list
which
has
a
actually,
let's
do
small
modification
on
this
one.
So
let
me
edit
the
current
view,
and
let
me
show
you
this
wizard
in
practice:
I'm
going
to
troll
emergency
contacts
in
a
little.
A
B
Probably
Patrick
help
them
back
on,
so
this
is
a
a
let's
say.
A
classic
was
a
typical
SharePoint
list
and
within
this
list
right
now
we're
listing
people
who
are
getting
who
have
signed
on
and
this
training
classes
within
the
contours
of
our
ventures.
Now,
if
you
want,
this
is
essentially
kind
of
a
simplistic
scenario.
If
you
want
to
expose
some
effects,
a
semi
confidential
data
like
the
phone
number
or
emergency
conduct,
I
can
get
those
being
visible
on
the
page,
so
let's
actually
get
the
whole
list
of
items
and
immediately
windows
fields
are
visible.
B
In
the
view,
the
SharePoint
will
realize
that
hey,
hey,
actually
those
fields
have
a
saucier
tit.
They
have
a
custom
field
customizer
they
have
a
custom
field,
customizer
associated
to
them.
So
it's
going
to
actually
ask
that
field
customize,
that
the
rendered
output
and
this
particular
field
customers
are
relatively
simple.
It
essentially
just
hides
the
value
unless
I'm
actually
interested
on
the
value.
B
So,
if
somebody
sneaking
behind
up
here
that
kind
of
having
look
on
on
the
list
of
phone
numbers
getting
heated
but
absolutely
it's
up
to
you,
how
do
you
want
to
add
this
functionality
to
behave?
So
you
as
a
developer?
You
have
full
control
on
this
div
with
a
friend
during
the
value.
After
of
the
tills
itself
and
as
a
developer,
you
get
access
on
other
fields,
values
in
the
row.
You
get
access
on
the
list
and
the
context
and
everything
else
and
I'll
show
that
one
in
a
practice
in
a
second
now.
B
The
second
thing,
what
we
have
visible
in
the
UI
is
also
the
high
level
top
navigation.
Sorry,
the
header
which
is
done
by
application
customizer,
and
this
particular
case
and
the
application
customizer
is
essentially
they're
realizing
but
hey
by
the
way.
This
content,
sensitive
information,
please
handle
the
accordingly
two
component
guidelines,
because
the
application
customers
are
realized,
but
within
the
page
we
have
fields
which
has
this
still
customizer
on
it.
So
it's
actually
enabling
itself
as
a
implementation,
but
that's
basically
a
modern
user
code
user
custom
action.
B
If
you're
familiar
with
that
concepts
from
a
past
and
except
that
it
has
been
implemented
using
the
SharePoint
framework
and
it's
also
using
the
modern
way
of
associating
itself
on
the
site
now,
I'll
quickly
run
through
some
code
and
I
will
quickly
then
and
I
explain
how
did
we
hook
in
essentially
the
field
and
user
custom
action
on
the
page?
And
then
we
can
move
back
on
the
questions,
because
I
can
imagine
that
there's
a
few
questions
on
them
on
the
queue
it's
sorted
quickly
on
the
updates
of,
let's
say
the
yeoman
template.
B
We
actually
are
running
in
my
case,
I'm
running
a
early
built
from
the
engineering
and
because
focus
I
have
access
under
under
daily
builds,
and
but
this
one
already
has
been
modified
to
support
the
extensions,
but
just
to
show
you
what
it
actually
means
in
practice.
So
solution
name
is
simple
and
quite
often
using
react
and
that's
already
a
new
question
which
type
of
client
component
to
create
web
port
or
an
extension.
If
you
choose
the
web
part,
it
will
be
the
classic
mode
and
classic
steps
with
the
report
creation.
B
Actually
get
this
couple.
The
initial
stuff
holding
completed
we're
not
going
to
wait
for
that
one
in
this
Court.
But
let
me
show
you
what
you're
actually
kidding
so
you're
kidding
a
normal,
let's
say:
SharePoint
framework
solution.
It
looks
exactly
like
the
solution
if
you're
familiar
with
client-side
web
parts,
so
it
has
to
be
exactly
the
same
basic
structure,
right,
manifest
packet
solution
and
all
content.
B
And
then,
if
I
extend
the
sources,
we
just
have
a
new
folder
called
a
station,
and
in
there
it's
going
to
score
folders
and
to
be
false
structure
and
the
default
model,
for
example,
for
application
customizer.
In
this
particular
case,
so
application
customers
are
just
showing
a
quickly
how
how
you
actually
hook
into
things
as
well.
So
all
of
these
customizes
they
do
have
a
base
class,
which
is
giving
you
some
basic
access
on
things.
So
as
an
example,
you
can
do
something
like
this
just
context,
and
you
have
all
of
that
typical
things.
B
What
you
should
have
access
and
like
you
just
have
or
like
you're
having
in
client-side
web
part
as
well,
so
to
develop
an
experience
is
steps
after
the
same
with
a
application.
Customizer
that
actually
applies
on
on
all
of
these,
almost
is
that
you
are
being
essentially
given
the
full
power
to
do
whatever
you
want
in
on
render
this
relatively,
not
necessarily
the
best
sample
and
the
application
customizer,
because
this
one
is
to
throwing
an
alert.
But
what
mention
it
doesn't
have
to
be
something
which
is
rendering
in
the
UI.
B
It
could
be
something
which
is
running
on
a
background,
doing
some
settings
or
adding
that
additional
things
or
it
could
be
Google
Analytics
or
whatever
analytics
service
you're
using
within
your
internet
as
well
to
pull
up
legibility.
What
you
want
to
do
now,
let's
move
into
that
slightly
more
complex
solution,
I'm
going
to
show
those
ones
in
practice
as
well,
so
let's
actually
close
up
the
web
fonts,
which
goes
to
the
extensions
depth
list
here,
which
is
so
in
my
demo.
B
Let's
go
to
the
on
render
there
we
go.
This
is
a
react
component
or
react
implementation,
but
this
is
already
showing
and
that
placeholder
to
get
access
on
the
dates
here
of
the
page.
So
through
the
list
of
contacts
placeholders
you
get
if
you
can
actually
get
an
instance
and
the
well-known
locations
in
a
page-
and
we
start
with
the
base
header
we'll
be
extending
that
in
the
future.
If
we
get
to
placeholder
and
then
we're
essentially
just
rendering
the
react
components
and
then
it's
again
after
us,
what
we're
going
to
do.
B
Essentially,
you
have
full
control
to
do
whatever
we
want
to
do
inside
of,
for
example,
for
this
div,
which
are
essentially
getting
technically.
We
obviously
want
people
to
remain
inside
of
that
div,
but
oversee
technically,
you
can
do
whatever
you
want.
We
can't
limit
you
from
technology
perspective,
because
it's
a
JavaScript,
so
you
can
do
technically
whatever
one
on
page
now
on
the
field
customizer,
let's
actually
have
a
quick
look
on
that
one
as
well,
almost
the
same
story.
B
So
if
the
field
customizer
is
attached
to
do
a
field
and
I'll
come
back
on
how
these
things
are
being
attached
in
a
second,
it's,
the
own
render
cell,
essentially,
which
is
the
one
where
SharePoint
SharePoint
has
realized
that
there's
a
client-side
component
on
the
field,
hey
and
it
is
requesting
you
to
render
out
the
value,
and
then
it's
really
up
to
you
what
I
want
to
do
and
what?
How
do
you
render
the
value
out
in
this
particular
implantation?
B
It's
nothing
more
than
the
fact
that
if
let's
see
I'm
scrolling
down
where's
my
render
there's
my
render
use,
we
should
show
private
data.
Essentially,
if
the
mouse
is
is
on
top
of
the
field,
let's
actually
show
the
private
data,
otherwise,
let's
actually
use
Clark.
So
essentially,
I
took
the
value
of
the
field,
so
it's
nothing
more
than
that
from
a
implementation
perspective,
because
that's
a
CSS
and
trick
to
make
that
happen.
But
again
up
to
you.
This
is
relatively
simplistic
scenario,
because
we're
just
overriding
the
style
and
when
the
mouse
is
over
the
field.
B
B
Good
and
one
thing
which
I
didn't
technically
show
on.
There
is
comments,
so
we
do
have
also
the
common
set
extensions
and,
for
example,
for
this
demo
there's
two
commands,
which
are
not
something
that
at
least
I
do
apologise
and
done,
but
you
can
essentially
and
define
custom
comments
and
comment
IDs
within
your
code,
contact,
user
or
open
class
and
then
within
your
code.
Essentially,
you
can
do
okay.
B
Now
one
thing
what
I
wanted
to
quickly
show,
because
then
you
create
this
and
awesome
I've
developed
these
and
and
how
do
I
actually
make
these
things
then
available
and
enable
on
the
slide.
So
this
is
a
SharePoint
favorite
solution.
I
like
find
set
solution,
so
SharePoint
framework
solutions.
Do
you
need
to
get
deployed
on
the
app
catalog
and
that's
really
the
key
difference?
If
you
consider
this
one,
comparing
the
classic
J's
link
and
use
the
custom
actions
if
you're
familiar
with
that
model?
B
Now,
because
this
requires
that
the
tenth
administrator
has
proven
these
scripts,
because
these
are
running
in
the
context
of
the
user.
So
this
is
a
security
requirement
or
control
requirement,
well
necessarily
necessarily
requirements,
but
it's
a
controlling
step
so
that
the
ten
administrator
or
a
person
to
whom
tenet
administrator
has
given
the
permissions
to
upload
applications.
Here
is
able
to
actually
get
that
application
available
and
whenever
we
are
uploading,
the
solution
in
that
catalog.
That
means
that
the
solution
is
then
available
to
be
installed
on
the
site.
B
Now
we're
looking
into
having
this
in
a
much
more
streamlined
in
the
future,
and
so
if
your
solution
is
called
that
kind
of
a
solution
which
should
be
hooking
to
all
of
the
slides
immediately
autumn.
Basically,
you
can
actually
design
that
and
do
the
settings
in
the
in
your
solution
package
we're
looking
into
doing
that.
B
Customer
collections,
and
like
mention
you
can
use,
for
example,
feature
framework
to
make
that
happen
as
part
of
your
SharePoint
framework
solution.
Installation,
that's
one,
okay,
the
second
option
again,
depending
on
how
you
are
creating
a
slide
collections,
is
simply
to
use
code
or
alternative
options
as
well.
So
this
is
a
super
simplistic.
Let
me
get
slightly
OOP
zoom,
this
super
simplistic
piece
of
season
code
to
be
a
rescue.
B
Then
I'm
saying
that
that's
an
open
custom
customizer,
it's
a
script
link,
so
it
will
be
rendered
as
a
embedded,
JavaScript,
honest
on
the
site,
collection
and
then
I'm,
saying
with
the
new
property
in
which
we
released
I,
think
in
February
season
or
in
the
not
this
one
was
in
the
March
season
raised
for
SharePoint
Online
I'm,
essentially
saying
hey
check
one.
You
should
have
this
kind
of
an
application
customizer
available
within
this
site
collection
and
whenever
user
is
rendering
anything,
please
make
sure
that
we're
rendering
that
JavaScript
on
the
page
as
well.
B
That
way,
SharePoint
knows
the
render
that
essentially
SharePoint
renders
the
page
it
realizes.
Hey,
there's
a
user
custom
action.
Oh
this
is
a
modern
using
custom
action
with
the
client-side
component
ID
create.
Do
we
have
a
a
component
in
the
application
catalog
or
in
our
manifests
in
the
application
catalog
designe
available?
Oh
yes,
we
do
awesome
I'm
going
to
render
that
as
part
of
my
page
as
well
and
almost
with
the
same
story
with
fields
as
well.
B
You
are
able
to
also
have
client-side
component
properties,
and
this
is
actually
a
Chasen
kind
of
a
Chasen
definition,
so
you're
able
to
say
something
like
type
equals.
Let's
say
four
four
and
what
it
means
is
that
your
code
can
now
read
this
property.
Read
this
property
with
no
new
code
and
whatever
the
property
is
doing
within
your
code.
B
So
we're
able
that
these
additional
instructions
for
the
concept
component
and
then
change
your
implementation
based
on
that
and
that's
pretty
cool,
as
well,
already
kind
of
a
considering
the
next
steps
and
requirements
and
how
the
power
of
exercise
nuances
and
all
of
them
I'm
not
going
to
go
to
details
on
the
development
experience,
because
I
want
to
make
sure
that
we
have
enough
time
on
for
the
questions.
Certain.
Imagine
that
there's
quite
a
few
questions
now
Windows
Live
Nation
by
do
apologize.
B
I
do
not
have
a
two
screens
as
I
can
follow
up
on
the
disk,
but
maybe
a
wanting
to
mentioned
on
on
the
employment
experience
around
this
one.
So
right
now,
when
we
go
to
the
Deaf
preview,
pretty
soon,
not
today
and
not
yesterday,
within
more
within
weeks
rather
than
months,
but
pretty
soon
we
go
to
deaf
preview
and
we
will
give
this
available
within
the
package
section
and
also
in
the
first
release,
tenants
or
dr.
thinking.
Right
now.
B
We
will
not
have
a
work
bench
experience
for
doing
development
with
extensions,
and
we
do
understand
that.
It's
it's
a
pity.
But
what
it
means
is
that
you
need
to
be
able
to
do
development
and
testing
of
these
things
within
the
SharePoint
site.
Now
we
do
have
tricks
on
doing
that.
We
do.
We
will
record
a
video.
B
Essentially
you
are
able
to
host
these
extensions
in
my
case
in
this
site,
these
are
actually
being
hosted
from
CDN,
well
SharePoint
as
CDN,
actually-
which
is
this
folder
in
here,
but
it's
usually
office
raises
to
five
CD
in,
but
as
a
developer
and
you're
able
to
close
these
from
your
on-premises
local
box
as
well,
using
the
local
host
model.
But
you
would
be
testing
them
on
a
live
site
because
the
workbench
can't
really
it
doesn't
have
this
kind
of
an
ad
hoc
list
creation
and
how
to
podcast
actually
render
the
stuff
behavior.
B
So
you
but
you're
able
to
essentially
say
with
a
certain
query
parameters
here
at
a
SharePoint
I,
do
explicitly
tell
you
that
I
want
to
do
some
debugging
with
these
components
and
do
load
them
from
my
own
premises.
Localhost.
You
are
able
to
have
a
depth
and,
let's
say,
connected
development
experience
when
you
are
developing
and
testing
what's
actually
happening
within
to
within
a
sharepoint
realize.
But
we'll
come
back
on
all
of
those
details.
We
will
have
tutorials
available
videos
available
on
how
to
get
started.
B
Tutorials
will
concentrate
on
hey,
let's
create
a
fuel
customizer
and
let's
do
a
small
modification
and
get
it
deployed
there
we
go
now.
This
is
how
it
works
on
Austin.
So
all
of
that
is
pretty
much
well,
I
wouldn't
say
done,
but
we
do
a
vanilla
version
to
follow
those
tutorials
over
debating.
So
whenever
we
are
looking
down,
the
version
which
is
going
live
will
push
out.
The
packages
will
push
out
videos
documentation
of
that.
B
At
the
same
time,
cool
I
didn't
want
to
steal
anything
more
time
than
this
I've
been
talking
now
as
a
monologue
in
the
30
minutes.
So
let
me
let's
do
this.
Let's
flip
back
on
the
slide,
so
you
don't
see
my
Skype
screen
because
doesn't
mechanisms
and
then,
if
there's
any
specific
questions,
apparently
there
has
been
a
long
discussion
on
the
ion
window
already.
B
But
if
there's
any
specific
questions
around
this,
one
just
actually
shoot
away,
I
think
actually
one
moment
I
think
I
added
one.
Yes
before
we
go
to
the
QA
section
and
for
questions
which
I
didn't
which
battery
couldn't
answer,
or
somebody
else
didn't
answer
and
quick
note
on
this
one
as
well
so
now
and
today
in
the
builds
of
us,
we're
pointing
out
that
we
already
have
a
TA
for
web
parts
in
SharePoint
framework,
we
will
keep
on
evolving
the
web
parts
as
well.
B
We
will
start
the
extensions
preview
producing
with
an
application
customize
their
command
set
customizer
and
field
customizing
we're
looking
into
enabling
adding
well,
for
example,
SharePoint
framework
development
using
and
outputting
adding
map
functionalities
as
well.
So
if
your
requirement
is
that
hey
I
cannot
embed
the
JavaScript
on
a
site,
I
need
to
have
security.
Isolation
in
the
adings
is
still
absolutely
100%
a
valid
solution
as
well
and
looking
into
other
future
options
as
well,
so
the
SharePoint
framework
will
gradually
expand
and
provide
additional
component
additional
capabilities
as
we
move
along
with
this
journey.
B
Yes,
then
trouble,
please
related
on
the
above
discussion
well
in
full
pace
taps
on
the
roadmap.
Yes,
that's
it
that's
mentioned
in
our
roadmap,
page
from
Russell,
looking
into
that,
it
is
still
in
our
backlog,
but
it's
not
something
which
we
explicitly
want
to
say
that
this
is
coming
super
super
super
soon
it
might
be.
Actually
it's
waiting
for
our
final
pronunciation
right
now,
we're
concentrating
on
polishing
the
wet
pots
and
then
making
sure
that
the
extensions
are
heading
to
the
Deaf
preview
and
getting
their
feedback
on
tech
stations.
B
B
So
because
we
need
to
somehow
you
can
use
feature
framework
you're
going
to
see
something
in
your
wrist.
You
can
use
multiple
other,
but
not
that
many
other
options,
but
still
the
cooking
that
customizer
either
the
user
custom
actions
or
enter
the
field
protection
question
will
we'll
be
able
to
use
craft
HTTP
client
school,
one
of
our
things,
Web
API
Asha
functions,
secure
it
with
a
show
ad,
something
which
isn't
and
the
crap
I'm
guessing
that
some
access
token
is
automatically
edit.
B
So
if
I
resisting
a
ad
app
grant
permissions
in
the
SharePoint
that
entered
a
planet
that
might
be
all
possible
so
on
the
current
client
would
submissions
into
yesterday's
plug
post
as
well,
which
will
be
there
it's
essentially.
What
we're
doing
is
that
they're
enabling
open
ID
connect
across
all
of
the
services
we
can
SharePoint
Online,
but
with
a
subset
of
services
and
subsets
of
scopes.
B
When
we
start
with
the
initial
value
and
initial
access
will
be
from
shape
on
framework
and
for
SharePoint
towards
craft,
and
there
will
be
limited
scopes
in
the
graph
endpoint
on
and
do
apologize.
We
were
looking
into
extending
data
spot.
So
when
we
start,
you
cannot
actually
secure
the
access
token
against
your
custom
with
API,
but
that's
absolutely
in
the
long
run
in
the
roadmap,
we're
looking
into
getting
that
to
happen
as
well.
B
The
webcast
was
released
on
this
Monday
and
does
actually
show
how
to
securely
call
an
usher
function
from
SharePoint
framework,
but
that's
only
for
authentication
and
not
for
authorization.
So,
essentially
you
can
secure
your
connection
between
SharePoint
framework
and
and
with
customer
pay
PR
as
your
function,
using
the
guidance
which
was
shown
in
the
end
of
this
week's
podcast
and
there's
a
guidance
article
coming
up
on
that
one
spot,
but
that
doesn't
mean
that
you're
able
to
get
an
access
token
and
pass
that
access
token
to
the
Web
API.
B
It
means
that
you
would
have
to
then
use
app
only
or
specific
account
when
you're
calling
back
from
the
SharePoint
back
to
SharePoint
or
calling
external
services
from
the
tracks.
Api
doot
any
last
words.
Let
us
know,
let
us
add,
customers
as
to
the
field
through
the
UI
rather
than
needing
the
right
code
and
we're
looking
into
making
that
simpler
in
the
future.
Right
now
again,
this
is
hitting
the
dev
preview
now
relatively
soon.
So
this
is
early
still,
it's
not
all
fun
but
we're
getting
there.
So
all
of
that
feedback
is
super
valuable.
B
Do
you
know
when
SPF
X,
German
language
Bach
will
be,
is
fixed
and
no
idea
now,
but
right
now,
if
you
have
any
issues
on
SharePoint
framework
and
whenever
it
says
to
ring
them
to
SPF
Doc's
issue
list,
those
are
actually
getting
replicated
and
those
issues
to
our
vs
do
so.
Our
engineering
is
looking
in
the
toast
and
we're
prioritizing
those
items.
I
do
not
have
a
timeline
for
that
particular
thing:
cute
Easter
link
for
the
cleaners
to
start
with
DES
and
to
me
this
is
referring
to
tutorials.
B
Well,
that's
the
sample
tutorial,
that's
actually
good
points,
and
but
if
you're
looking
into
getting
started
on
SPF
x,
the
easiest
way
to
find
location
is,
let's
be
FX,
tor
tutorials
and
this
that
akms
SPSS
tutorials,
that's
where
we
have
that's
in
the
deck,
turtlecom,
sharepoint
official
location
for
all
of
the
development
look
at
documentation
on
SharePoint,
where
we
have
ten
tutorials,
which
are
linking
into
videos
and
all
stats
are
able
to
kind
of
a
crutch.
Allah
learn
how
to
do
a
chevron
framework
cute.
B
Yes
me
and
my
a
K
and
there's
quite
a
few
of
them.
There
are
these
videos
on
YouTube.
Yes,
there
is,
we
will
have
a
baseline
of
customizations
in
roadmap
like
defining
zones
where
we
put
web
parts
and
so
on.
Yes,
so
that's
not
explicitly
said
again
this
forcing
the
responsibilities
of
our
internal
engineering
teams.
So
technically
the
beige
isn't
part
of
the
SharePoint
framework
but
obviously
and
we're
working
as
a
shipment
engineering
to
make
sure
that
you
can
have
multiple
different
layouts
on
the
morning
basis
as
well.
B
B
And
recommending
getting
a
bit
a
share
time
to
do
your
VMs,
so
you
have
a
first
experience.
Yeah,
that's
that's
true
as
well,
so
it's
not
a
bad
idea
to
use,
let's
say
a
VM
in
nature
to
pull
down
the
de
packages,
so
have
a
clean
machine,
which
is
how
to
make
that
happen.
We
do
have
at
the
video
where
which
is
recorded
but
I'm,
showing
how
to
set
up
your
development,
employments
I'm
using
a
completely
clean
windows,
10,
environment
and
I.
B
When
should
we
expect
a
preview
to
be
available,
I
would
say
rather
weeks
and
months,
but
pretty
soon
now,
I
cannot
give
you
a
date.
So
if
the
video
on
YouTube,
so
we
do
have
a
kms
link
for
that
one
as
well
a
kms
SPP
and
be
videos.
It's
our
SharePoint
development
media
channel
under
the
BMP
emperor
PMP
umbrella
does
actually
nowadays
mean
all
of
our
development
items
in
the
shipment
engineering.
So
you
can
easily
access
those
videos
as
well
just
double,
check,
link
and
I'm,
not
missing
anything.
B
Do
you
say
something
about
not
needing
to
install
an
extension
type
on
side
by
side
pieces
or
did
I
miss
that
good
question
from
Leo?
So
right
now,
when
we
go
to
the
Deaf
preview,
you
need
to
install
those
1.1
on
on
the
side
to
be
able
to
have
that
extension
available
within
the
slide.
We
do
understand
absolutely
that
that's
not
an
optimal
situation
if
you
need
to,
if
you
have
hundreds
of
thousands
of
site
collections
and
all
of
that,
so
we
need
to
get
that
one
solved.
B
It
is
absolutely
in
our
roadmap
to
make
that
model
more
simpler
part
of
insurance.
What
stops
me
for
updating
JavaScript
on
my
CDN,
which
is
associated
to
the
application
customizer,
so
that
the
new
model
gives
the
registration
of
tears,
which
goes
through
ten
on
administrator,
but
what
stops
the
chase
implantation
being
subsequently
changed?
Now,
theoretically,
nothing!
So
you
can
actually
and
that's
one
of
the
things
why
we
had
a
well.
We
did
had
a
webcast
related
and
organizational
considerations
and
administrative
considerations.
B
One
of
the
key
points
within
the
webcast
was
that
you
need
to
understand
where
your
customizations
are
being
hosted
and
they
still
a
standard.
This
contractual
situation
on
that
now
technically,
when
you're
creating
a
new
version
of
a
ship
on
framework
or
modifying
JavaScript
and
bouncing
bundling
a
new
version
of
your
SharePoint
framework
solution,
you
actually
do
get
a
new
cover
up
available.
We
are
having
the
JavaScript
implementation
and
file
again.
B
But
I
could
say:
hey
I
want
to
actually
my
JavaScript
implementation
and
for
us
to
be
renamed
as
part
of
this
new
version
used
existing
names
and
and
the
things
would
be
still
intact
cute
because
the
data
is
stored
in
my
subscribe,
so
is
so
critical
for
building
engaging
web
application.
Today
we
announced
in
it
yes
the
graph
HTTP
client
services
in
creve.
So
that's
what
kind
of
attached
that
one
I
think
the
post
question
from
Chris,
but
it
is
the
open
ID
connect
which
is
now
enabled
within
the
office
365.
B
So
in
your
SharePoint
framework,
you
can
request
well
in
your
travele
crypt
implementation.
You
can
request
an
access
token,
which
you
can
use
to
get
access
on
additional
services
in
SharePoint
in
office
365.
In
the
SharePoint
framework.
We
will
give
you
a
craft,
HTTP
client,
so
don't
actually
need
to
do
now,
any
additional
loops
and
stuff
to
get
that.
Get
that
access
token
and
then
you're
able
to
call
certain
craf
endpoints
and
to
get
access.
B
Undone
we'll
start
with
the
subset
of
scopes,
and
so
it
will
be
a
subset
of
things
but
as
I
sort
of
things
exposed
from
the
from
the
craft,
but
we'll
get
better
on
the
will
add
additional
scopes
on
the
on
the
permissions
as
we
move
along
and
the
custom
API
is
the
custom
8.
The
eyes
with
the
access
token
were
is
in
the
roadmap,
the
webcast
which
we
went
released
this
week
and
showing
how
to
call
a
custom
web
api,
but
not
with
an
access
token,
but
in
a
security,
but
not
with
the
next
token.
B
B
B
Good
we're
getting
there
and
we
are
hearing
by
the
way
on
the
hour
as
well,
so
not
that
many
questions
that
I
think
we're
going
through
the
craft,
cool
I
think
it's
time
to
close
up,
but
hopefully
an
interesting
webcast
and
awesome
updates.
Absolutely
super
excited.
We're
super
excited
in
engineering
to
be
able
to
actually
talk
about
and
there's
things
as
well,
because
we
be.
We
know
that
you
have
been
asking
this
one
and
these
capabilities
already
for
a
long
time.
We
know
to
ask
we
understand
it
has
to
happen.
B
B
A
Awesome
stuff
thanks
very
thanks:
everybody
for
joining
the
call
I
think
it's
really
exciting.
Updates
it's
going
to
be
really
exciting.
Once
we
can
get
those
out
the
dev
preview,
so
folks
can
start
playing
with
them.
I've
played
with
them
a
little
bit
really
cool
stuff,
really
exciting.
Thanks
peso
for
the
time
and
the
great
demos,
and
thanks
to
all
of
you
for
joining,
see
you
guys
on
May
25th,
bye,
bye,.