►
From YouTube: SPFx JavaScript SIG 12th of October, 2017
Description
Bi-weekly community call around SharePoint Framework and JavaScript development in SharePoint platform. This is recording from the 12th of October call. You can download recurrent invite from http://aka.ms/SPPnP-JSSIG.
A
Good
it's
time
to
start
so
we're
hitting
on
the
hour
and
depend
is
in
the
morning
or
evening
or
afternoon
or
night
time
for
your
location.
It
slightly
depends
obviously
where
your
settings,
but
anyway
welcome
everybody.
This
is
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meeting
or
a
sink
or
discussion.
This
is
October
12,
2017
edition,
and
at
this
time
it
will
be.
My
name
is
Wes
aluminum
I'm,
a
Senior
Program
Manager
from
ship
on
the
engineering
side,
so
my
team
is
responsible.
A
Among
the
other
things
on
the
SharePoint
frameworks,
we
ship
the
SharePoint
framework
as
part
of
our
deliverables
and
we
own
all
of
the
dev
api's
and
all
that
stuff
as
well
now,
but
the
quarters
who's
usually
leading
this
special
interest
group
and
this
community
caller
is
on
parental
leave.
So
he
has
a
pretty
good
reason
and
not
to
be
here
and
it's
good
that
he
is
not
joining
on
the
middle
of
that
vacation
time
and
concentrate
on
his
family,
so
I
will
be
leading
this
one.
A
We
do,
however,
have
three
different
demos
coming
up
on
this
session
as
well,
so
there
will
be
a
lot
of
other
people
presenting
during
the
session
as
well.
Now,
let's
get
on
going
on
the
thing
so
quickly
explaining
what
this,
what
the
special
interest
group
is
all
about,
so
the
SharePoint
Patterson
practice
is
SH
of
meaning
the
SharePoint.
That
ecosystem
owns
all
of
the
guidance,
samples
and
messaging
around
the
SharePoint
development
in
on-premises
or
within
the
SharePoint
Online.
So
the
PMP
is
its
kind
of
Lu.
A
It's
large
and
there's
a
lot
of
actions
happening
here,
and
this
is
a
special,
a
special
interest
group
around
the
SharePoint
framework
and
JavaScript
development.
So
this
kind
of
evidence
has
spin
off,
but
it's
a
pace
up
initiative
and
underneath
the
SharePoint
path,
largest
SharePoint
BMP
initiative,
and
so
the
whole
point
of
this
one
is
to
have
an
open
discussion
around
the
SharePoint
framework
and
client-side
development
patterns
and
always
have
also
SharePoint
engineering
people
in
place.
A
A
Check
there
we
go
if
we
can
get
checks
on
them
on
the
presentation
as
well
good.
So
so
in
this
special
interest
group
originally
in
the
BMP,
we
had
a
monthly
community
course
and
and
pretty
fast.
We
realized
that
having
those
monthly
community
costs
on
a
monthly
basis
isn't
actually
good
enough.
There
has
to
be
a
forum
where
people
can
have
more
open
discussions,
do
demos
and
all
that.
A
So
that's
when
we
started
the
special
interest
groups
and
for
we
have
two
of
them,
so
we
have
a
one
for
SharePoint
framework
and
JavaScript
development
and
one
for
the
general
SharePoint,
deaf
and
provisioning
and
powershell
science.
So
and
all
of
the
meetings
are
always
on
Thursday
dat
Thursdays
at
7
a.m.
Pacific
time,
and
we
do
know
that
it's
it's
matter
of
these
time
zones
that
it's
not
suitable
for
some
people
and
it
might
be
suitable
for
some
people.
A
We
also
recommend
all
of
these
sessions,
so
people
can
actually
watch
this
in
the
YouTube
and
later
on,
as
well
now
to
in
today's
agenda
and
we'll
have
a
look
on
the
latest
on
the
PM
PHAs
core
site.
So
that
is
the
open
source,
VM
PHAs
core
component,
which
we
started
developing
back
in
one
and
a
half
years
ago,
and
that
one
actually
provides
a
nice
fluent
API
on
top
of
the
ship
and
wrist
API.
A
So
you
don't
have
to
understand
and
remember
what
is
the
rest
HDD
Beatrice's,
you
can
use
the
PM
PM
PHAs
core
and
which
will
increase
your
productivity
again
completely
optional
and
it
doesn't
have
to
you.
Don't
have
to
do
that,
but
that's
one
of
the
things
which
are
providing
the
PNP
as
well.
So
now
we
provide
reusable
components
to
increase
your
productivity
so
and
that's
one
of
those
now
then
we'll
have
a
talk
about
the
SharePoint
framework
latest
news,
so
we'll
have
a
quick
chart
on
the
latest.
What
has
happened
since
the
last
time?
A
These
meetings-
and
please
do
remember
to
read
yourself
so
last
time
when
we
did
have
these
meetings
so
we'll
talk
about
latest
announcements
roadmap
and
all
of
that
in
that
section,
that
will
be
me
and
then
we'll
have
three
demos.
Now
Jax
is
having
small
issues
of
getting
in
tribal,
so
we'll
start
with
Elio
and
I
will
try
to
get
checks
in
during
Ilyas
demo,
and
then
we
can
actually
flip
between
the
the
order.
A
So
we
start
providing
SharePoint
framework
controls
for
you
to
reuse
and
we
start
harvesting
our
first
party
webparts
and
share
some
of
those
controls
for
you
to
reuse
within
your
implementation,
because
most
likely,
you
will
never
ever
well,
never
say
never,
but
it
will
at
least
take
a
while
to
get
the
first
party
web
part
open
sourced.
If
that
will
never
happen.
But
we
want
to
have
some
of
the
reusable
things
from
those
webparts
available
for
you,
and
this
is
the
easiest
where
we
can
actually
make
that
happen.
A
So
already
right
now
we
have
reusable
property
controls
and
then
there's
some
content
controls
as
well,
we'll
go
through
elio,
we'll
culture
what's
available
and
show
how
they
can
be
used
and
then
Paolo
is
going
to
do
a
more
detailed
demo
around
the
discuss
now,
which
is
a
ListView
common
set
with
Microsoft
a
craft
integration
and
that
one
was
part
of
the
demos
which
Paula
did
actually
already
in
ignite
a
pro
Boca
Wilco,
slightly
more
detailed
on
the
behavior
of
that
or
actually
was
this.
The
one
with
Dan
Cogan
showed
I
can't
remember.
A
A
Now,
like
mention
Patrick
Rodgers,
is
on
parental
leave
and
luckily
he
is
not
joining
on
this
golf,
which
is
a
good
sign.
So
he
was,
he
will
actually
have
a
small
break
which
absolutely
he
deserves
to
have
done,
but
the
one
slide
around
the
BMP
tas
core
component.
So
the
key
point
of
this
one
is
this
was
something
which
we
started
back
in
one
and
a
half
years
ago
way
before.
A
Actually,
ship
on
framework
receivin
announced
because
we
knew
what's
coming
up
and
we
started
actually
working
together
with
community
on
the
modern
way
of
doing
customization
somehow
with,
and
we
started
pushing
community
on
this
direction
without
people,
knowing
the
reasons
why
we
were
doing
that
and
the
PM
PHAs
component
was
actually
the
the
reason
or
the
the
project
what
we
started
to
build
built
at
the
time.
So
this
was
February
2016
already
at
the
moment.
A
This
fellow
is
quite
widely
used
because
it
truly
simplifies
and
the
the
access
of
the
SharePoint
REST
API
is
again
completely
optional.
You
can
use
it
if
you
like
it.
If
you
don't
like
it,
you
don't
have
to
use
it
this
add,
but
it
supports
and
you
can
use
it
in
SharePoint
framework
or
in
the
classic
JavaScript
customization
as
well.
So
you
can,
you
know,
use
a
custom
actions.
You
can
use
it.
A
It
works
and
on-premises
in
SharePoint
2010,
even
well
in
2010,
because
there's
no
rest
a
pianist
in
2010
but
anyway,
and
it's
it's
a
really
great
component
which
is
available
for
you.
We
are
evolving
this
quite
significantly
pretty
fast
and
whenever
Patrick
is
actually
back
from
parental
leave.
But
already
at
the
moment
you
can
say
that
we
have
1,600
1,700
tenants
within
the
last
month
who
were
which
were
using
the
s
BPM
PHAs
in
production
in
SharePoint
Online
over.
A
So
we
don't
trace
back
who's
doing
that
in
on-premises,
because
that's
basically
impossible
well,
it
could
fall
back
by
the
home,
but
we
don't
actually
include
that
kind
of
code
and
within
our
stuff,
and
if
somebody
is
wondering
how
do
we
actually
trace
this?
Well
as
part
of
the
requests
which
are
going
into
the
SharePoint
Online?
We're
adding
a
header
tag
on
the
request
and
that's
when
we
are
able
to
then
crawl
that
from
the
locks
of
SharePoint
Online,
because
we
are
of
shape
and
engineering.
So
we
have
access
unlocks.
A
That's
how
we
kind
of
a
trace
back
on
how
many
tenants
and
how
many
requests
are
coming
in.
We
don't
actually
know
how
it's
been
used,
because
that's
could
be
considered
already
as
a
confidential
information
and
we
didn't
I
didn't
have
any
additional
things
on
the
PMPA
s
core
site
and
that's
mainly
because
I
didn't
about
we
want
to.
We
want
to
make
sure
that
Patrick
is
on
place
and
he
has
the
latest
on
that
one.
So
I
don't
want
to
actually
steal
any
thunder.
There's
good,
good,
good,
great
stuff,
coming
up
on.
A
B
B
A
Remember
to
meet
yourself
now
we
have
again
somebody
talking
on
top
of
me.
There
we
go
now
a
few
announcements
related
on
SharePoint
framework
or
in
the
context
of
SharePoint
framework
in
ignite.
We
announced
this
a
new
set
of
reusable
controls
for
a
shared
solution,
and
this
one
is
super
super
useful
for
you
to
Inc
use
your
productivity,
so
you
can
use
them.
A
It's
it's
absolutely
optional,
and
but
the
whole
point
of
this
one
is
that
you
don't
have
to
worry
about
how
to,
for
example,
how
do
you
integrate
the
taxonomy
service
to
build
your
own
taxonomy
picker
for
your
web
part?
You
can
use
two
reusable
control
to
make
that
happen,
and
this
is
a
new
initiative
which
we
announced
in
the
ignite.
A
If
you
go
AKMs
SP
FX
controls
that
will
land
you,
the
one
of
the
github
repositories
around
this
one
will
do
more
documentation
and
round
how
to
contribute
how
to
get
started
and
all
of
that
all
the
time.
But
if
you
go
to
the
wikis
of
these
repos,
you
can
actually
find
already
how
to
use
these
controls
and
also
there's
cross
linking
between
the
content,
controls
and
the
property
bank
controls
and
Elia
will
work
through
both
of
these
options
in
the
demo.
Now.
A
A
Many
of
those
solutions-
and
many
of
those
are
in
quite
simplistic
samples,
there's
so
much
scenario
how
to
make
something
happen
or
they
hit
an
API
but
they're
not
necessarily
ready
to
be
used
in
production.
Now
this
one
is
more
around
the
SPF.
X
solution
is
more
around
ready
to
be
used.
You
can
easily
configure
them
we'll,
provide
additional
guidance
and
documentation
on
them
as
well.
Right
now,
the
situation
isn't
quite
optimal,
but
looking
into
having
Mike
Camelin
used
from
the
marketing
and
who's
been
leading.
A
This
effort
in
the
in
by
week,
within
two
weeks
in
the
sick
and
actually
the
latest
and
greatest
on
this
one.
But
you
can
already
go
to
the
key
top,
have
a
look
on
what's
available,
what
are
the
wet
parts
and
what
do
they
actually
do
and
then
have
a
look
on
the
code
and
learn
from
them
as
well?
How
quickly,
before
we
go
to
the
actual
demo
section?
A
We
also
announced
pretty
recently
easily
deploy
webparts
an
extension
across
the
enterprise,
and
this
refers
to
the
tenant
scope,
deployment
option
which
we
did
have.
I
also
a
webcast
release.
This
more
this
Monday
so
a
few
days
ago,
if
you
go
to
the
BMP
youtube
channel
or
to
the
left
of
scot
combs
last
box,
we
actually
walk
through
in
a
webcast
me
and
Waldeck.
What
are
the
options?
What
is
the
impact
of
the
tenon
scope
deployment?
What
does
it
mean
in
practice?
A
We
also
announced
the
yeoman
generator
with
1.3,
which
understands
on-premise
and
cloud,
which
is
cool
thing,
so
there's
a
one
yeoman
generator
depending
on
your
selection.
It
will
then
ask
awful
do
a
solution
which
is
targeted
for
one
premises
and
cloud
or
only
to
cloud,
and
the
reason
why
there
is
that
question
is
quite
simply,
the
cloud
is
always
ahead
of
the
on-prem
and
because
there's
the
server-side
dependencies
on
the
sharepoint
framework
versions.
A
We
can't
update
your
local
on-premises
box
as
often
as
we
update
sharepoint
online
Chevonne
framework
extensions
are
now
generally
available,
as
in
SiC
night.
That's
an
awesome
announcement
as
well,
so
you
can
actually
improve
use
application.
Customizers
field
customizers
released
to
your
customizers,
so
a
massive
deal,
so
you
can
actually
do
intern
customizations
in
the
modern
experiences,
which
is
great
thing.
The
tenant
properties
are
now
in
def
previewed,
so
a
now
the
checks
asana
kolchak's
can
actually
start
immediately.
A
When
I
stop
that's
the
first
version
to
do
the
demo,
then
we'll
move
to
Ilya
and
Paulo
and
Chuck's
is
going
to
explain
what
that
is
all
about.
One
new
thing
also,
which
is
not
related
on
SharePoint
framework
but
around
the
SharePoint
development
is
the
modern
themes,
modern
custom
themes
and
they
are
now
available
in
SharePoint
online
as
well.
What's
coming
soon,
obviously,
our
fabric
core
support,
so
core
styling
support
is
coming
soon.
A
A
Also,
the
add-ins,
though
not
such
the
only
for
SharePoint
framework
solutions,
so
you're
able
to
remotely
install
add-ins
which
have
been
installed
to
the
app
catalog
as
long
as
they're
in
app
catalog
you're
able
to
push
them
running
an
API
and
install
them
to
the
individual
sites
within
your
Tanakh
and
also
are
creating
and
deleting
and
often
then
we
have
site-specific
app
catalog
or
site
collection,
specific
app,
catalog
coming
up
pretty
soon
as
well,
and
also
the
last
thing
which
again
isn't
really
around
of
SharePoint
framework.
It's
the
site
designs
with
an
extensibility
point.
A
The
point
of
that
one
is
the
fact
that
you're
able
to
in
the
create
your
own
customizations
that
are
out
of
the
box,
I
provisioning,
a
story
and
that's
coming
up
pretty
soon
as
well
and
among
the
other
things
you
could
push
out
your
SharePoint
framework
extensions
on
top
of
communication
site
whenever
the
communication
side
is
getting
provision,
that's
really
the
key
point.
Data
now
on.
Let's
move
on
to
the
demo
section,
so
I
don't
actually
eat
up
any
time
from
additional
time
from
the
demos.
A
A
C
C
C
Tenant
property,
so
this
is
something
we
announced
at
ignite
and
this
is
a
way
for
developers
to
have
a
property
set,
that
they
can
have
it
in
the
common
tenant,
app
catalog
and
basically
consume
them
in
your
webparts
or
in
extensions.
So
some
examples
could
be
that
you
would
want
to
store
your
Google
Analytics
key
or
you
know,
Google
Maps
key,
so
that
your
Maps
webpart
can
actually
use
that
key
instead
of
having
it
as
a
configurable
property.
C
We
have
started
it
small
so
that
we
can
extend
it
when
we
release
other
features
in
our
SPF
X,
so,
basically
the
documentation.
If
you
go
to
SharePoint
framework
documentation
and
in
the
table
of
contents
on
the
left,
you
will
see
that
tenant
properties
here
and
this
documentation
is
still
evolving.
I'm.
Writing
more.
C
You
know,
Bess
and
I
have
been
discussing
on
this,
but
we
basically
started
out
with
giving
powershell
commandlets
for
get
and
set
and
we're
basically
calling
it
as
storage
entity
in
the
tenant,
and
you
can
add
key
and
value
and
give
some
description
and
comments
so
that
you
know
this
key
is
for
this
particular
scenario.
Or
you
know,
this
is
a
Google
Analytics
key
and
if
you
have
any
comments,
maybe
you
need
to
tell
someone
to
go
to
this
person
to
update
this
key.
C
So
you
can
have
those
comments
as
well
and
the
way
that
we
are
consuming.
This
is
through
the
API.
We
have
a
get
API
which,
basically
now
you
can
go
to
any
site
and
say
get
me
the
storage
entity
of
relat
the
key,
and
once
you
give
that
key
will
give
you
back
the
all
of
the
properties
that
you
have
for
that
entity
from
the
tenant
add
catalog
today.
This
is
all
independent,
app
catalog
and
you
need
to
be
a
Canon
administrator
to
work
with
this
powershell
commandlets.
C
But,
as
you
saw
the
previous
slide,
we
do
have
site
collection
at
catalogue
coming
up.
That
means
that
you
know
this
is
not
just
for
the
tenant
at
catalogue,
but
once
we
have
the
site
collection
at
Kenalog,
the
goal
is
that
these
things
work
according
to
that
specific
scoped
site
collection
as
well,
and
that's
why
we
have
this
site
kind
of
that
lets
developers
and
trend
mister
to
specify
which
site
you
are
working
against.
C
Now,
to
start
with
this,
you
need
to
download
the
Microsoft
SharePoint
Online
management
show
you
can
get
the
link
from
the
dock
as
well.
If
you
are
familiar
with
this,
then
you
know
that
the
way
that
you
first
connect
to
the
service
is
through
the
connect,
SPO
service
command,
and
you
basically
have
to
give
your
SharePoint
admin,
Center,
URL
and
once
you're
authenticated
with
this
service.
C
So
basically
now
you
can
use
the
get
sorry
set
SPO
storage
entity
and
if
you
give
the
enter,
if
you
hit
enter,
it's
gonna,
ask
you
for
all
of
the
parameters,
and
initially
this
is,
as
I
said,
it's
working
against
the
ad
catalog.
So
you
need
to
give
the
ad
catalog
URL
for
this
and
then
it's
gonna
ask
you
a
key.
Let's
say:
P
and
P
key
value
is
VESA
comments.
This
is
a
P
and
P
key.
C
C
Description
and
now
it's
going
to
basically
save
this
and
apologize.
My
machine
somehow
is
taking
some
time
to
reach
the
service
I.
Don't
know
why
it
might
be
my
wireless
connection,
so
this
is
going
to
get
added
to
the
tenant
ad
catalog
key
and
known
to
be
available
for
apps
to
consume
and
even
for
10
straight
years
ago,
and
remove
this
key
or
just
get
the
key
and
see
what
the
value
is
just
making
sure.
So
any
questions
so
far.
A
C
Anybody
so
read
is
available
to
everyone,
so
anybody
can
greet
it
so,
of
course,
in
the
tenant
PowerShell
you
would
need
to
be
a
trend
admin
because
it's
not
available
to
other
users,
but
if
you
usually
get
SPS
village
entity
now
you
can
basically
say
what's
the
size
site
and
again
here.
The
point
is
that
this
is
a
storage
entity
for
a
site
and
right
now
it's
available
for
the
ad
catalog
in
the
tenant,
the
tenant
at
Kellogg
website.
C
Now
it's
gonna
ask
me
the
key,
let's
say
TMP
key,
then
it's
gonna
give
me
the
comment,
description,
value
and
one
thing:
if
you
know
it
is
closely
the
comment
and
description
are
or
I
mean
they're,
not
the
same
they're
just
flipped,
but
we
are
fixing
that
and
we'll
be
fixed
very
soon.
So,
basically,
this
is
the
way
how
you
can
set
and
and
get
from
the
tenant.
Powershell
tenant.
C
Sharepoint
online
management
show
no
for
developers.
We
also
have
the
api.
So,
for
example,
here
I
am
in
my
site
in
the
same
tenant
that
I
was
using
and
I
can
just
go
to
my
site
/
my
team
/
in
the
score
API
slash
web.
So
underneath
the
bed
we
have
get
storage
entity
and
all
you
need
to
pass
is
the
key.
C
C
So
that's
how
you
can
request
this
from
your
web
part
through
this
API,
which
is
available
for
every
user,
and
that
will
give
you
back
the
key
and
then
you
can
use
it
into
any
other
solution
that
you
have
in
your
extension
at
that
part.
So
that's,
basically
the
simplest
form
of
having
a
property
common
across
all
of
the
solutions
that
you
want
to
build
in
a
tenant
in
a
tenant
that
you
want
to
consume
this
from.
C
A
C
Yeah
I
forgot
about
one
thing,
so
this
is
still
in
preview.
It's
available
for
only
first
release
tenants.
We
want
to
push
this
to
GA,
so
everybody
can
start
using
it.
I
also
have
a
tech
community
post
under
the
shape
one
developer
space.
So
far,
one
person
has
replied.
Thank
you
to
that
person.
But
if
you
are
interested
in
this
feature
and
if
you
can
use
it-
and
let
me
know
what
you
think
about
this-
and
what
other
things
do
you
see
any
bugs
or
anything
like
that?
B
A
Excellent
thanks
two
checks
for
this
one:
it's
guerrilla
tively,
simple
scenario,
but
I
think
it's
super
super
powerful,
because
there
was
a
good
example
in
the
in
the
iron
chat
window
was
around
was
a
day.
Asha
function,
rest
endpoint
with
all
of
your
web
part
instance.
They
should
be
using.
So
you
would
have
a
one
location
where
you
configure
done,
and
then
the
web
parts
can
access
that
from
that
you
don't
need
to
set
the
property
in
every
single
instance
as
an
example
or
what
would
be
the
other
scenarios
for
this
one.
C
Any
anything
that
you
know
if
you
want
to
deploy
a
component-
and
you
don't
want
that-
you
want
to
use
a
property
that
you
don't
want
to
put
in
the
property
pin,
so
that
not
every
user
has
to
configure
it
for
every
page,
for
example,
for
for
every
page
they
add
the
web
part
to
then
this
becomes
a
very
viable
solution
to
push
that
forward.
Maybe
there
is
a
common
endpoint
that
you
always
refer
to
and
you
want
it
to
be
common
across
all
the
web
parts,
and
maybe
there
is
a
there's
a
there's.
C
A
B
Switch
to
this
demo
and
maybe
later
come
back
to
the
previous
one
yeah.
So
this
demo
is
about
the
discuss
now
common
set
that
we
introduced
at
ignite
2017
couple
of
weeks
ago,
and
this
is
basically
a
list
view
and
library
common
set
to
allow
users
to
create
on
the
fly,
a
meeting
for
a
document
selected
in
a
document
library.
So
this
is
the
repo
in
which
you
can
find
the
source
code
of
the
sample.
B
The
well-known
SP
dive
effects,
extensions,
repo
and
the
solution
is
under
the
samples,
react
command,
discussed
now,
folder
just
to
set
the
context.
Let
me
show
first
of
all
the
extension
in
action
and
then
I
will
explain
you
how
it
works
under
the
cover.
So
this
is
the
home
page
of
a
modern
site
in
which,
by
the
way,
you
have
yet
another
example
that
we
have
on
still
on
get
up
in
the
same
repo.
But
this
is
not
the
sample
we
will
see
today
and
if
I
go
into
a
document.
B
B
But
aside
from
that,
this
is
a
nice
common
set
extension
to
show
you
how
you
can
leverage
SharePoint
framework
to
provide
nice
UI
to
extend
the
out-of-the-box
capability
of
the
environment.
So,
let's
see
how
it
works.
First
of
all
it
it
is
a
SharePoint
framework
extension.
So
here
I
have
a
Visual
Studio
code.
The
instance
in
which
I
have
the
full
source
code
of
the
solution
and
from
a
solution
perspective.
B
Moreover,
we
have
a
typescript
file
in
which
we
export
the
class,
which
internally
extends
the
base
list,
view
command
set
type
which
is
provided
by
the
SharePoint
framework,
extensions
infrastructure,
and
here
what
we
do
simply
in
the
on
list
view
updated
method
of
writing.
We
double
check
if
there
is
one
and
only
one
item
selected
in
the
UI,
so
whenever
these
own
list
view
update
event,
fires,
we
get
the
event
input
argument.
We
select
the
property
for
having
the
list
of
all
of
the
selected
rows
and
in
case
we
have
just
one
row.
B
We
make
visible
the
custom
command
in
the
UI
because
we
don't
want
to
handle
multiple
meetings
with
one
click,
at
least
not
in
this
demo.
But
if
you
like,
you
can
work
on
it
and
you
can
share
your
experience
with
the
community
as
as
like
as
everything
else,
it's
an
open-source
project.
Moreover,
whenever
the
end
users
will
click
on
the
discuss
Now
button,
we
will
have
the
overriding
of
the
own
execute
method
in
which
we
will
still
get
an
event
object
and
we
can
simply
double
check.
What
is
the
comment?
B
B
B
Dialog
framework
and
I
will
show
you
how
it
works
pretty
soon
and
we
just
set
few
properties
of
this
dialog
object
and
we
show
the
dialog
so
all
of
the
magic,
let
me
say,
is
done
by
the
dialog
and
in
fact
here
we
have
the
scheduled
meeting.
Dialog
react
component,
which
provides
first
of
all
is
scheduled,
meeting
dialogue
content,
which
will
be
a
class
which
will
implement.
It
will
be
a
component
which
will
implement
all
the
UI
stuff
of
our
dialogue.
So,
as
you
can
see,
it
extends
the
component
base
type
of
reactor.
B
We
have
some
custom
properties
and
a
state
object
will
hold
the
state
of
our
dialogue.
Content
object
in
the
render
method
of
our
component.
We
simply
use
a
dialog
content
object,
which
inside
will
have
a
bunch
of
office,
UI
fabric
components
like,
for
example,
the
text
field
for
the
document
title,
which
will
become
the
meeting
subject,
we
define
a
date/time
picker
controller,
which
is
a
custom
one
we
built
on
top
of
the
date,
picker
padding
the
time
the
hour
and
minute
selection
beside
the
date
selection.
B
Once
the
submit
button
got
pressed
in
the
dialog
component
that
we
have
here,
which
extends
the
base
dialogue
component
again
of
the
SharePoint
frame
or
dialog
framework.
We
simply
do
the
rendering
of
our
data
content
and
upon
the
click
on
the
submit
button,
we
will
have
the
submit
function
which
will
use
the
micrograph
to
create
a
new
meeting
in
the
calendar,
so
how
we
do
that.
First
of
all,
we
create
a
JSON
object
memory
which
will
define
the
event
which
will
be
created
in
the
calendar.
B
B
So
by
doing
this
post
of
the
JSON
object,
we
will
create
the
meeting
the
event
in
the
calendar
and
then
we
simply
handle
the
response,
which
can
be
a
positive
one.
So
we
simply
say:
okay,
all
good,
or
we
can
have
an
issue
and
we
can
simply
notify
the
issue
to
the
end
users.
That's
the
overall
picture
of
the
implementation
of
the
common
set.
B
One
more
thing
that
I
think
is
really
useful
to
underline
is
that
this
solution
from
a
packaging
and
deployment
perspective
has
been
defined
in
order
to
be
a
solution
which
has
to
be
installed
in
every
single
target
site
collection.
So
we
don't
use
the
so
called
tenant
wide
deployment,
which
is
one
of
the
new
features
introduced
around
the
ignite
conference
timing.
B
So
because
of
that,
in
this
scenario,
whenever
we
do
the
packaging
of
the
solution,
we
also
package
inside
the
HP
pkg
file,
a
feature
framework
element
file
which
I
can
show
you
and
in
this
feature
frame
or
file
with
a
final
custom
action
which
will
simply
target
all
of
the
lists
of
type
101,
which
means
all
of
the
document,
libraries
and
which
will
add
in
this
location,
which
is
the
one
which
identifies
both
the
a
CB
menu
and
the
top
menu
area.
On
the
list.
B
View
screen
these
client
side
component
ID,
which
of
course
is
the
ID
of
the
common
set
that
we
have
in
our
manifest
file.
So
whenever
you
will
install
the
package
in
the
app
catalog
and
add
the
package
in
your
target
set
collection
by
adding
the
package
in
your
target
cell
collection,
the
feature
framework,
custom
action
will
be
activated
and
you
will
find
the
common
set
available
in
all
of
the
document.
Libraries
in
your
environment.
B
B
So
all
of
the
list
of
type
one
one
in
your
target
environment
or
if
you
rather
prefer
you
can
even
use
this
option
which,
by
using
season
in
PowerShell,
will
simply
bind
this
command
set
to
any
specific
library
that
you
want
to
target,
and
you
can
see
an
example
in
which
I
target
the
document,
library
and
I
add
a
custom
action
just
and
only
for
that
specific
document
library.
Just
to
give
you
a
pointer
to
the
SharePoint
framework
dialog
framework.
B
This
is
the
article
which
explains
you
how
to
install
first
of
all
and
then
how
to
play
with
the
dialogue
framework,
which
I
I
think
is
really
really
interesting
and
powerful
and
more
in
general,
as
I
told
you,
the
full
source
code
of
the
solution
is
on
the
github
repo
for
SPD
of
effects.
Extensions
I
think
that's
all
my
side
visa.
So
if
you
want,
we
can
try
to
go
back
to
Ilya
or
we
can
yes.
A
A
D
So
yeah
and
now
they
start
calling
yeah
just
keep
it
okay,
so
at
ignite
we
released
two
sets
of
controls.
One
is
the
SharePoint
framework
controls
for
react,
which
are
obviously
using
react
components
or
can
be
used
in
react,
components
and
the
other
one
is
property,
Bank
controls,
so
the
controls
you
can
use
in
for
customizing
the
properties
of
your
web
part.
So,
let's
first
focus
on
the
react:
controls
on
NPM
there's
a
repository
and
PNP
/
s,
pfx,
don't
roles,
so
somebody
damn
wait.
A
D
Boy,
so
at
ignite
we
released
two
sets
of
controls,
one
the
controls
for
react,
which
are
obviously
used
in
react
components
and
the
second
part
is
the
property
pane
controls
which
are
controls
that
you
can
use
in
the
web.
Part
configuration
pane.
So
let's
first
focus
on
the
SharePoint
framework
controls
for
react.
D
Currently,
if
you
go
to
MPN,
so
npm,
GS,
comm
and
search
for
at
PMP,
/sb
FX
controls
react.
You
will
end
up
on
this
page.
You
can
also
go
to
this
link,
which
is
the
Gator
repository
which
you
will.
You
will
bring
you
over
here
and
we
will
give
you
more
information
about
how
you
can
install
them.
So
just
explore
the
wiki.
Normally,
okay,
there
it
is,
and
currently
we
released,
a
four
did:
I
open
the
wrong
one.
D
Okay,
then
we
start
with
the
property
controls
currently
released
for
property
controls,
which
are
the
property
fields
date
picker
control,
the
list,
picker
the
people
picker
and
the
term
picker.
So,
let's
open
up
the
term
picker,
for
example,
this
term
picker
is
going
to
give
you
what
names
us
it's
going
to
give
you
a
term
picker.
So
it's
going
to
go
over
your
managed
metadata
term
sets
and
it's
going
to
visualize
them,
and
it's
going
to
allow
you
to
select
some
terms.
You
can
do
a
multi
selection.
You
can
do
a
single
selection.
D
All
can
be
done
by
just
providing
write
values
in
the
property.
You
also
see
the
codes,
how
you
need
to
add
it
to
your
web
parts
and
so
on
and
so
on,
but
one
important
thing:
if
you
go
to
the
getting
started
on
the
getting
started
page,
you
see
what
you
have
to
actually
install.
So
this
is
what
you
need
to
install
and
then
you
can
go
to
the
property
paint
controls
to
add
them
to
your
web
part
to
start
using
them.
So
let
me
open
the
project.
D
So
this
is
a
project
inside
the
projects
both
for
the
control
set
for
react
and
for
the
property
paint.
You
will
find
a
sample
reports
in
that
sample
web
part.
We
added
all
the
property,
pain,
control,
pickers
and
also
for
the
controls
for
react.
We
edit
the
controls
inside
the
web
parts,
so
if
you
want,
if
you
want
to
contribute
to
this
library,
feel
free
to
do
so,
but
just
make
it
just
be
aware
that
you
also
add
the
control
to
the
web
part.
So
we
can
test
it
and
people
can
explore
how
they
work.
D
D
They
should
also
work
offline.
So
if
you
want
to
do
some
test
of
line,
you
can
also
use
the
local
workbench
I
just
want
to
show
the
online
world
bench
because
then
I
can
show
more
information.
So
you
see
the
people
picker
I
can
search
for
myself.
So
I
can
add
myself
in
there.
I
can
also
specify
multiple
lists,
and
here
we
have
the
term
picker
and
in
the
term
picker
we
can
just
open
our
terms.
That's
it's
going
to
load
the
terms,
and
then
we
can
select
a
couple
of
them
like
phrases.
D
These
kind
of
things
in
my
configuration,
I
disabled,
my
date
picker.
So
that's
why
it's
grayed
out
just
for
a
test,
and
now,
if
I
apply
it,
you
see
that
the
configuration
has
been
added.
This
is
how
you
can
use
it.
It's
very
simple,
or
we
made
it
very
simple
for
you
so
that
you
don't
have
to
do
a
lot
of
configuration
and
most
of
the
configuration
is
added
on
the
documentation
site
or
on
the
wiki
of
the
repository
and
one.
A
Point
on
the
picker
so
that
tsunami
picker,
is
no
doubt
one
of
my
favorites
in
here,
because
you
don't
have
to
worry
and
it's
a
good
example.
What's
the
difference
between
these
controls
and
office,
you
have
factory
create
controls,
so
these
are
meant
to
be
an
abstraction
layer.
On
top
of
office,
UI
fabric
controls
the
office.
You
have
fabric
controls.
They
don't
actually
know
that
they're
being
used
in
SharePoint.
These
fellows
know.
So
as
an
example,
this
taxonomy
picker
is
hiding
all
of
the
traffic
between
your
web
part
and
SharePoint.
A
You
don't
have
to
provide
the
needed,
URLs
and
rest
endpoints
and
in
the
in
the,
in
that
case,
the
the
magic
behind
off
of
hitting
the
taxonomy
store.
All
of
that
is
getting
encapsulated
inside
of
the
control
you
just
control.
Is
it
a
single
picker
or
multi
picker
picker
and
be
good
to
go?
Yeah.
Sorry,.
A
D
Good
addition
to
it,
so
we
also
have
the
controls
for
react
that
contains
for
other
controls,
which
is
the
file
type
icon
control.
The
list
view
control
the
place,
all
the
control
and
the
side
breadcrumb
control.
If
we
open
the
place,
all
the
control
you
will
see,
this
is
a
control
that
was
previously
it
was
added
by
Sheraton
framework
itself,
and
then
it
was
removed.
D
You
want
to
use
in
here
like,
for
instance,
the
10,
the
text
you
want
to
show
the
button
which
label
it
needs
to
have
how
what
do
you
want
to
do
when
you
click
on
the
button
like,
for
instance,
if
we
gave
the
example
of
opening
the
property
pane.
So
let's
go
to
that
demo.
Let's
kill
this
one
and
let's
open
up
this,
it's
already
open
problem.
D
So,
let's
open
this
and
it's
this
demo
so
same
structure
in
there
in
this
structure
we
have
the
controls,
you
will
find
all
the
controls
and
we
also
have
a
web
part
sample
web
part
and
in
this
sample
web
part,
you
will
see
that
our
is
a
lot
of
content,
but
that's
just
for
the
demo
reasons.
So
we
can
test
all
the
controls
in
there.
You
also
will
find
unit
tests,
so
every
control
in
there
will
also
have
its
own
unit
tests.
D
So
if
you
want
to
go
through
the
unit
test
feel
free
to
do
so,
so
you
can
see
how
it
works,
so
normally
it
should
be
running
and
if
I
go
back
to
my
websites
over
here
and
I
should
have
a
configuration
part,
let's
refresh
controls,
test
and
once
this
is
that
you
see
that
we
have
a
fall
time.
I
can
controller,
it
works
with
font,
icons
and
images.
So
these
are
coming
from
office
UI
fabric
we
can
play
with
the
sizes.
D
We
have
a
bread,
crumb
control
right
now,
I'm
on
my
root
side,
so
I
only
see
my
root
side,
but
if
I
go
to
another
side,
I
would
see
deeper
levels
of
that
I
have
the
configuration
or
the
placeholder
control,
so
I
can
click
on
this
and
it
will
open
my
property,
pane
and
I
have
my
list
view
control
set.
So
if
you
want
to
explore
more
there,
we
also
release
the
sample
webparts
sample
report.
D
That
is
probably
more
functional
which
you
can
find
in
the
sample
gallery
repository
of
share
points
on
github
and
if
we
are
going
to
show
you
that
demo,
that
demo
shows
a
couple
of
controls
that
are
combined
together,
so
to
give
a
good
view
of
what
it
can
do,
so
this
webpart
is
using
the
property
controls.
So
if
we
are
going
to
check
it
should
be
in
there
or
didn't
I
when
we
are
over
here,
you
see
a
PMP,
you
see
the
s
P
of
X
controls
for
react
and
you
see
the
property
controls.
D
So
it's
going
to
use
the
place
holder,
it
will
show
me
a
place
holder
if
the
web
part
is
not
configured
once
the
web
part
is
configured,
it
will
show
me
a
spinner
when
it's
retrieving
the
items
and
when
the
items
are
retrieved,
it
will
show
me
the
items
by
the
list
view
control.
If
there
are
no
items
to
be
found,
it
will
show
me
a
place
all
the
control
that
says
yes
or
ain't,
no
items
that
we
found.
Let's
spin
this
one
up.
D
D
Okay,
it's
there.
So,
first
of
all,
it's
going
to
say:
hey,
you
need
to
configure
your
web
parts,
that's
what
I
explained
and
then
we
have
our
ListView
title
and
we
have
our
list
picker.
So
I
can
say:
okay,
give
me
the
documents.
If
I
apply
this,
then
it's
going
to
show
me
my
documents
from
my
document
library.
Now,
what
can
we
do
if
we
are
going
back
towards
that
property
controls
and
I
would
add
the
term
picker?
What
should
I
do
for
a
term
picker?
Hopefully
it's
even
it's
always
that
simple.
D
So
in
my
case,
I
just
have
to
copy
everything.
In
your
case,
it
could
be
that
you
still
have
to
configure
a
couple
of
parameters
or
properties
so
I
first
configure
the
interfaces
I
require
a
mile
apart
and
once
I
add
this,
then
I
will
be
able
to
use
a
property
term
picker
in
my
lab
part.
So
let's
use
this
piece
of
the
code
I'm
just
going
to
skip
this
one.
This
is
the
property
that
webpart
is
using,
so
it
will
store
the
selected
terms
inside
the
property
called
terms.
D
D
So
if
I
going
back
now,
I
see
that
I
also
have
the
select
terms
if
I
click
on
this
one
and
I
go
to
countries
and
I
would
say,
enter
because
I
love
and
work
I
live
there,
so
I
click
apply.
If
I
can
click,
you
see
that
my
list
gets
refreshed
based
on
the
selected
term,
so
it
does
a
query
to
my
document
library,
which
give
me
all
the
documents
linked
to
Antwerp.
D
A
Not
really
under
on
the
I
window,
I
think
crate
demo
actually
create
coverage
on
the
on
the
simplicity
of
actually
using
those
controls
in
practice.
As
well
and
like
mentioned
when
we
started
the
webcast.
Sorry,
the
special
interest
group
and
our
intention
is
absolutely
to
start
harvesting
the
first
part
of
a
part.
So
there
are
if
well
it
may
or
may
not
happen
in
the
future-
that
some
of
the
first
part
of
a
part
will
be
open
source.
But
we
don't
know
it's
that's
going
to
happen.
A
So
it's
it's
better
for
us
and
easier
for
us
to
actually
harvest
ideas
from
our
SharePoint
engineering
and
then
share
them
through
this
control
set
in
the
future.
Right
now
we
do
have
four
or
five
controls
for
both
of
those
control
sets,
but
we
will
absolutely
have
additional
controls
coming
up.
We
also
welcome
other
people
to
contribute
on
this.
A
Let's
rather
build
a
common
set
of
controls,
which
we
use
to
cater
and
use
the
engineering
resources,
also
to
review
the
code,
but
and
to
give
input
on
the
code
and
so
rather
than
everybody
implementing
their
own
stuff
all
over
again.
What
are
the
new
controls
are
planned?
Well,
there's
a
pretty
high
long
list
of
things
where
we've
been
thinking
web
part,
title
web
part,
chrome,
there's
additional
panels
and
dialogues
and
and
simplicity
on
those,
but
we
should
probably
do
a
better
job
on
the
wiki
to
list
the
next
step
of
things.
A
What
we
are
planning
to
do,
but
cool
we're
three
minutes
on
top
of
the
on
late
already
from
the
schedule,
so
I
do
apologize
and
that
we
did
have
some
audio
and
video
issues
while
we
were
traveling.
My
fault
yeah
no
worries
no
worries
but
I'll
cut
them
away
from
the
recording
and
the
recording
will
be
available
in
the
YouTube
channel
within
24
hours.
But
thank
you
everybody
for
joining.
Thank
you,
cheques
and
Paolo
and
Elia
for
your
great
demos.
Thank
you
also
for
the
participants
from
your
input.
A
Please
keep
the
input
coming
in
the
github
issue
list.
Sp
dev
Docs
issue
list
is
good.
If
it's
a
new
idea,
new
capability
go
to
the
user
voice
and
submit
issues,
and
suddenly
the
entry
aren't
there.
If
you're
interested
on
these
controls,
please
use
them
or
give
us
feedback.
Why?
Wouldn't
you
use
them,
so
we
really
want
to
help
you
to
be
more
successful,
more
and
increase
your
productivity
while
doing
development
on
top
of
the
motor
share
point.
But
thank
you,
everybody.
Thank
you.