►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 2nd of August. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
Cool demo on local development of Azure Functions to consume third-party API and connect a SharePoint Framework web part locally.
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group
biweekly
meeting
it
is
August,
2nd,
2018
I
can't
believe
it
is
already
August
summer
is
rapidly
escaping.
So
let's
jump
right
into
our
call
here
today,
so
this
is
just
to
sort
of
frame
what's
going
on
for
folks,
that
might
be
new
to
the
call
or
new
to
listening
to
the
recordings,
we're
a
part
of
the
larger
SharePoint
patterns
and
practices
program
and
the
reason
we
started.
These
special
interest
group
calls
is.
We
were
really
a
victim
of
our
own
success.
A
A
Alternating
special
interest
group
calls
this
one
is
the
client
side
development,
one
which
is
focused
very
much
on
SharePoint
framework
and
the
client
side
development
patterns
associated
with
SharePoint
framework,
as
well
as
the
PJs
libraries
that
we've
all
worked
on
together,
building
as
a
community
and
then
anything
else,
client-side
development,
/,
SharePoint
related,
so
whether
that's
doing
stuff
in
a
script
editor
web
part
we've
seen
some
cool
demos.
There
or
doing
some
other
kind
of
client-side
solutions
around
now.
Excuse
me,
for
example,
like
the
column,
format
or
work,
and
things
like
that.
A
So
we
really
are
focused
more
on
that
and
then
alternating
with
these,
we
do
have
the
PowerShell
and
core
components
special
interest
group,
which
is
the
opposite
Thursdays
from
this
meeting.
You're
of
course
welcome
to
join
one,
or
all
of
these
calls
we
love
having
folks
join
the
calls,
but
that
one
will.
The
other
call
will
focus
a
little
bit
more
on
the
power
show
a
little
bit
more
on
the
core
core
power.
Sorry
Wow
core
patterns
and
practices,
see
some
components
and
give
you
a
little
bit
more
focus
there.
A
A
A
So
moving
into
this
week's
agenda,
well
real
quick,
any
chat
or
team
channels
around
PNP,
like
teams
or
discord,
we
do
have
a
couple
different,
get
ur
channels
for
the
PJs
component
as
well
as
the
office.
365
CLI
has
a
gator
channel,
but
we
don't
really
have
other
team
channels
that
we
maintain
as
such.
So
really
the
tech
community
and
the
threads
there
are
are
kind
of
that
sort
of
thing,
and
a
bit
of
that
is
just
honestly
the
time
it
takes
across
all
these
things
to
maintain
them.
A
A
There
he's
going
to
show
us-
and
we
may
have
a
little
bit
of
time
at
the
end
for
Q&A,
we'll
see
how
the
rest
of
the
meeting
goes
so
jumping
right
in.
We
always
like
to
start
off
with
opportunities.
People
ask
us:
how
can
I
get
involved
in
patterns
and
practices
or,
more
specifically,
how
can
I
get
involved
in
the
SharePoint
framework
or
JavaScript
special
interest
group?
A
The
best
way
to
get
involved,
or
my
favorite
way
for
folks
to
get
involved,
is
for
you
to
demo
something
you're
working
on
so
demo
in
a
SharePoint
framework
solution.
It
could
be
a
web
part,
it
could
be
an
extension
could
be
a
lot
of
different
things.
You
can
do
a
SharePoint
framework
now
demoing
something
with
the
PM
pjs
libraries.
A
combination
of
the
two,
of
course,
is
great,
but
I
find
the
demos
to
be
one
of
the
more
valuable
parts
of
the
call,
because
we
really
get
to
see
some
of
the
awesome
work.
A
Excuse
me
having
a
real
allergy
attack
this
morning,
to
build
up
solutions
for
your
customers
and
I,
know:
I,
see
something
new
and
different
and
cool
every
time.
Somebody
does
a
demo
and
we've
seen
some
really
amazing
stuff.
On
the
calls
and
I
know
a
lot
of
you
out.
There
are
working
on
really
amazing
stuff
of
your
own,
so
it
would
very
much
invite
you
to
demo
those
things
on
the
call.
So
if
you
want
a
demo,
all
you
have
to
do
is
reach
out
to
myself
or
vasa.
A
Twitter
is
a
great
way
to
do
that
and
we'll
get
you
on
the
agenda
for
an
upcoming
call.
It
might
not
necessarily
be
the
immediately
next
upcoming
call,
but
we'll
definitely
get
you
on
the
agenda
and
I
would
love
to
have
anyone
out
there
who's
interested
in
doing
a
demo
just
get
in
touch
with
us
and
we'd
love
to
have
you
as
well.
You
can
always
contribute
on
github,
so
contribute
on
github
takes
in
a
couple
different
shapes.
One
of
those
is.
You
can
obviously,
of
course,
contribute
code.
A
We
accept
pull
requests
across
all
the
the
pnp
projects,
not
just
p.m.
PJs,
but
everything
the
PMP
team.
Does
we
accept
pull
requests
there
as
well
contributing
can
include
reporting
issues
you
might
find
with
any
of
the
libraries
or
SharePoint
framework
itself,
always
appreciate
hearing
those
issues
and
working
to
solve
them,
because
it
makes
things
better
for
everybody
and
then,
finally,
you
can
always
provide
feedback,
so
it
might
not
necessarily
be
feedback
on,
for
example,
an
issue
with
the
library
it
might
just
be
feedback
on
the
calls
or
feedback
on
samples
or
things
like
that.
A
We
always
appreciate
that
feedback.
We
can't
necessarily
act
on
it
always
immediately,
but
we
do
very
much
appreciate
it.
We
do
very
much
take
it
to
heart
when
you,
when
you
take
the
time
to
give
us
feedback,
we
do
listen
and
we
do
our
best
to
change
and
adjust
and
grow
and
learn
from
that
feedback.
So
please
keep
that
coming
so
updates
this
week,
you'll
be
hearing
from
me
for
the
SharePoint
framework
update
as
Vasa
is
still
on
vacation.
A
So,
as
always
documentation
and
guidance,
you
can
find
that
the
SPD
dev
Doc's
akms
link
we've
got
a
new
platform,
we're
working
on
or
it's
a
new
back-end
platform
for
all
the
SharePoint
development
documentation,
we're
working
to
move
all
of
the
SharePoint
development
topics
to
this
location.
So
this
link
hasn't
changed,
just
sort
of
the
backend
platform
and
layout.
We
hope
it's
a
lot
clearer
for
folks
to
see
there.
A
Obviously
lots
of
views
folks
are
hitting
this
documentation,
which
is
great,
and
we
are
managing
this
content
in
github,
but
it's
still
surfaced
at
Docs
up
Microsoft
comm,
slash
SharePoint.
So
again
the
backend
changes,
hopefully
invisible
to
all
of
you,
but
the
front-end
changes
hopefully
have
made
things
a
little
bit
easier
to
find
and
a
little
bit
clearer
does.
This
include
class
documentation,
it
may
I
haven't
looked
in
a
little
bit.
If
it
doesn't,
it
will
so
we're
working
on
moving
things
over
there.
A
Excuse
me
and
then,
as
always,
if
you're
running
into
issues
with
SharePoint
framework
or
office,
365
SharePoint
online
service,
you
can
always
report
those
bugs
there's
a
link
there.
Sp
dev
issues
will
take
you
to
the
SP
dev
Doc's
repository,
which,
despite
the
name,
is
actually
the
issues
list
for
reporting
all
potential
bugs
with
the
SharePoint
SharePoint
framework
or
SharePoint
online
service.
If
you
think
you've
found
a
bug
with
the
service,
something
was
working
and
now
isn't
things
like
that
love
to
hear
those
get
those
reported.
A
Those
are
all
triaged
twice
a
week
and
are
worked
through
just
as
fast
as
folks
can
do
it,
and
this
again
started
with
SharePoint
framework
was
expanded,
of
course,
as
a
place
to
report
other
critical
bugs
around
the
SharePoint
online
service.
So
we'll
do
our
best
to
respond
there
and
as
well
to
redirect
you
if
there's
a
better
place
to
report
a
certain
issue
with
the
service,
but
do
if
you
are
seen
issues
please
do
report
them.
Don't
just
keep
it
to
yourself
because
it'll
never
get
fixed.
A
A
You're
building
and
then
on
the
tenants
as
well
we're
seeing
tenants
doing
more
and
more
deployments
of
what
we're
finding
or
of
SharePoint
framework
of
what
folks
are
putting
out
there.
The
usage
continues
to
grow
for
those
things
so
roadmap
for
calendar
year
2018,
as
always,
disclaimer
preliminary
plans.
These
are
always
subject
to
change
so
spring.
A
lot
of
stuff
spring
has
kind
of
already
happened.
So
now
we're
under
the
summer
fall.
A
I
won't
read
through
the
whole
list
here,
but
the
big
one
is
SharePoint
framework
1.6
looking
to
do
that
mid-august
so
that'll
be
another
version
bump
for
the
SharePoint
framework.
The
big
things
coming
there
is
going
to
be.
The
native
graph
access
will
hopefully
finally
be
sorted
and
go
to
GA
and
then
as
well.
Some
things
around
dialog
framework
and
updating
to
react.
16,
which
I
know,
has
been
a
big
thing
for
a
lot
of
folks.
Getting
react.
16
support
in
there
as
well
as
some
SharePoint
2019
support,
will
be
rolled
into
the
SharePoint
framework.
A
1.6
I
don't
have
details
on
exactly
what
that
will
look
like
yet,
but
that
is
all
coming
and
then
the
next
sort
of
planned
version
bump
would
be
around
ignite
2018,
which
is
going
to
be
the
framework
1.7.
So
looking
for
that'll
be
the
next
big
version
bump
after
this
one
coming
hopefully
mid-august
does
that
include
a
ad
HTTP
client
I.
A
Imagine
you're
talking
about
the
native
graph
access
that
will
include
some
flavor
of
a
ad
HTTP
client
I'm,
not
certain
exactly
how
they're
gonna
release
that
at
this
point,
but
it
will,
it
will
evolve
that
kind
of
capability,
global
deployment
is
being
able
to
automatically
deploy
and
activate
extension,
such
webparts
on
all
site,
collection,
I,
don't
think
activate,
necessarily,
but
definitely
a
global
deployment.
They
may
roll
activation
in
there,
but
I'm
not
aware
of
that.
So
I
don't
think
for
sure
that
that
is
going
to
be
part
of
what's
coming
out.
A
So
then,
so
updates
as
well
on
the
starter
kit,
so
demonstrating
end-to-end,
modern
experiences.
If
you
haven't
checked
out
the
SharePoint
starter
kit,
it
is
a
great
way
to
sort
of
without
sort
of
self
referential
starting
an
intranet.
So
it
gives
you
some
great
examples
on
how
to
provision
and
then
how
to
style
and
then
how
to
produce
some
of
these
custom
web
parts
that
are
commonly
asked
for
importance
so
working
on
gradual
updates.
A
This
is
a
community
effort,
the
SharePoint
starter
kit
so
separate
from
the
SharePoint
engineering
updates,
but
this
does
demonstrate
some
end
to
end
modern
experiences.
So
it
is
again
a
community
building
so
constantly
improving
the
documentation
working
on
that
working
on
demos
for
each
web
part
and
then
as
well.
Improving
the
web
parts
and
extensions
and
again
that's
all
gradual,
slow
work
as
folks
have
time.
A
That's
a
place
if
you'd
like
to
contribute
like
to
jump
in
you
could
definitely
do
that
and
then
some
of
the
more
long-term
steps
for
targeting
around
ignite
again
sort
of
tying
into
the
ignite
timeframe,
self-service
web
site
to
automatically
provision
things.
So
that's
something
we're
looking
at
providing
as
well
support
for
different
open
source
content,
packs
and
then
support
for
overriding
configurations
inside
the
starter
kit
so
which
themes
which
web
parts
things
like
that
around
the
starter
kit
deployments.
A
A
A
Will
the
requirement
for
first
release
tenants
stay
for
the
starter
kit
for
now?
Yes,
simply
because
it
uses
some
of
the
first
release
capabilities,
but
as
those
things
start
to
roll
out
to
GA,
I
think
I.
Think
please
don't
come
for
me
if
I'm
wrong
on
this,
but
I'm
pretty
sure
the
release
of
1.6
will
will
be
everything.
The
starter
kit
needs
so
will
now
no
longer
be
first
released.
Tenants
I
think
that
is
going
to
be
the
case,
so
that
should
help
with
the
starter
kits
on
non
first
release:
tenants.
A
Will
there
be
a
new
integration
with
teams
as
skype?
Sunsets
I
cannot
give
you
any
details,
but
yes,
there
will
be
new
integrations
with
teams
coming.
Things
are
in
the
works,
but
nothing
I
can
talk
about
publicly
right
at
this
moment.
Steve
very
sorry
to
be
cryptic
on
that.
But
yes,
stuff
is
coming
up.
Oh
got
a
great
echo
there,
so
just
remember
to
find
her
mute
there.
We
go
so
do
remember,
joint
on
mute
when
you
jump
into
the
calls
really
helps
us
with
the
recording,
so
updates.
A
Yeah
I
think
I
got
all
the
questions
so
updates
on
the
PP
client-side
libraries.
Next
release
is
gonna,
be
August
3rd.
That
is
actually
tomorrow.
For
those
of
you
checking
out
the
calendar,
do
you
remember,
patterns
and
practices?
Sp
taxonomy
has
been
released,
give
it
a
try.
It's
a
great
way
to
have
a
fluent
API
to
talk
to
the
taxonomy.
A
We
did
just
fix
a
book,
so
it
was
kind
of
a
good
find
we
had
that
submitted
as
an
issue
got
that
fix,
that'll,
be
in
the
release
on
August
3rd,
so
do
give
the
taxonomy
stuff
a
try.
I
would
love
to
hear
the
feedback
from
folks
using
that
how
we
can
continue
to
improve
and
grow
that
the
libraries
have
been
published
to
see
dnj,
so
you
should
be
able
to
use
those
and
access
those
as
well,
and
one
thing
I
wanted
to
bring
up.
A
So
if
you
are
having
trouble
with
the
CDN
stuff,
do
let
us
know
and
we'll
do
our
best
to
try
and
address
those
things.
Where
should
we
focus
next,
of
course,
always
looking
for
feedback
from
folks
on
the
kind
of
things
we
can
add
to
the
library
or
how
we
can
best
expand
the
library
or
enhance
the
library
to
make
everybody's
lives
easier?
That's
always
our
goal.
A
If
you
have
ideas,
you
would
like
to
contribute
we'd
love
to
hear
those
as
well
absolutely
welcome
your
pull
requests
and
your
contributions
back
to
the
library
is
a
great
way
to
get
involved
and
would
love
to
have
those
as
well
about
getting
involved.
I'm
looking
for
folks
to
help
with
samples
and
help
with
the
documentation,
one
of
our
pretty
much
consistent
pieces
of
feedback
is,
you
should
have
better
documentation.
A
We
do
try,
but
the
documentation,
I
think,
as
we
all
know,
as
developers
sadly
usually
gets
pushed
in
priority
for
fixing
bugs
and
helping
folks
with
their
other
issues.
So
we
are
looking
for
help
if
you
have
ideas
or
what
I
helped
make
the
documentation
better.
It's
all
there
in
the
github,
so
absolutely
welcome
help
with
that
and
would
very
much
appreciate
help
with
that.
It's
it's
just
hard
at
times
to
get
in
there
and
just
a
final
note,
I
feel
like
every
few
months.
A
We
just
have
to
remind
folks
of
this,
keep
your
feedback
and
your
issues
and
your
things
you
to
report
constructive,
we're
all
doing
our
best.
We're
all
doing
this
in
our
free
time,
and
it
is
something
we're
putting
out
there
into
the
community
for
free,
so
sort
of
showing
up
and
kind
of
having
a
less
than
collaborative
attitude,
isn't
necessarily
the
best
way
to
approach
reporting
an
issue
or
approach
the
library
love.
The
feedback
love
to
hear
from
folks
love
to
try
and
help
folks
and
get
things
fixed,
but
do
keep
things
constructive.
A
Do
keep
things
in
the
vein
of
we're
all
trying
to
work
to
make
things
better
for
everybody.
So
if,
if
you
find
a
problem
with
the
library
or
find
a
bug,
it's
certainly
not
something
we
put
there
on
purpose.
We'd
love
to
hear
about
it.
We'd
love
to
hear
ideas
on
how
to
make
things
better,
but
do
keep
that
constructive.
Do
keep
that
civil,
but
do
let
us
know
we
love
to
have
that
feedback
yeah.
The
rabbits
are
growing
people.
A
People
are
noticing
so
links
down
there
at
the
bottom,
P
and
P
github
I
owe
slash
P
and
PJs
gets
you
all
the
documentation
for
P
and
PJs
libraries.
You
can
follow
the
hashtag
PJs
on
Twitter
and
you
can
always
follow
me
at
mediocre.
Bowler
on
Twitter
I,
don't
post
a
ton
of
stuff,
so
you
won't
get
a
lot
of
spam
for
me,
but
it'll
be
updates
around
the
p.m.
PJ's
libraries
releases.
Things
like
that
interesting.
A
You
know,
retweets
of
stuff
people
are
doing
in
the
community.
So
follow
me
we'll
do
our
best
will
I
be
hosting
any
meetings
or
sessions
at
ignite
I
Patrick
personally
will
not
at
this
time
be
at
ignite,
but
I
think
the
vase
will
be
there
and
there
will
be
some
PNP
activities
at
ignite
so
we'll
see,
but
as
we
get
closer,
we'll
update
folks
with
what's
actually
going
on,
you
know
with
P
and
P
and
ignite
so
have
a
little
bit
more
explicit
schedule.
A
So
this
week
this
was
gonna
be
two
weeks
ago,
but
I
wanted
to
talk
about
a
little
bit
a
brief
history
of
SPP
and
PJs.
So
this
is
the
library
that
started
all
of
the
client-side
development
inside
patterns
and
practices
so
again
separate
from
SharePoint
framework
inside
patterns
and
practices.
We
had
way
back
when
before
SharePoint
framework
was
released.
A
So
the
way
to
go
now
is
we're
not
stopping
with
our
client-side
development,
but
we
are
very
much
encourage
you
to
migrate
to
the
new
p.m.
PJs.
Libraries
got
I
think
a
lot
of
improvements.
There
we've
got
a
little
bit
better
model
there.
It's
been
updated
with
I
know
a
lot
of
my
learnings
and
I
know
a
lot
of
our
learnings
as
a
as
a
whole,
as
a
community
have
gone
into
those
new
libraries
and
then
that
graph
there
I
think
is
really
cool
and
I
think
really
shows
off.
A
So
it's
really
a
community
success
that
I'm
I'm
very
proud
and
happy
to
have
been
a
part
of
and
I
hope
you
are
as
well
just
a
little
bit
some
other
facts.
We
started
this
as
a
way
again
before
SharePoint
framework
was
released.
Some
of
you
that
were
here
back
at
the
beginning,
remember
when
we
started
these
calls,
we
kind
of
had
a
lot
of
cryptic
hey.
A
You
might
want
to
learn
this
kind
of
messaging
without
a
lot
of
details,
and
it
wasn't
always
clear
necessarily
why
we
were
telling
you
to
learn
this
or
why
we
were
trying
to
move
forward.
You
know
some
of
these
technologies
or
why
we
were
pushing
things
and
then
I
think
a
lot
of
folks
had
a
kind
of
aha
moment
when
SharePoint
framework
came
out
and
realized,
we
tried
been
trying
to
lay
the
groundwork
for
that.
So
we
started
this.
It
was
a
bit
of
a
preparatory
exercise
for
SharePoint
framework.
A
The
library
really
provided
a
fluent
API
for
SharePoint
rest,
while
wrapping
up
a
lot
of
the
common
operations
that
folks
do
every
day,
I
think
it's
been
a
really
valuable
exercise.
I
think
it's
really
helped
a
lot
of
stuff
and
made
things
a
lot
easier
for
folks
as
well.
We
expanded
over
the
years
over
the
years
of
maintaining
the
library
to
support
graph
to
support
expanded
nodejs
support.
We
commented
or
focus
down
on
a
common
request
pipeline
between
all
the
libraries
of
graph
and
SharePoint
use
that
common
pipe
and
then
as
well.
A
So
again,
I
can't
emphasize
enough
how
much
this
was
a
community
success
growing
this
that
all
of
us
had
a
stake
in
and
really
helped
build,
and
then
it
served
as
the
foundation
for
the
PJs
work
which
continues
moving
forward.
So
we're
not
done
developing
libraries.
We've
just
moved
over
to
the
new
libraries
that
I
mentioned
a
little
bit
earlier
on
the
previous
slide
and
that
again
we're
still
working
and
corporated
the
feedback
from
the
community
and
our
learnings
there
and
to
really
the
goal
is
always
to
make
things
better
for
everybody.
A
So
if
you've
been
using
SPP
and
PJs
I
just
want
to
say
thank
you,
but
please
do
start
to
migrate,
move
over
to
PN
PJs
libraries.
Let
us
know
your
feedback
help
us
grow
and
make
those
better
in
the
way
that
we've
all
worked
together
to
make
the
SPP
PGS
library
great.
So
it's
been
quite
a
journey
and
the
last
thing
I'll
say
on
that
is
just
thank
you.
So
that's
a
thank
you
to
everybody
out
there.
A
Who's
listening
and
the
heavens
just
opened
up
here,
so
you
might
hear
a
little
background
noise
of
the
rain
hitting
my
metal
roof.
But
thank
you,
everybody
out
there.
It's
been
great
and
look
forward
to
continuing
the
journey
with
the
PPG
libraries,
with
all
of
you
in
the
same
vein,
so
we'll
keep
up
the
great
work
and
thank
you
again
to
everybody.
So
really
can't
say.
Thank
you
enough.
It's
been
quite
rewarding
to
be
part
of
this.
A
Alright
enough
gushing.
For
me,
let's
go
check
out
the
office
365
CLI
updates,
we've
got
the
new
beta
version
of
1.5.0
is
out
that
has
just
added
support
for
managing
content
types
fields,
navigation,
nodes,
client-side,
webparts,
listing
columns
as
well
as
updating
site
properties.
So
you
can
check
that
out
today
in
that
beta
version
and
then
as
well
still
working
on
getting
support
for
more
SharePoint
framework
versions
for
the
upgrade
do
cross
platform.
Pnp
starter
kit
set
up
script,
so
the
there
would
be
a
way
to
to
set
up
your
PMP
starter
kit
cross-platform.
A
So
you
wouldn't
be
tied
in
as
much
to
like
PowerShell
approach
and
then,
of
course,
always
looking
for
more
commands.
And
then
you
know
the
feedback
as
well
to
drive
this
CLI
development.
What
commands
can
be
improved
or
added
to
there,
so
you
can
always
install
the
latest
version
from
NPM
using
the
dash
G
at
PNP
office,
365
CLI
command,
more
information
at
aka,
MS,
Office,
365
CLI.
You
can
follow
on
the
hashtag
office,
365
CLI
on
Twitter
there's
as
well.
A
git
er
channel
there
officer,
c5,
CLI
and
the
docs
are
at
that
AKA.
A
A
So
no
I
don't
think
that's
in
there,
so
reusable
SharePoint
framework
controls.
So
these
are
some
great
controls
that
if
you
haven't
checked
these
out,
make
your
SharePoint
framework
development
experience
a
little
better
in
two
ways.
The
first
way
is
a
set
of
react
controls
you
can
use
in
the
body
of
your
webparts,
so
some
enhancements
so
version
1.6,
0.7.
A
Insights
and
then
as
well
a
disabled
property
for
the
people,
picker
has
been
added,
so
you
can
enable
and
disable
the
people,
people
picker
control
and
then
fixes
the
people.
Picker
property
selected
items
has
been
fixed,
so
that
was
a
bug
number
90.
The
issue
that
had
been
approached
so
those
controls
are
fantastic,
use
them
right
in
the
body
to
extend
your
SharePoint
framework
webparts.
A
Those
are
built
on
of
the
react,
UI
framework
control,
so
you're
gonna
get
the
same,
look
and
feel
that
you're
used
to
out
of
the
UI
framework
so
check
those
out
or
I'm.
Sorry,
the
UI
fabric,
not
framework
UI
fabric,
so
check
those
out
really
speeds
up.
Your
development
could
save
you
a
lot
of
time
for
a
lot
of
commonly
used
controls
and
then
the
second
way
is
for
helping
you
out
with
property
control.
So
these
are
controls
you
would
use
in
your
property.
Pane
is
to
help
with
when
you
go
into
edit
mode.
A
Folks
can
use
these
controls
to
give
you
a
better
webpart
editing.
The
experience
and
version
1.8
has
just
been
released.
So
again,
the
new
telemetry
approach
has
been
added
here
as
well,
and
then
the
property
field
list
picker
and
optional
property
for
target
sites
has
been
added
to
the
property
of
the
I'm.
Sorry
I
said
that
sentence
really
terribly.
The
optional
property
for
target
sites
has
been
added
to
the
property
field
list
picker,
so
you
can
check
that
out
as
well.
A
More
information
is
always
there
at
those
two
links
on
the
github
sites
for
those
and
these
are
again
open
source.
So,
if
you'd
like
to
contribute-
or
you
find
an
issue,
please
do
submit
your
contribution
as
a
pull
request
or
report
your
issue
there
in
the
issues
list,
does
the
People,
picker
properties,
post
people's
picture
or
pickles
I,
believe
it
posts
the
collection
of
just
the
properties
of
that
picked
person
right
like
the
login
name
or
the
ID,
pickles
pepper,
okay,
so
now
ready
to
step
into
a
great
demo
from
Stephan
Stephan.
B
Embed
video
them
to
your
sharepoint
site
would
be
a
great
tool
this
now,
then,
what
I
came
to
that
is
so,
should
I
really
write
in
the
B
meal
access
directly
through
to
my
back
part
or
should
I
use
something
else
like
an
Asia
function.
So,
for
example,
if
the
client
application,
ID
or
the
client
secret
changes,
I
have
to
redeploy
to
that
part.
B
But
this
is
something
I
simply
cannot
press
in
the
Asia
function
configuration
so
when
some
when
I
need
to
change
something
that
to
access
the
third
party
API,
it's
a
safer
place
to
have
it
in
Asia
function
and
all
web
parts
access
the
API
through
this
Asia
function.
Instead
of
have
all
your
code
inside
the
web
part
and
then
I
thought
to
myself.
Okay,
I
can
go
up
to
the
Asia
portals
that
the
Asia
function
right
there
and
start
to
develop
directly
on
the
edge
of
horrible.
B
B
What
I
used
what
I
installed
first
on
my
client
was
the
asia
function
cup
tools,
because
this
allows
you
to
create
y&z
CLI.
All
the
asia
functions
locally
on
your
computer
and
actually
mimic
the
all
the
functionalities
of
an
asia
function,
and
this
was
the
first
thing
I
installed
and
then
a
follow
to
tutorial.
So
when
I,
when
you
look
over
to
the
to
the
sample
here,
are
in
the
SPF
death
FX,
where
part,
so
you
see
the
vimeo
request
year.
B
B
So
let's
take
a
look
at
the
code,
so
what
you
have
here
is
in
your
local
settings
of
chasing.
This
is
actually
the
equivalent
to
the
application
settings
that
you
have
in
Asia,
so
you
can
put
in
here
the
Vimeo
secret
and
you
can
have
the
Vimeo
endpoint,
and
one
thing
that
was
required
is
that
I
created
a
certificate
because
by
default,
this
Asia
function
run
on
HTTP
but
to
access.
The
Asia,
the
local
Asia
function
have
to
turn
the
Asia
function
to
HTTPS,
and
this
is
also
included
in
this
configuration.
B
B
B
When
Alice
started
to
develop
or
actually
try
to
take
a
look
at
the
venire
website,
what
it
this
website
offers
for
developers,
I
found
no
chess
and
as
an
official
supported
library,
so
I
wrote
all
my
Asia
function.
Basically
all
in
JavaScript
and
no
chess
was
was
for
me,
the
next
step
to
do
so.
I
actually
installed
here.
The
Vimeo
client,
which
is
currently
the
version
2.0
point
two
and
I
have
simply
here
an
index
file,
and
this
is
the
complete
Asia
function.
So
what
it
does
it
here?
You
you
create
them.
B
You
pass
in
the
Vimeo
API
key
and
the
secret.
Then
you
log
in
with
a
to
scope,
which
is
publix.
So
this
allows
me
to
actually
query
all
the
public
available
videos
from
Vimeo.
So
if
you're
an
organization
that
has
published
all
your
videos
there,
then
you
actually
have
to
switch
the
scope
a
little
bit
that
you
might
be
able
to
access
videos
that
are
not
listed
on
the
mail
publicly.
B
B
So
let's
search
for
a
video,
for
example
here
and
take
a
look
at
what
happens
here
in
the
Asia
function.
So
I
just
simply
pass
in
a
query
that
says
hello
world
and
now
it
goes
to
Vimeo
and
actually
returns
all
the
results.
All
videos
that
have
been
found
with
hello
world
back
as
of
jason
12-
and
you
see
also
here
how
this
is-
requests-
have
been
sent
out
to
the
vanilla
api.
B
B
B
And
then
first
show
you,
the
back
part
have
is
there's
all
words,
so
this
actually
has
two
parts.
So
one
part
is
you
can
edit
all
your
or
you
can
search
Vimeo
for
four
videos
directly
inside
of
that
part,
so
I
here
once
loaded
here
to
Vimeo
and
search
for
example,
hello
world,
then
it
directly
search
just
the
platform
and
I
do
this
again.
B
So
I
cleared
the
the
search
result
and
now
search,
for
example,
Pemex
and
press
the
Search
button,
and
you
see
here
in
the
Asia
function
that
the
request
has
been
sent
us
through
my
Asia
function
to
the
third
party
API.
So
this
is
the
actually
the
list
of
videos
that
I
cut
back
from
the
from
Vimeo
and
in
here,
for
example,
I
can
say:
let's
I
want
to
use
this
video
I
want
to
see
this
video
I,
hope,
I,
muted,
other
words,
so
I
can
directly
preview.
The
video
in
here
and
I
say:
okay.
B
This
is
the
right
video
that
I
want
to
use
I.
Just
simply
press
this
button
say
use
this
video
and
when
I
open
up
the
the
web
part.
This
video
link
actually
has
directly
saved
in
here,
so
when
I
cannot
go
now,
we
always
have
in
in
the
workbench
the
possibility
to
preview
the
video
and/or,
how
it
looks
then,
under
on
the
edit
mode,
you
directly
see
the
video
how
it
will
be
embedded
on
the
page
directly.
Okay,.
B
So,
from
a
coding
perspective,
what
I
created
is
a
simple
web
part
you
see
here,
and
this
dot
display
mode
is
actually
a
representation
where
I
can
identify
if
I'm,
currently
in
the
edit
mode
so
like
we
are
used
to
using
in
the
old
in
the
classic
experience.
So
when
the
display
mode
is
actually
set
to
true,
then
it
returns
true
or
otherwise.
It's
false,
so
I
pass
in
here,
for
example,
the
Vimeo
or
the
HTTP
client
the
unsaved.
B
So
the
first
thing
actually
that
gotta
load,
that
is
here
the
video
happy
meal
client,
so
I
can
hear
a
check
when
I'm
in
edit
mode,
then
please
show
the
search
and
I
feel
another
control
that
is
actually
called
here
in
your
search
and
this
one
meal
search
control.
We
a
control
just
consists
of
the
text
field
and
the
button,
and
when
I
click
the
button,
then
it
searches
the
video
and
what
you
see
here
in
the
search
video
it
actually
access
directly.
B
My
right
now,
my
local
Asia
function,
passing
the
search
value
or
the
return
that
has
been
entered
in
the
text
box
runs
the
query
and
then
returns.
Actually,
the
video
result
in
a
video
result
item
and
what
you
see
here
is
this
is
the
video
entry
that
actually
checks
the
Edit
State.
So
when
I'm
in
edit
State,
then
I
want
to
see
more
details
on
the
video.
Otherwise
it
just
renders
the
video-
and
you
have
there's
this
one
entry
in
the
list
and
the
F
here.
B
Actually,
the
video
player
well
only
took
the
iframe
embedding
that
the
meal
provided
me
for
their
player
yeah
and
that's
basically
all
components-
are
I
used
in
here.
So
the
rest
is
pretty
simple
but
relatively
simple
back
parts,
development
and
bypassing
in
the
edit
mode
I.
Can
it's
easy
to
identify,
hey
I'm
in
edit
mode
and
I?
Guess
the
experience
for
the
for
the
end
user
is
way
better
when
they
are
not
have
to
switch
the
context,
so
I
have
to
go
to
the
meal
search
for
the
video
copy.
A
Cool
as
really
also
demo
shows
a
lot
of
stuff
hooking
up
a
lot
of
different
stuff
and
stuff
on
will
be
pasty.
This
is
gonna,
be
up
on
github
and
we'll
have
the
link
included
with
the
when
we
post
the
video
but
as
well
I,
don't
know
Stephane.
If
you
have
that
handy
and
want
to
paste
that
now
into
the
into
the
chat
for
folks
to
go
check
that
out,
yeah
and.
B
I
mean
this
was
just
a
brief
overview
of
just
this:
the
where's,
my
hidden,
your
somewhere
yeah
yeah.
Actually,
this
is
the
demo.
What
this
way
you're
currently
find
the
demo-
and
this
was
just
a
brief
overview,
so
I
post
the
complete
story
here
on
my
on
my
blog,
which
is
a
three
part
series,
so
you
have
a
smart,
stupid
web
part,
one
where
I
just
explain
the
idea
that
I
explained
shortly,
then
how
you
set
up
this
Asia
function
and,
in
the
end,
how
you
develop
the
best
part.
A
B
A
B
A
Yeah
really
impressive
stuff
I
encourage
everybody
to
check
that
out,
so
we're
gonna
jump
back
to
the
slides
here,
as
always
others
for
my
folks.
If
you
would
like
to
demo
something
on
the
call,
please
just
get
in
touch
I
love
to
have
these
community
demos
I
think
it's
really
valuable.
We
get
to
see
really
amazing
stuff
like
this
and
like
a
lot
of
the
other
demos,
we've
seen
so
just
reach
out.
Thank
you
very
much
great
stuff
there.
So
we
do
actually
this
week
have
a
little
bit
of
time
for
Q&A.
A
B
A
A
So
SharePoint
framework
doesn't
support
or
not
support
redux.
That
would
be
a
decision
on
in
your
application.
If
you
choose
to
use
it,
you
you
can
and
SharePoint
framework,
really
wouldn't
care,
so
just
like
I
could
use
angular
or
knock
out
or
view
j/s
or
any
of
the
other
frameworks
within
SharePoint
framework.
If
I
chose
to
use,
react
and
then
I
chose
to
use
redux
with
react,
SharePoint
framework
really
wouldn't
know
or
care
right
that
would
that
would
really
be
in
in
inside
your
application.
A
A
Now
anybody
know
why
the
placeholder
footer
floats
around
on
iOS
devices
and
doesn't
dock
at
the
bottom
like
it
is
supposed
to
I
I,
don't
know,
but
that's
a
great
thing
to
drop
into
the
issues
list
for
that
SP,
dev,
Doc's
issues
list
and-
and
maybe
folks
can
take
a
look
at
that.
I
I
don't
have
any
special
insight
on
that
one.
A
No,
those
are
not
currently
public,
but
you
can
always
report
issues
in
the
issues
list
and
you
know
look
look
to
have
those
fixed
or
changed
or
enhanced
to
match
what
you're
thinking
about.
They
may
at
some
point
become
open-source,
but
there's
no
schedule
for
that,
and
so
right
now
you're
not
able
to
submit
a
pull
request.
There.
A
That's
back
to
the
redux
saying
now
that
the
ability
to
select
default
language
in
modern
sites
is
the
API
support
for
the
else'd
parameter.
Also
working.
Currently
it
takes
the
route
sites
default.
Language
I'll
tell
you
truthfully,
I,
don't
know
rough
top,
my
head,
if
that
parameter
and
the
API
is
working
or
not,
the
the
quickest
way
would
be
to
just
go,
give
it
a
try
and
and
see
I
know,
that's
not
a
great
answer,
but
that's
I
don't
know
off
the
top
my
head,
unfortunately,
as
my
answer
for
you
right
now,.
A
Jim
is
posting
this
issue.
Is
there
I'm
guessing
that's
the
floater
one
yeah,
that's
the
footer
one.
Okay,
yeah
I
wouldn't
have
any
information
beyond
what
would
already
be
in
that
issue,
or,
what's
that
so
we'll
the
PNP
commands
be
quickly
updated
support
language
and
the
new
template
STS
pound
three.
A
So
it
should
work
but
as
always,
we're
doing
our
best
as
an
open
source
project
update
things
quickly.
But
if
you
see
something
you
can
also
always
submit
a
pull
request
or
just
remind
folks
to
that.
So,
if
you
you
know,
are
coming
in
and
you
see
a
thing
that
maybe
a
command
needs
or
is
lacking
some
new
feature-
that's
come
out,
you
could
always
submit
a
pull
request.
Sometimes
you
know
we
on
the
core
team.
Don't
always
have
time
to
get
around
to
things.
A
A
Okay,
cool,
so
we
got
through
some
questions
any
more
questions,
if
not
we'll
go
ahead
and
close
out
just
a
little
bit
early
this
week
reminder
your
next
SharePoint
framework.
Java
Script
special
interest
group
meeting
is
gonna,
be
August
16th,
that's
in
two
weeks
and
your
next
general
SharePoint
dev
specialist
group
will
be
on
August
9th.
That
is
next
Thursday,
so
we
will
see
everybody
next,
a
Thursday.
Everybody
have
a
great
weekend,
and
you
know
we
love
love.
Having
everybody
calls
appreciate.
Everybody's
feedback
and
participation.
Thank
you,
Stefan
for
the
great
demo.