►
From YouTube: SPFx JavaScript SIG 22nd of June, 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
and
welcome
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meetings
is
June,
22nd
2017
and
we're
going
to
have
a
good
meeting
for
you
today.
We've
got
a
couple
of
cool
demos
as
well
as
a
great
community
demo,
so
looking
forward
to
having
a
look
at
those
but
first
for
folks
that
might
be
new
on
the
call.
We
always
like
to
review
what
this
is
about.
So
we
are
a
subset
of
the
larger
SharePoint
patterns
and
practices.
Program
focused
on
SharePoint
framework
and
client,
finds
elements
and
roots
and
meets.
A
Please
do
remember,
stay
on
mute,
thank
you,
and
so
we're
focused
on
SharePoint
framework
and
client-side
development
and
the
JavaScript
core
library
that
we've
put
together
here
in
the
patterns
and
practices
group,
and
so
this
is
a
venue
for
folks
that
are
very
interested
in
those
types
of
endeavors.
So
the
client-side
development
and
SharePoint
framework
to
have
a
place
to
have
a
little
bit
more
focused
conversation
as
we
found
that
the
general
like
monthly
meeting
we're
just
getting
too
big,
and
you
know
it's
hard
to
sort
of
focus
on
these
topics
that
were
coming
up.
A
So
we
started
a
special
interest
group
and
we
meet
twice
a
week
and
we
will
continue
that
into
the
next
when
I
say
next
year.
Microsoft
our
fiscal
year
ends
at
the
end
of
June,
so
we
are
will
have
to
reset
the
Cowie
invitation
will
end.
Actually,
this
is
the
last
session
on
that
calendar.
Invite
we
will
get
that
reset
and
set
back
out
to
folks.
The
same
link
will
work,
we'll
just
update
the
file
at
that
link.
A
What
is
our
agenda
for
today?
We're
going
to
do
a
quick
update
on
the
JavaScript
core
component,
including
some
amazing
growth
numbers
I
want
to
talk
about
very
quickly
base
has
got
a
great
update
on
SharePoint
framework
as
well
as
a
short
demo,
and
then
we
got
demos
like
I
said
bases
got
a
quick
demo.
A
We've
got
a
demo
from
Velan
Georgio's
who
fled
in
butcher
that
too
badly
he's
got
an
SPI,
FX
sample
he's
been
working
on
which
I'm
excited
to
see,
and
then
I'll
have
a
short
demo
on
what
I'm
working
on
in
terms
of
the
graph
inside
the
JavaScript
core
library.
It's
a
very
early
look,
but
I
want
to
show
that
the
folks
really
with
the
idea
of
getting
feedback
since
it's
very
early
days.
So
we
have
the
opportunity
to
kind
of
craft
how
that's
going
to
work
before
it's.
A
You
know
built
out
and
sort
of
more
set
in
stone
and
harder
to
change,
and
then
we
should
have
maybe
a
little
time
at
the
end
for
some
open
discussion,
but
we'll
see
how
we
do
so
as
always
want
to
mention
opportunities
if
you're
new
to
participate
in
the
patterns
and
practices
program
or
this
special
interest
group,
we
do
encourage
you
in
the
community.
If
you
would
like
to
do
a
demo
on
this
call,
please
reach
out
those
demos
can
be
anything
to
do
with
SharePoint
framework
webparts
or
the
new
SharePoint
framework
extension
work.
A
That's
come
out
very
recently.
That
base
is
going
to
talk
about.
You
talked
about
on
the
last
call
and
I
think
we'll
talk
about
a
little
bit
more
on
this
call
if
you
have
anything
involving
the
JavaScript
core
library,
so
that
could
be
something
in
node
that
might
not
necessarily
be
inside
SharePoint
framework.
I've
had
some
really
cool
demos
around
that
you
can
also
contribute
on
github,
so
contribute
on
github.
You
can
submit
issues.
Give
us
feedback
feature
ideas.
A
So
if,
if
you
feel
like
you're,
not
getting
an
answer
or
that
we're
sort
of
ignoring
you,
it's
go
ahead
and
tag
us
in
the
question
will
sometimes
help
bring
that
to
our
attention.
So
don't
think
we're
trying
to
ignore
you
or
avoid
you.
It
might
just
be
that
we
missed
your
question
for
which
we
apologize,
which
is
kind
of
give
us
a
little
reminder
and
we'll
do
our
best
to
help
you
out.
So
a
quick
update
on
the
JavaScript
core
component,
so
latest
updates
206,
was
released
on
Monday
the
12th.
A
So
if
you
haven't
upgraded,
please
do
give
that
a
shot,
not
a
lot
of
ton
of
changes
in
there,
but
a
little
bit
of
added
functionality
as
well
as
some
bug
fixes
from
issues
folks
had
reported.
So
do
you
know
give
that
a
shot,
and
let
us
know,
of
course,
any
feedback
or
issues
you
might
see
with
that.
A
I
have
started
working
on
the
graph
support,
so
we
had
a
great
thread
going
on
there's
an
issue
in
the
issues
list
that
we're
using
is
that
thread,
and
so
we
are
going
to
sort
of
start
to
move
towards
doing
that.
But
do
you
want
to
get
feedback
on
that
design
and
I'll?
Show
you
guys
that
later
in
the
call
I'm
working
with
Sergey
he's
submitted
a
pull
request
which
is
really
cool.
It's
going
to
be
really
cool,
we're
working
through
exactly
how
that's
going
to
shape
up,
but
the
idea
is
going
to
be
you'll.
A
Have
the
ability
to
sort
of
essentially
do
like
a
P
and
P
dot,
configure
for
lack
of
a
better
term,
we're
still
sort
of
figuring
out
the
shape
of
it,
but
you'll
be
able
to
configure
sort
of
on
a
per
chain
basis,
a
base
URL
and
all
the
headers,
and
all
those
things
that
you
sort
of
can
now
configure
using
like
P
and
P
dot
setup,
so
it'll
be
sort
of
a
more
isolated
P
and
P
dot
set
up
that
won't
necessarily
be
global,
and
this
actually
it's
going
to
be
really
cool.
I.
A
Think
it's
going
to
open
up
a
couple
of
interesting
scenarios
and
actually
I
think
there's
a
question
a
while
back
and
I
apologize
forget
the
gentleman's
name,
I
want
to
say
was
Mike
or
Matthew,
but
had
a
great
question
around
sort
of
multi-tenant
support
and
how
to
do
that
more
easily.
So
I
think
this
might
open
up
that
as
well.
So
that's
going
to
be
really
cool,
that's
in
the
works,
and
he
and
I
are
working
through
that.
A
If
anybody
else
would
like
to
take
a
look
and
has
some
ideas
and
feedback
certainly
welcome
that,
but
that
will
definitely
be
part
of
the
next
release
and
then
I
want
to
also
add
in
terms
of
the
SharePoint
side
of
things
so
set
graph
aside
for
a
second,
the
SharePoint
side
of
things.
As
far
as
I'm
concerned,
things
are
fairly
feature
complete
and
stable
at
this
point.
So
if
you
have
ideas-
or
you
have
things
you
feel
are
missing-
please
let
us
know
happy
to
look
at
incorporating
them.
A
I
can't
promise
a
timeline
necessarily,
but
definitely
if
you
have
things
that
are
like
man,
this
would
make
my
life
so
much
easier.
If
that's
the
kind
of
thing
we'd
like
to
hear
about,
and
that's
the
kind
of
thing
we'd
love
to
incorporate
into
the
library,
because
we're
all
about
making
developers
lives
easier,
so
do
just
let
us
know
a
couple
of
links
down
at
the
bottom
again
to
the
s
P,
P
and
P
community
and
as
well.
A
We
have
the
Gitter
channel
and
that's
on
this
slide,
because
that
Gitter
channel
is
specific
to
the
JavaScript
core
library,
but
that's
a
great
place
to
also
ask
quick
questions
and
reach
out
to
to
folks.
You
know
if
you're,
if
you're
stuck
or
just
aren't
sure
how
to
do
a
certain
thing
and
then
I
didn't
want
to
mention.
We've
had
some
amazing
growth
over
the
last
two
months,
so
some
of
you
might
remember
when
I
showed
I,
don't
know.
A
A
So
that
was
probably
through
a
few
days
ago
in
June,
so
phenomenal
growth,
I've
got
to
say
it's
all
up
to
you,
guys
in
the
community
who
are
using
this
in
your
projects
talking
to
your
customers
about
it
and
incorporate
it
into
your
work,
so
I,
just
big.
Thank
you
for
me
from
on
a
very
personal
level.
I'll
just
say
it's
really
cool
to
kind
of
see
this
kind
of
growth
for
something
I
and
all
of
us
have
worked
on
together
and
it's
probably
the
piece
of
software.
In
my
entire
software
writing
life.
A
That's
gotten
the
most
usage.
We've
all
had
those
projects
that
just
get
thrown
away.
So
it's
really
cool
to
see
something.
We've
all
built
together,
get
you
so
highly
and
then
you'll
see
down
here
on
the
bottom.
That
graph
is
the
NPM
downloads
for
the
package
by
month.
So
you
can
see
that
has
also
ramped
up
really
impressive
lead
again,
that's
a
tribute
to
all
of
you
using
this
in
your
projects
and
evangelizing
it
out
there
in
the
world.
So
thank
you
for
myself,
the
whole
PNP
core
team
and
I.
A
Really
it's
a
congratulations
to
everyone.
In
the
community,
that's
made
this
work
possible,
so
great
work,
really
everybody.
This
is
something
for
all
of
us,
I
think
to
be
proud
of.
Quite
frankly,
and
then
the
graph
on
the
right
you'll,
see
Norway
by
requests
is
now
the
number
one
country
for
the
JavaScript
core
library,
so
I
won't
I,
won't
name
the
tenant,
but
there's
one
tenant
that
is
is
has
some
really
amazing
usage
numbers
when
we
first
saw
them
in
May
I
wasn't
sure
they
were
accurate.
A
So
if
any
of
you
worked
on
that
customer
I'd
love
to
hear
from
you
to
hear
what
happened
in
that
project
and
what
you
guys
did
because
I'd
love
to
hear
that
story,
and
maybe
tell
that
story
a
little
more
broadly.
If
everybody
involved
is
okay
with
that,
so
I'll
just
kind
of
put
that
out
there
and
but
anyway.
A
So
then
you
see
United
States,
but
but
we
needed
500
and
some
tenants
and
as
opposed
to
Australia
that
had
90
and
third,
so
so,
but
really
great
and
it's
awesome
to
see
the
worldwide
usage
and
again
just
thank
you
to
all
of
you
in
the
community
for
making
this
growth
possible
and
making
this
you
know
something.
That's
valuable
to
all
of
us
and,
like
I,
said,
keep
that
feedback
coming.
So
we
can
make
it
more
valuable
and
continue.
B
Do
let
me
unmute
my
dolphin
take
over
the
presentation
as
well
so,
and
hopefully
the
audio
is
fine,
the
quality's
not
for
tomorrow,
but
hopefully
guys
can
hear
me
fine.
So
let's
talk
about
ship,
one
excellent,
Thank,
You
Patrick.
So
if
you
think
sharepoint
framework,
obviously
we
talked
about
the
sharepoint
framework
extension
last
time
in
two
weeks
ago
as
well.
It's
still
relatively
new
thing
that
it's
in
preview,
it's
now
available
in
preview
in
Deftones,
and
I'm
going
to
talk
about
what
it
actually
means
in
the
following
slide
as
well.
B
But
if
you
go
to
the
AKMs
SP
FX
extensions
you'll
find
the
product
at
or
will
still
say,
for
series
of
creating
an
application
customizer
which
is
equals
to
user
custom
action
and
then
there's
the
two
separate
tutorials
on
a
field
customizer
and
a
command
set
customizer.
So
you
will
then
understand
what
you
can
actually
do
right
now
in
the
dev
preview.
If
you
follow
up
on
the
tutorials
and
the
code
is
also
available
as
well.
We
do
also
have
already
quite
a
significant
amount
of
community
samples
on
SharePoint
framework
extensions,
which
is
pretty
cool.
B
Unfortunately,
you
forgot
to
put
a
slide
on
that
one,
but
let
me
actually
paste
in
that
URL.
So
it's
just
looking
into
looking
in
the
testing
something
related
on
those
extensions.
You
can
easily
find
reusable
samples
from
following
location,
so
I'm
going
to
paste
and
on
there,
where
we
have
the
tutorial
code
and
also
community
posts
and
we're
adding
their
samples
from
an
engineering
criticism
as
well.
Now
let
me
be
some
some
discussions
around
what
does
the
SharePoint
flavor
crustacean
preview
actually
means,
and
let's
try
to
clarify
the
situation
on
this
one
as
well.
B
So
if
one
extension
preview,
it
means
that
it's
now
available
in
the
developer
tools.
It
doesn't
mean
the
same
as
developer
site
collection.
So
you
need
to
have
a
developer
tenant
to
be
able
to
test
this.
You
can
ask
five
to
a
or
get
a
a
new
developer
tenant
by
signing
up
to
office,
365
developer
program
and
the
URL
is
in
da
window.
That's
free!
You
just
need
an
email
and
that's
it,
and
after
that
you
will
get
a
free
developer
tenant
where
you
can
actually
play
around
with
these
things.
B
At
certain
points
will
avail
ability
of
SharePoint
framework
extension
previews
the
first
release,
but
it's
not
ready
for
production
usage
for
time
being
and
the
reason
for
that
one
is
is
quite
simply
simple:
we're
waiting
for
the
feedback,
we're
adjusting
the
api's,
we're
adjusting
the
interfaces
and
capabilities
as
well,
and
in
this
point
maybe
we
should
have
some
more
clarity
and
maybe
a
separate
video
where
we're
explaining.
Why.
A
B
It
take
so
long
to
get
all
of
this
stuff
out.
Well,
actually
it
doesn't
the
the
reason
why
we
need
to
take
some
time
is
to
make
sure
that
the
API
is
and
indexes
are
good
enough
and
your
feedback
has
been
at
rest
and
then,
when
we
get
them
out,
we
can
no
longer
change
those
api's,
because
we
can
pray
cue
in
the
future.
B
So
when
we
are
doing
software
development
into
engineering,
we
can
go
and
adjust
our
interfaces
and
api's
in
the
matter
of
days
or
weeks,
because
that
would
actually
break
you
and
your
customizations
and
that's
why
it
does
take
slightly
longer
than
let's
say
a
standard,
random
custom
delivery
of
customizations
in
SharePoint.
So
we're
looking
into
getting
the
extensions
to
GA
summer
early
early
autumn,
there's
ignite
conference
coming
over.
So
that's
a
big
announcement
timing
as
well.
It
might
be
that
it's
g8
before
it
might
be
they're
seeing
in
ignite.
B
We
don't
actually
know
it
depends
on
the
feedback
we're
getting
so
there's
no
ETA
at
the
moment
for
the
ship
and
framework
extensions,
and
we
would
like
to
have
your
feedback
so
github.com,
slash,
sharepoint,
slash,
spdf
talks.
Last
issues
is
our
issue
list
for
recording
box
and
also
this
questions.
Hey
other
types
are
following:
can
I
do
that
and
if
it,
if
we,
if
that
capability,
it's
not
available
request
you
to
submit
a
user
voices
and
user
voice
entry
as
an
example,
so
we're
able
to
track
all
of
the
requests
in
an
official
manner.
B
The
reason
why
we
use
github
the
weld
the
key
topics
for
bugs
and
discussions,
and
then
user
voices
to
get
your
additional
or
new
feature
request
in
our
official
process
and
because,
quite
simply
sending
an
email
to
me
doesn't
mean
that
it's
actually
getting
into
the
queue
of
Kay
getting
thing
done
in
the
SharePoint
framework.
So
we
need
to
use
official
processes
because
otherwise
we
can't
follow
up
on
all
these
requests.
B
Cute
now
maybe
the
absolute
summary
on
that
one,
a
few
things
one
I
wanted
to
quickly
update,
and
so
this
one
is
a
relatively
new
series
on
the
SharePoint
framework.
So
we
did
a
recording
of
five
videos
together
with
Waldeck
and
round
TMP.
Well,
it's
the
video
series
is
called
the
empty
sorts,
but
this
one
essentially
four
to
ten
minutes
videos
which
are
showing
specific
websites,
internship
on
SharePoint
framework.
B
As
an
example,
today,
I
announced
this
one
in
Twitter
as
well,
so
there's
a
new
video
which
is
showing
what
does
it
mean
when
you
need
to
update
and
SharePoint
framework
solution,
because
this
has
been
apparently
quite
a
lot
of
confusion.
What
do
I
actually
need
to
do
to
get
a
updated
JavaScript
reflected
on
all
of
the
instances
of
my
clients
at
wakeport,
so
now
there's
a
video
recording
which
is
explaining
and
providing
that
insights
and
social
explaining
how
to
double
check
those
things
and
all
of
that,
so
that
came
up
well.
B
Actually,
I
recorded
that
this
morning
and
it's
live
in
into
the
YouTube
already.
So
these
are
essentially
the
SharePoint
VMP
shorts
are
well
maturity
of
them,
probably
in
future,
will
be
also
in
shape
on
framework,
but
they're
really
meant
to
be
explicitly
concentrating
on
a
specific
scenario
and
showing
you
how
it
can
be
done.
So
you
don't
have
to
listen
us
to
wonder
and
teach
at
on
random
topics
like
we're
doing
they're
in
a
special
interest
groups
or
every
now,
and
then
in
the
webcasts
as
well.
B
Now,
and
actually,
let's
move
on
so
a
few
things
before
I
do
a
quick
demo
on
the
cost,
I
love
books,
which
is
one
of
the
think
quizzes
in
the
def
previews
from
the
latest
packages,
I
wanted
to
kind
of
a
quick
to
share
what
are
we
doing
in
shape
and
engineering?
So
what
are
we
currently
working
on?
Also,
we
are
working
on
a
ship
on
framework
extension
so
targeting
that
g8,
it's
the
next
release.
B
Well,
there
will
be
subsequent
Steve
a
def
preview
releases
before
we
get
actually
duty
a
release,
we're
looking
into
having
automatic
solution
deployment.
This
is
a
classic
request
on
a
SharePoint
framework.
Currently,
the
only
way
you
can
get
a
client-side
web
part
available
in
a
site
is
the
SharePoint
framework
solution,
using
the
add,
an
app
capability
within
the
site
level,
and
we
do
absolutely
acknowledge
that.
B
Let's
put
it
that
way,
we're
looking
into
also
having
a
site
collection,
app
catalog,
which
essentially
means
that
if
a
tenant
admin
approves
your
a
to
have
an
application
site
collections
to
catalog
for
certain
site
collections,
so
that
the
site
collection
owners
and
those
site
collections
can
deploy
add-ins
or
Shep
and
framework
solutions
without
going
to
the
tenant
level
app
catalog.
So
that
will
provide
some
flexibility
on
things.
B
We're
working
on
the
on-premises
support,
so
SharePoint
2010
feature
pack
two
will
have
to
share
one
framework
available
in
down
premises
and
on
that
one
they
will
say
Abe
random
discussions
in
social
media
and
in
in
the
plaka
sphere.
If
everybody
is
is
if
somebody
is
still
using
the
blogosphere
term
and
just
to
be
clear
on
that
one.
So
there's
a
nice
block
from
AC
and
Chicanos
he
he
had
been
digging
on
the
SharePoint
frame
a
few
month
templates
and
then
kind
of
a
cup
scare
to
do
what
does
it
mean?
B
B
Difference,
however,
that
in
shipment
online
we
are
releasing
additional
component
types
like
extensions
or
reveal
customize
or
application.
Customized
are
much
faster,
so
that
selection
in
the
Yeomen
templates
will
just
filter
down
the
next
question
that
what
kind
of
component
you're
actually
about
to
create.
So,
for
example,
right
now
we
promised-
and
let's
be
clear
on
this
one
as
well.
The
promise
will
deliver
client
side
with
parts
in
SharePoint
framework
for
feature
vector.
B
We
haven't
promised
a
deliverer
Wall
Street,
a
framework
because
the
demo
possible,
so
what
you
will
see
in
a
future
back
to
is
the
client
side
web
port.
But
you
won't
see
extensions.
So
when
you're,
when
you're
then
running
the
yeoman
template
and
whenever
we
push
out
those
updates
available,
it
will
ask
you
that,
are
you
targeting
on-premises
or
online?
And
if
you
choose
on-premises,
then
you
are
creating
a
client
side
wave
board
if
you're
choosing
sharepoint
online
you're
still
able
to
create
an
extension
or
a
classic
report,
so
yeah.
B
Hopefully
that
clarifies
that
situation
on
that
one
we're
looking
into
or
working
on
a
craft,
HTTP
client,
since
the
one
you're
able
to
access
most
of
craft
without
a
tell
jeaious
and
all
of
the
additional
logins
and
that
documentation
is
on
my
table
and
I
do
apologize
on
and
delay
a
small
delays
on
that
one.
It's
coming
pretty
soon
in
the
documentation
section
as
well,
and
then
we're
working
on
a
dialogue,
dialogue
control
which
is
in
dev
preview
as
well
and
I.
B
What
I
was
planning
to
do
is
quickly
show
and
what
does
the
dialogue
control
actually
means
in
our
SharePoint
framework?
Extension
tutorials
we're
doing
a
super
simplistic
dialogue
scenario,
but
I'm
going
to
release
an
updated
tutorial
on
that
one
which
will
show
how
to
do
a
custom
dialogue
completely
and
that's
pretty
much
what
I
was
planning
to
do
as
a
quick
demo.
So
let
me
jump
on
that
one
by
the
way
I'll
get
back
on
the
questions
in
the
I
window
whenever
we
move
into
the
follow
our
Billings
demo.
B
B
So
this
is
my
developer
tenant
and
what
I've
done
here
in
my
environment
were
recreated
a
a
custom
command
set
or
list
the
command
set,
which
has
a
one
command,
which
is
common
one,
and
that
is
actually
opening
up
a
dialogue.
So
if
you
have
done
the
extension,
excuse
me
tutorials.
This
is
kind
of
a
similar
kind
of
a
set
up,
but
the
difference
is
that
we
are
creating
a
custom
dialogue
completely
so
we're
taking
over
the
rendering
of
the
dialogue
and,
in
my
actual
dialogue,
command
base
class
or
the
implementation.
B
We're
then
showing
the
dialogue
and
what's
important,
we
are
also
returning
a
value
from
the
dialogue
back
now.
Let's
have
a
look
on:
how
does
it
look
in
practice
in
this
case?
This
is
an
imaginary
scenario,
and
but
let's
have
a
look
on,
how
does
it
actually
work?
So
let
me
go
to
my
command
line.
I'm,
just
double!
Checking
that
it's
running
so
I
can
actually
save
a
live
demo.
B
Let
me
go
back
on
my
visit
studio
code
I'm,
going
to
copy
the
debug
path
and
Deepak
URL
from
here,
which
is
in
the
samples
and
all
of
the
extensions
sample,
should
have
this
one
included.
So
you
can
easily
test
these
things
in
the
dev
Channel
and
now
I
want
to
test
the
game's
live
data
and
live
site.
My
extension
so
I'm
going
to
do
that.
B
B
We
can
say
that
there's
a
new
open,
dialog
button
available
in
the
in
the
bottom
bar
and
I-
can't
remember
if
we
add
it
in
here
so
now
we
do
no,
but
you
can
absolutely
add
a
button
here
as
well
or
a
menu
item
and
in
the
context
menu.
So
in
this
case-
and
this
one
is
a
relatively
simple
scenario
but
I'm
able
to
open
up
a
dialog
and
then
you
are
able
to
control
what
are
we
actually
show
within
the
dialog?
B
So
in
this
case,
which
is
showing
a
scenario
where
we're
overriding
the
dialog
completely
and
writing
or
drawing
or
render
a
color
picker
picker
as
part
of
the
dialogue?
Well,
it
doesn't
actually
make
any
sense
to
have
a
color
picker
picker
handle
in
this
in
the
list,
but
it
shows
the
scenario
how
it
can
pay
them
now.
I
can
actually
pick
a
color
and
choose
whatever
it
is
and
adjust
slightly
the
transparency
or,
let's
put
it
there
and
click
OK
and
we're
getting
actually
to
return
value
back
on
the
extension.
B
So,
let's
quickly
have
a
look
on
I'm
not
going
to
spend
too
much
time
on
on
the
actual
implementation.
I'll
show
you
simple:
if
this
one
is
so
quickly
showing
what
it
actually
means,
so
here's
my
dialog,
sorry
command
set
the
implementation
inherited
from
the
base
class
I
would
see
a
common
set
only
thing
what
I
need
to
do
is
is
overwrite
or
implement
one
execute
for
command
one,
because
I
had
one
comment
comment.
One
was
matching
on
the
manifest
Jason
comments
which
I'm
actually
defining
here
I
mean
here.
B
In
this
case,
this
react
based
implantation.
It
is
taken
care
at
the
age
of
two
FF
quick
react
and
the
implementation
is
relatively
simple.
So
let
me
scroll
down
here.
It
extends
the
base
dialogue
which
is
coming
from
SharePoint
framework
and
this
the
results
return
value.
My
actual
render,
because
it's
a
rare
component,
is
super
simple.
That's
rendering
a
color
picker
dialog
content
component,
which
is
actually
defined
in
other
section
in
here
and
in
in
this
component,
which
is
essentially
rendering
some
components
or
controls
react
and
providing
additional
properties
for
them.
B
So
they
taking
advantage
of
the
office
UI
fabric
controls
create
control.
So
we
don't
actually
need
to
worry
about
the
UI
rendering
within
our
customization,
which
is
pretty
cool,
and
that's
really.
The
key
value
of
the
facility
operates,
react
on
controls
or
components
as
well.
It's
the
matter
of
me
designing
what
parameters
I'm
actually
passing
into
those
controls,
and
they
will
then
start
behaving
slightly
differently.
B
So
there's
a
dialog
content,
color
picker
this
the
color
picker,
which
is
actually
coming
from
the
red
components
as
well,
there's
a
dialog
footer,
which
is
actually
coming
from
SharePoint
framework.
That's
an
office
react
prophesy,
autocorrect
and
button,
that's
a
primary
button
and
that's
it
were
rendering
the
content
and
let's
actually
have
a
look
on
that
one
one
more
time.
So
there's
my
dialog
I
can
click
that
one.
The
elements
and
the
rendering
look
is
looking
consistent
with
office
365,
because
everything
is
using
the
office.
B
Do
I
have
recreate
components
in
general
and
I
can
pick
a
color
click
OK
I'm.
Getting
that
return
value
back
can
work
on
that
value
if
needed
within
my
code
again
so
relatively
simplistic
scenario,
but
it
shows
that
how
to
use
a
custom
and
how
to
build
a
custom
custom
dialogue-
and
you
can
absolutely
do
this
without
reacts-
you
can
absolutely
implement
this
using
angularjs
if
needed,
knock
out.
B
Whatever
is
your
preference
from
a
user's
perspective
and
obviously
you
can
use
this
dialog
in
the
context
of
web
parts
in
the
context
of
whatever,
so
it's
not
limited
on
the
on
the
command
sets
or
extensions.
So
but
right
now,
it's
still
in
Def
preview.
So
it's
not
really
meant
to
be
used
in
production
or
we're
collecting
feedback
from
you
guys
and
before
we're.
Releasing
this
one
good
I
think
that's
it
from
my
side,
so
I'm
going
to
go
back
on
the
iron
window
and
have
a
look
on
those
but
I.
B
C
C
C
Right
so
I've
uploaded
this
sample
last
week.
Theme
but
I
know
that
we
already
have
one
sample
there
that
this
applauded
and
it
shows
a
provisioning
placed
along
with
the
solution
package,
but
I
wanted
to
go
beyond
that
custom,
listen
and
put
additional
stuff
within
the
elements
file.
So
you
can
see
that
you
can
deploy
much
more
stuff
here
and
I'll
quickly
go
through
the
demo,
so
you
can
get
the
idea
what
what
we
have
there
and
I
already
packaged
my
solution
in
folded.
C
The
solution
to
the
other
catalog
so
I'll
have
it
available
here
and
I'll
just
write
hard
as
application
to
the
test
site.
I'll
just
say:
sigh
contents,
add
application
and
then
I'll
select
my
solution
points
I
solution.
What
I
did
other
not
and
I'll
just
select
my
solution.
It
is
def
on
ref
provision
Isis,
so
once
it's
installed
it
will
waste
all
my
wet
bar,
but,
along
with
my
web
part,
it
is
live
in
Italy,
so
some
simulation
of
stuff
here
at
the
end,
because
this
might
take
some
time-
I
already
pre
install
this
here.
C
So
we
will
get
here
at
the
end
and
see
whether
just
these
things
are
installed,
and
here
I
already
installed
it.
So
you
can
see
that
my
provision
asset
is
here,
but,
along
with
the
assets
that
provision
this
custom
place
this
custom
document
library.
If
we
go
in
the
list,
you
see
a
faced
data
here
as
well,
and
if
we
go
into
a
common
library,
you
see
in
each
folder
another
image
within
the
folder.
C
Even
if
we
go
to
the
side
pages,
this
is
uploaded
from
solution
packages
a
side
page
and
if
I
click
on
the
side,
page
I'm
getting
my
web
part
from
the
package
as
well,
and
we
also
have
created
our
web
property
back
properties
here.
But
if
I
have
some
time,
I
can
try
to
show
you
the
property
bed
properties
as
well.
C
That's
that's
pretty
much
and
now
we'll
go
to
to.
The
call
now
from
the
web
part
perspective.
Nothing
interesting
here.
This
is
a
boilerplate
blank
react
with,
but
I
haven't
done
anything
within
the
code
here.
The
most
interesting
part
is
here
so
within
our
assets:
folder
we'll
have
that
element
file
and,
as
you
can
see,
we
have
image
one
image
to
two
schemas,
one
for
the
custom
library,
one
for
that
we're
going
to
deploy
and
site
page
itself.
C
C
But
whenever
you
do
such
a
things,
if
he
is
someone
requires
you
to
deploy
a
site
page
with
the
web
part
directly
provision,
it
make
sure
that
you
download
the
latest
site
page
that's
on
the
SharePoint
tenant,
because
they
might
change
this
and
don't
use
just
the
page
from
the
sample.
You
might
have
additional
controls
here
too.
C
Most
of
the
code
is
here
within
the
elements
file
and
then
how
we
provision
those
this
all
gets
packaged
within
the
solution,
but
how
we
tell
the
SharePoint
to
to
deploy
all
these
stuff
now
at
the
top.
I've
just
created
one
common
here
and
these
elements,
if
somebody
is
not
familiar
with
the
elements,
this
is
part
of
the
classic
SharePoint
feature
framework,
and
we
have
this
from
like
SharePoint,
2007
I,
don't
know
vessel,
maybe
knows
better
than
me,
but
it
is
there
from
from
long
time
ago.
C
Now
we
have
one
content
type
for
the
list,
the
custom
basis
we're
going
to
to
deploy
and,
as
you
can
see,
it
inherits
from
the
item
so
and
these
are
our
custom
fields
here
placed
into
the
content
tag
and
another
callback
for
the
document,
library
that
inherits
from
the
document,
content,
dot
and
again
they're
the
very
same
field
place
into
the
content
bag.
These
are
all
custom,
something
that
maybe
is
false.
C
Also,
you
can
specify
your
own
Word
documents
template,
for
example,
with
to
the
form
inside
and
amuse
eaters
as
a
default,
a
default
in
plate
and
whatever
you
heat
in
your
body,
number
two
comes
libraries
going
to
open
your
Word
document.
For
example,
then
we
have
a
list
influence
over
here,
that's
going
to
create
our
custom
list
and
the
custom
list
has
its
own
way
schema.
If
we
open
the
delay
scheme
XML.
This
is
a
traditional
way
scheme.
Xml,
nothing
fancy!
Here,
you
have
viewed
within
the
waist
pretty
much
the
same
from
from
vs.
self.
C
C
Whenever
the
document
library
is
available,
it
will
upload
two
images
to
the
document
library.
As
you
can
see,
there
is
another
module
without
that
point,
to
the
URL
of
the
documents,
library
and
then
within
the
document
library,
we
will
upload
our
image
at
adapter
l.
That
means
that
this
immaterial
go
into
the
root
folder
of
the
document,
library
and
the
Mallory
images
that
is
going
to
go
into
a
custom
file
folder.
This
is
how
you
can
specify
a
virtual
path,
so
it
will
create
a
folder
field
for
you
and
place
the
image.
C
Another
interesting
property
here
at
like
content,
so
be
careful.
If
this
is
set
to
true,
whenever
you
have
image
image
with
with
that
name
on
the
document,
libraries
will
be
opened
up
over
it
and
the
last
two
here
we
have
a
property
back.
You
can
set
up
property
back
properties,
so
we
can.
You
can
specify
such
an
on
a
web
level
or
on
on
list
level,
as
just
put
two
samples.
The
first
one
will
specify
properties
on
the
web
level.
C
This
might
be
handy
for
your
app
whenever
you
you
have
settings,
for
example,
when
you
need
to
put
the
setting
somewhere,
but
they
need
to
be
visible
outside
of
a
list,
for
example.
But
if
you
have
less
specific
properties
you
can
you
can
create
a
properties
in
the
property
back
of
the
list,
and
this
is
my
custom
list
here
and
I'm
setting
custom
properties
in
the
in
the
property
back
of
the
list.
C
C
What
was
his
data,
but
this
should
not
be
done.
I
guess
in
introduction.
There
should
be
another
mechanism
that
you
you,
you
have
to
use
it
to
provision
data
I
would
suggest
that
for
development
purposes
you
could
do
it,
but
because
this
is
a
part
of
the
feature
framework
and
along
with
your
up,
your
vendor
feature
if
you'd
be
install
and
uninstall
and
then
install
the
feature
again,
this
data
will
be
double
there,
so
you
have
the
duplicate.
C
So
it
is
just
there
to
to
show
you
that
you
can
do
stuff
like
this,
but
you
can
create
separate
all
single
lists,
and
this
is
the
field
that
you're
going
to
populate,
and
then
this
is
the
video
another
interesting
thing
within
the
elements.
Xml
is
using
the
special
token.
So,
as
you
can
see,
we
have
that
one
side
and
then
on
the
front.
I,
don't
know
how
to
call
this
in
the
English,
but
you
can
see.
This
is
a
specific
token
and
it
has
specified
links
here.
C
Good
he'll
go
back
to
my
cheat
sheet
here
and
I'll,
say:
ok,
this
asset
should
be
specified
in
the
into
the
config
file
of
the
solution.
You
should
go
here
and
you
have
the
elements
XML
file
here,
but
also
you
should
specify
all
the
files
that
you're
going
to
know
upload
to
the
SharePoint,
so
they
can
visit
within
the
package.
C
If
you
miss
the
image,
for
example,
it's
not
going
to
be
packaged
so
bear
in
mind
and
how
we
can
troubleshoot
these,
for
example,
if
you
work
on
under
XML
file
and
then
for
some
reason,
you
messed
up
that
note
here
and
that
note
here
looks
like
they're
expecting
since
1
2
3.
This
will
fail
when
you
try
to
install
the
application,
and
it
will
fail
like
like
that.
It
will
say
sorry.
Something
went
wrong
like
that
and
at
that
point
I,
don't
know
what
went
wrong
with
in
my
package
solution
package.
C
So
the
one
of
the
things
that
you
can
do
and
the
only
one
that
I
know
is
you
can
go
on
the
details
here
from
from
site
contents.
Your
your
application
here
details
and
within
the
details.
If
you
have
an
app
permissions,
that
means
that
you
should
be
I,
think
that
I
don't
know
the
current
permissions.
But
if
your
psyche,
election
administrator,
you
should
be
able
to
see
it
or
share.
C
You
can
get
here
to
install
errors
and
then
try
to
see
what's
the
type
of
the
error,
what
happened
and
then
try
to
troubleshoot
what
I'm,
drawing
with
in
this
XML
provisioning
class,
so
that
I
can
say
copy
paste
and,
as
you
can
see,
did
some
some
more
details
there.
But
if
you
go
for
example,
here
you
will
see
as
an
evil
a
child
element
of
a
Philistine
six
one,
two
three
and
sometimes
even
Christ-
to
give
you
a
bit
more
details,
so
it
is
a
way
to
troubleshoot
this
element
files.
C
Now
when,
when
this
is
useful
in
many
of
the
cases
you
knew
you'd
prefer
to
do
some,
some
scripting
or
using
the
the
provision
in
engine
to
provision
your
Oh
acids,
but
if
you'd
like
a
fully
encapsulated
application,
so
everything
in
one
package
without
additional
scripting
or
additional
provision,
scripts
or
or
whatever
you
decide
to
develop.
This
comes
handy.
C
So
you
can
just
package
to
a
parts
list
or
whatever
is
there
and
then
just
deploy
it
like
that
and
whenever
someone
says
add
an
application
that
would
be
enough
to
deploy
hope
the
whole
package
I
find
it
very
handy
for
foursomes
most
analyses
if
you're
about
to
provision
the
whole
thick
texture
with
side
collections
in
whatever
you
know.
This
is
not
part
of
the
package.
C
B
Yeah,
now
that's
a
great
even
as
well
that
there
was
too
simplistic
scenario
like
like
I
mentioned
as
part
of
the
brilliant
spring,
but
this
is
a
good
example
of
a
kind
of
a
showing
all
of
the
different
capabilities,
but
what
are
available
in
the
future
framework
related
on
SharePoint
solution,
SharePoint
framework
solutions.
So
one
thing
what
I
wanted
to
quickly
pinpoint
just
to
be
super
clear:
the
engine,
what
we
used
within
the
SharePoint
framework
we
laid
it
on
feature
framework.
It's
exactly
the
same.
B
So
when
we
were
activating
the
SharePoint
frame
rate
of
solution
with
an
assign,
it
is
the
same
engine
as
it
is
for
farm
solutions
or
Adams
if
there,
if
there
are
provisioning
assets,
so
the
capabilities
are
exactly
the
XS
there's
only
subset
of
elements
which
are
supported.
So
the
subset
of
elements
are
field,
content,
cyclists,
custom
action
and
I
think
that's
it
last
list
to
know
system
players
and
therapists.
That
would
be
a
horrible
thing,
and
so,
but
it's
dough,
it's
documented
it
in
the
depth
of
circumcise
SharePoint,
what
attica
elements
with
source
for
it.
A
Yeah,
thank
you
outstanding,
and
so
now
I
want
to
do
a
quick
sort
of
demo
and
I
said
this
is
very
early.
Look
at
some
of
the
graph
work
I've
been
doing
but
wanted
to
get
this
out
in
front
of
the
community
to
get
feedback
before,
like
I
said
it
gets
built
out,
which
then
makes
it
much
harder
to
change
the
overall
shape
of
things.
So
this
only
exists
on
my
computer.
A
That
is
the
version
right
now.
It's
version
1.0
or
v10
is
out
there,
so
I'm,
exposing
a
v1
property
and
then
that
v1
property.
If
we
go
to
that-
and
so
this
very
much
follows
if
you've
ever
looked
at
the
JavaScript
core
library
source
code,
it's
almost
exactly
the
same
kind
of
style
at
this
point,
but
with
no
I
haven't
built
out
any
of
the
methods
in
any
of
that.
Yet
right,
so
let's
get
the
basic
shape
of
it
and
then
it's
easy
to
sort
of
build
out
the
methods.
A
So
we've
got
groups
which
it
happens
to
be
one
of
the
things
we
can
query
through
the
graph
client
in
SharePoint,
the
HTTP
graph
client.
So
we've
got
groups
and
you
can
see
again
we
can
just
chain
these
objects.
I.
Think
that's!
For
me.
A
very
fundamental
part
of
kind
of
the
the
fluent
API
is
the
ability
to
chain
these
objects
together.
So
we
go
V
one
two
groups
and
then,
if
we
look
at
groups,
groups
is
again
I,
don't
have
any
of
the
properties
or
any
no
methods
coded
out.
A
Some
of
this
get
parents
will
probably
be
the
same,
clone
and
so
forth,
but
what
I
want
to
get
down
here
to
is
get,
and
you
can
see
a
lot
of
the
other
stuff
is
missing,
so
there's
no
post
puts
or
deletes
or
any
of
that
stuff
I've
got
get
right
now
and
you're
going
to
see
I'm,
creating
a
new
client
which
is
a
graph,
HTTP
client
and
then
I'm
calling
client
get
and
I'm
saying
passing
at
the
URL
and
passing
the
options.
This
will
likely
change
as
well.
A
I
think
it
makes
sense
to
build
up
a
request
pipeline
in
the
same
way
we're
doing
for
SharePoint,
but
for
now,
like
I
said
this
is
very
early
days.
Just
kind
of
wanted
to
see
will
will
we
be
able
to
build
a
query
and
run
it
now,
this
just
to
be
a
little
more
confusing
this
graph.
Http
client
is
not
the
SharePoint
framework
one.
It's
actually
this
graph
HTTP
client,
which
again
is
mostly
commented
out,
but
our
implementation
in
this
point
at
this
time.
A
So
the
idea
again,
if
you've
looked
at
the
source
code
for
the
SharePoint
side
of
things,
the
implementation
is
pluggable
right
now
what
I'm
doing
is
grabbing
our
runtime
configuration
and
the
SharePoint
context
which
we're
providing
to
the
library
and
I'm
grabbing
the
graph,
HTTP
client
directly
from
SharePoint
framework
and
then
I'm
calling
its
method
with
the
URL
and
options
like
I
said,
will
likely
need
to
rebuild
or
build
around
this
some
retry
logic
and
things
like
that,
but
again,
very
early
days.
So
how
does
this
get
used?
A
So
let
me
pull
over
this,
which
is
a
nice
hello,
world
web
part
and
one
of
the
things
you
could
do.
If
you,
if
you
weren't
aware,
is
you
can
actually
npm
install
from
local
files,
so
I've
MPM
installed
my
current
version
of
the
javascript
core
library.
Soon
on
my
machine
into
my
hello
world
web
part,
this
is
a
straight
boilerplate.
I
created
a
hello
world
web
part
using
the
yo
generator
and
that's
what
I
have
here
until
we
look
at
the
actual
hello
web
part
file,
so
I've
done
the
on
an
it
set
up.
A
That
means
being
able
to
set
the
base
URL
correctly
for
our
queries
and
for
graph
it
means
getting
to
grab
that
graph
graph
client
from
SharePoint
framework,
and
so
now
we've
got
a
little
code
snippet
here
that
is
so
PNP
graph,
and
this
is
another
place.
I'd
like
a
little
bit
of
feedback
from
folks
is
right.
Now
the
structure
is
PNP
graph
dot,
v1
groups
get
etc.
But
then
you
know,
after
that
it
remains
very
much
the
same
and
we
would
do
we're
not
doing
any
parsing.
A
So
this
is
going
to
be
the
raw
response
from
the
graph
client
at
this
point,
but
we
would
end
up
doing
some
parsing,
just
as
we
do
for
SharePoint
responses
to
make
things
easier,
but
you
will
get
the
oops
it's
not.
Oh,
it's
P
and
P.
So
now
you've
got
your
graph,
so
one
of
the
like
I
said
feedback
places
is
right.
Now
it's
v1
dot
groups
I
could
see
it
being
groups
dot
stuff,
but
we
need
a
way
to
swap
out
the
versions.
A
So
is
that
something
we
want
to
inline
like
this
or
is
that
something
we
want
as
part
of
a
configuration?
Is
that
something
we
want
to
do?
Pnp
graph,
I'm
passing
a
string
that
could
be
an
object
or
a
configuration
object
or
whatever
dot
groups
would
be
another
style
to
do
it.
So
you
know
it's
something
we
could
do
in
the
setup
method.
You
could
specify
a
graph
version,
something
like
that.
So
anyway,
not
something
we
have
to
decide
right.
The
second,
but
something
I
am
looking
for
feedback
on
from
the
community.
A
What
would
be
easiest
or
what
makes
the
most
sense
as
we
move
forward,
because
I
think
it
also
makes
sense
to
as
possible
expose
the
beta
things.
So
it
would
be
something
like
P
and
P
dot
graph
dot
beta
instead
of
v1
dot.
Other
things
right
so
you'll
be
able
to
do
more
things
in
beta
or
do
different
things
in
beta
as
well.
So
I
think
several
different
approaches
to
that
problem.
But
I
think
you
know
it's
just
one
of
those.
A
We
all
need
to
kind
of
come
together
and
make
a
decision
as
a
community
as
what
we'd
like
to
see
there.
But
really
what
we
want
to
see
is:
is
this
actually
do
something
so
I've
got
the
gulp
serve
running
for
this
project
already
and
if
I
go
I'm
just
going
to
refresh
this,
because
this
is
probably
pretty
stale
at
this
point.
So
this
is
my
workbench
in
my
SharePoint
Online
site.
So
this
is
not
the
local
workbench.
A
A
We
can
wrap
that
in
so
again
very
early
days,
but
did
want
to
share
this
because
it's
something
we've
been
talking
about,
and
you
know
it
kind
of
solicit
feedback.
Honestly,
because
it's
early
enough
that
we
can
get
that
feedback
and
then
you
know,
make
the
changes
and
things
before
we've.
You
know
really
written
out
a
ton
of
code
and
then
we
have
to
change
it
and
we
all
know
the
fun
of
trying
to
change
a
giant
codebase.
A
So
trying
to
avoid
that,
but
also
trying
to
end
up
with
the
best
ultimate
result
for
everybody
in
the
community
so
going
through.
We
don't
have
much
time
for
the
open
discussion,
so
I'm
going
to
skip
over
that
we
have
some
great
stuff
in
the
IM
window.
As
always.
So
thank
you
do
if
you
have
questions
hit
up
the
Gitter
channel
or
the
sharepoint
tech,
community
or
twitter,
or
the
issue
list
for
any
of
the
libraries.
If
you
have
comments
on
the
graph
stuff,
I
just
showed
definitely
welcome
those.
A
There
is
actually
already
an
issue
in
the
issues
list
for
the
JavaScript
core
library.
That
would
be
a
great
place
to
drop
your
thoughts
about
what
I
just
showed
as
well.
As
you
know,
any
feedback
and
ideas
on
how
to
kind
of
grow
that
and
then
once
we
kind
of
get
the
core
stuff
together,
we
can
open
that
up.
So
folks
can
really,
you
know,
start
to
add
stuff,
and
we
can
get
the
community
contributions
to
help
build
that
out.
A
So
our
next
meeting
will
be
July
6th.
As
I
said,
we
need
to
get
the
invite
updated
for
the
new
fiscal
year,
the
new
Microsoft
fiscal
year,
so
we
will
be
doing
that
and
we'll
tweet
out
when
the
invite
is
updated,
it
will
be
the
same
link
that
it
currently
is.
So
if
you
have
that
link
or
it's
the
same
link,
that's
on
the
patterns
and
practices,
dev
office,
column,
slash
patterns
and
practices
or
patterns
and
practices,
I
think
page.
That
link
will
still
work.
That
link
will
still
get
you.
A
The
right
invite
so
look
forward
to
seeing
everybody
in
July
and
I.
Think
that's
all
from
me.
So
I
just
want
to
say
thank
you
to
everybody.
Thank
You
Velan
for
amazing
demo,
really
cool
to
see
the
new
provisioning
stuff
in
action,
and
then
they.
So.
Thank
you,
of
course,
always
for
the
great
SharePoint
framework
updates,
always
look
forward
to
that
and
again
want
to
remind
folks
if
you,
if
you're
doing
some
cool
work,
let
us
know
and
sign
up
for
a
demo
on
this
call.