►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 7th of June. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
This one includes what was released on the SharePoint Framework v1.5 and also what is the current plan for SharePoint Framework v1.6.
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Hello
and
welcome
the
SharePoint
framework
at
JavaScript
special
interest
group
bi-weekly
sync,
it
is
June
7th
2018.
We
are
almost
halfway
through
the
year
of
2018,
which
is
kind
of
crazy,
but
we
got
another
great
meeting
for
you
here
today,
but,
as
always,
we're
gonna
start
off
with
what
this
is
all
about.
A
little
bit
of
background
for
folks
that
might
be
new
to
the
call
or
watching
these
videos.
A
For
the
first
time
on
the
YouTube
channel,
we
are
part
of
the
larger
SharePoint
patterns
and
practices
program,
and
we've
started
these
special
interest
groups
to
give
us
an
opportunity
to
focus
on
some
specific
areas.
We
were
sort
of
having
this
problem
with
a
victim
of
our
own
success,
in
that
we
have
these
monthly
calls,
and
we
just
couldn't
cover
all
of
the
stuff
we
wanted
to
do
across
the
sea.
A
So
two
links
down
there
at
the
bottom.
We've
got
a
kam
SSP
P&P
community.
That
will
take
you
to
the
microsoft
tech
community
for
all
things,
SharePoint.
So
that's
sort
of
the
the
SharePoint
corner
of
the
Microsoft
tech
community.
That
is
a
really
great
place
to
ask
general
questions.
How
do
I
questions
that
aren't
necessarily
related
specifically
to
a
bug
or
an
issue
in
the
library
and
start
one
second
I'm
checking
my
recording
is
still
running.
I
just
got
a
weird
message
in
my
recording.
A
It
failed
so
we'll
see,
but
so
the
community
they're
a
great
place
to
ask
general
questions
and
get
involved
and
seek
some
guidance
around
your
architecture,
ideas
or
maybe
how
to
pursue
different
problems
and
the
second
link
there.
The
SP,
dev
Doc's,
will
take
you
to
the
developer,
documentation
all
up
for
SharePoint.
A
So
if
you're
new
to
the
SharePoint
framework
want
to
get
started
with
that,
you'll
find
some
great
tutorials
and
guides
on
how
to
get
up
to
speed
with
SharePoint
framework,
but
as
well,
if
you're
doing
see
some
development,
the
manage
code,
development,
even
on-premises,
deploying
your
solution
packages
you'll
find
the
guidance
and
documentation
for
those
things
there
as
well.
So
do
please
check
out
the
documentation
and
do
please
check
out
the
Microsoft
tech
community.
A
What
are
we
going
to
cover
on?
Today's
call
will
have
as
always,
an
engineer,
an
update
from
SharePoint
framework,
so
we
will
have
we've
just
released.
1.5
of
the
yeoman
generator,
which
has
some
great
new
features
face,
is
going
to
talk
us
through
those
we've
got
the
PNP
J's
client
libraries
update.
We've
got
an
update
with
live
demo
on
the
office,
65
CLI.
That
was
a
new
release
just
this
week.
I
believe
just
this
week,
our
very
end
of
last
week
for
the
office,
365,
CLI
and
then
demos
we've
got
Andrew.
A
Connell
is
gonna,
do
dynamic
data
and
that's
using
the
SharePoint
train,
work,
1.5
latest
release
and
then
velan
is
gonna.
Do
a
showing
how
to
use
the
jest
test
framework
with
SharePoint
framework,
and
that's
something:
we've
gotten
a
lot
of
quit.
Some
good
questions
on
from
folks
out
there
in
the
community
on
how
do
I
test
my
SharePoint
framework
things
and
velen's
gonna
show
a
great
example
of
how
to
do
that.
But
just
and
then
we
should
have
some
time
at
the
end
for
Q&A.
So
look
forward
to
our
agenda
this
week
and
now.
A
I
will
hand
things
over
to
know.
I
will
hand
things
over
to
myself
to
quickly
mention
opportunities
to
participate
in
the
SharePoint
framework
and
the
special
interest
group
here.
So
we
really
encourage
these
community
demos
so
demo
a
SharePoint
framework
solution,
demo,
something
related
to
PN
pjs
demo,
those
two
things
together,
which
is
always
a
nice
thing
to
see.
But
for
me
the
demos
are
one
of
the
most
valuable
parts
of
these
calls.
A
Is
it
it
lets
us
all
of
us
in
the
community,
see
what
other
folks
are
working
on
and
doing,
and
it
gives
us
great
ideas
things
we
can
do
in
our
own
projects.
Maybe
learn
some
new
techniques,
so
I
very
much
encourage
you.
I
know
lots
of
people
out.
There
are
doing
some
really
awesome
things
in
SharePoint
framework
and
with
client-side
development.
A
So,
if
you'd
like
to
share
those
things,
please
do
reach
out
to
us
reach
out
to
myself
reach
out
to
vasa
about
doing
a
demo
and
we'll
get
you
just
as
soon
as
we
can
on
the
agenda.
We
can't
always
get
you
perhaps
like
on
the
next
week
next
instance
of
the
call,
but
will
very
much
get
you
on
as
soon
as
we
can
and
would
encourage
you.
Please
do
reach
out
with
those
demos,
they're
really
awesome
to
see
what
folks
are
doing.
You
can
as
well
contribute
on
github,
so
you
can
contribute
to
p.m.
A
PJs
on
github.
You
can
contribute
questions
and
feedback
to
the
SP,
dev
Doc's
or
those
repositories
on
github.
You
can
submit
new
samples
for
the
SharePoint
framework
areas
and
would
remind
folks
please
do
come
onto
the
call
on
mute
if
you
don't
mind
and
and
then
as
well
all
up
on
what
we're
doing
with
the
programs.
Please
we
do
welcome
the
feedback
you
have
and
the
ideas
you
have
to
do,
what
we're
doing
better
so
not
just
specific
to
the
given
libraries
or
specific
to
SharePoint
framework,
but
really
about
the
program.
A
How
can
we
communicate
better?
How
can
we
do
a
better
job?
What
can
we
do
to
improve
our
delivery
or
documentation,
etc?
So
really
appreciate
all
that
feedback.
We
can't,
as
I
always
say,
always
act
on
each
piece
of
feedback
immediately,
but
we
do
take
them
to
heart.
We
do
listen
to
that
feedback
and
we
do
try
and
respond
as
best
we
can
to
what's
going
on
so
stepping
now
I
will
hand
things
over
to
visa
for
an
update
on
SharePoint
framework.
B
We
go
I'm,
hearing,
I'm
hearing
myself,
yes
technology,
so
let's
actually
talk
about
the
SharePoint
framework
and
the
latest
on
this
side.
So
my
point
in
here
is
talk
about
the
Oberer
21.5
release
which
went
live
yesterday,
one
day
before
yesterday:
Tuesday,
yes,
Tuesday
on
my
time
and
then
a
few
other
things
related
on
SharePoint
framework.
B
Now
so
let's
get
moving
so
one
thing
what
we
actually
already
shared
last
week,
I'm
just
or
II,
read
this
week
actually
just
some
numbers
from
a
May,
because
we
kind
of
a
past
the
main
month
as
or
some
number
so
they
didn't
on
SharePoint
community,
a
shape
on
deaf
community
from
May
sign.
So
on
YouTube
channel
we
had
one
hundred
and
fifty
seven
thousand.
What's
time
minutes
and
used
on
twenty
seven
thousand.
B
We
have
thirty
eight
thousand
unique
visitors
and
github,
and
this
is
growing
quite
fast
as
well,
and
it's
great
to
see
the
interest
of
or
let's
say,
people
finding
our
SharePoint
flavor
of
samples
and
share
fun
samples
in
github,
which
is
really
really
great.
On
video
from
microphone
we
actually
crew
again
at
ten
db10.
B
Sorry
double-digit
numbers
so
we're
now
in
eight
eight
hundred
and
ninety
eight
thousand,
who
are
pretty
close
and
hitting
the
900,000
or
1
million
in
the
views
in
the
dust
of
my
shafted
cog,
which
is
really
great,
because
that
shows
that
people
are
finding
their
new
location
and
also
that
the
information
is
hopefully
valuable.
If
something
is
missing,
please
let
us
know
so
we're
able
to
address
those
gaps
are
related
on
your
things
now
to
be
amply
reusable
components.
B
This
includes
the
PMPA
sites,
core
powershell,
PM
PJs
and
all
of
that,
and
they
were
used
in
12,000
tenants,
so
open
source
community
stuff
was
used
in
more
than
12,000
tenants
and
they
generated
more
than
or
pretty
close
than
10
billion.
It's
a
debate,
requests
which
is
pretty
cool
in
general.
Now
on
other
topics,
just
a
reminder:
there's
always
new
people
in
this
course
akms
SPF
dukes
are
official
documentation,
a
source
where
you
can
find
documentation,
guidance
from
sharepoint,
adding
sharepoint
framework.
B
Our
schema
reference
feature
xml
reference,
if
you're
still
on
doing
that
stuff,
hopefully
not
the
provisioning
reference,
and
all
of
that
so
and
we're
constantly
evolving
this
documentation
based
on
your
input.
So
please
keep
the
feedback
coming
and
tell
us
if
something
is
missing
or
something
isn't
sufficient
enough
will
absolutely
make
sure
that
we
improve
the
documentation.
The
second
thing
related
kind
of
on
that
one
as
well.
B
It's
the
issue
list,
so
we've
been
even
in
internal
in
SharePoint
engineering,
we've
been
having
an
always
every
now
and
then
meditates
on
this
issue
list,
because
this
is
causing
Oberst
a
lot
of
traffic
on
our
side
as
well,
but
pretty
reasonably.
We
have
accrete
completely
to
keep
this
one
and
this
process
up
and
running,
because
it
is
super
valuable
for
people
who
do
not
have
a
premiere
support,
call
or
premiere
support
support.
B
The
whole
point
of
this
one
is
that
if
you
run
into
any
random
issues
in
SharePoint,
Online,
you're
able
to
actually
reach
out
directly
to
the
SharePoint
engineering-
and
this
is
for
developer
topics.
So
if
you
run
into
random
issue
in,
let's
say
a
functionality
on
the
UI
something
isn't
working
properly,
please
use
the
tenon
admin
services
for
opening
up
a
super
case
using
official
channels
and
the
right
channels.
B
So
you're
able
to
report
issues
were
able
to
jump
on
the
issues
and
we're
trying
to
tree
us
there's
actually
multiple
times
in
a
day
officially,
which
we
asked
our
BSO
tasks,
which
are
generated
based
on
this
twice
a
week
pretty
recently,
thank
you
for
those
who've
been
reporting
this
we
were
able
to
identify
as
an
example,
a
pretty
big
issue
related
on
Azure
ad
application
in
the
creation,
and
that
was
fixed,
then,
in
a
matter
of
hours.
That
was
pretty
cool
good
example
of
a
successful
reporting
of
the
other
issues.
B
Now
moving
on
on
things,
SharePoint
framework
every
now
and
then
and
still
we're
getting
questions.
Is
this
really
the
model
what
people
are
using?
Is
this
really
the
thing
what
I
should
be
concerned
concentrating
on?
And
the
answer
is
yes,
so
everything
in
SharePoint
Online
in
the
modern
experience
is
or
in
SharePoint
2019,
which
goes
live
pretty
soon
or
well?
Yes,
2019!
B
B
There
will
be
also
the
enterprise
solutions
from
SharePoint
can
be
hosted
in
Microsoft
themes,
which
is
a
pretty
cool
thing,
we're
working
on
that
one.
We
will
have
a
dev
kitchens
and
everything
else,
but
hopefully,
by
the
time
of
ignite,
we
can
actually
get
stuff
available
for
you
for
testing
and
then
release
that
after
that,
one
is
resolution
for
my
stuff
steams
to
SharePoint.
B
That
means
that
whatever
you
see
in
the
is
VA
selection
in
themes
can
be
actually
used
in
the
inertia
pond
on
one
side
as
well,
which
is
pretty
cool
global
deployment
of
SharePoint
framework
extensions.
This
means
that
you're
able
to
push
those
extensions
to
SharePoint
Science
in
your
tenant
from
one
centralized
location
currently
scheduled
for
1.6
of
the
SharePoint
framer,
and
it
is
pretty
much
done
as
though
it
should
be
there
as
well.
I'll
come
back
on
that
one
in
a
second
dynamic
data
in
SharePoint
framework
components.
B
This
is
something
which
AC
is
going
to
demonstrate
today
within
with
the
one
sample
which
is
available
for
you,
because
the
dynamic
data
it
was
available
well
was
released
to
preview
as
part
of
SharePoint
framework
1.5,
and
then
the
SharePoint
framework
is
in
the
SharePoint
2019,
as
SharePoint
2019
has
a
native
modern
experience
is
supported,
which
is
really
really
cool
and
2019
will
be
released
to
theta
our
preview
within
well
during
the
summertime.
So
in
summer,
2000
air
18
now
moving
forward
ship
on
2019,
sorry
SharePoint
framework
1.5.
B
This
was
released
two
days
ago,
so
Tuesday
and
20
from
1.5
basically
had
the
following
capabilities.
So,
first
of
all,
we
decoupled
the
project,
scaffolding
from
the
package
management,
which
basically
means
that
you're
able
to
also
use
a
yarn
or
B
NPM.
If
you
prefer
to
do
so,
and
this
technically,
you
can
absolutely
keep
on
using
NPM
I'm
using
NPM,
but
there's
this
always
those
people
who
actually
want
to
use
yarn
or
PNP
em
as
an
example,
and
that
is
now
an
option
starting
from
1.5.
B
Now,
internally,
in
SharePoint
engineering,
we
actually
use
P
and
PM
because
that's
slightly
faster
based
on
our
based
on
the
structure,
what
we
are
using
and
it
is,
it
doesn't
actually
require
that
much
space
in
the
disk
or
storage
within
your
computer
again
slightly
debatable.
It
depends
on
the
design.
Slightly
depends
on
the
on
the
solution,
what
you
are
actually
building
now.
The
second
thing
is
the
support
for
beta
API,
so
all
of
our
beta
stuff
is
now
in
a
separate
location.
B
So
you
have
to
actually
execute
this
plus
beta
command
in
command
line
to
be
able
to
provision
and
scaffold
projects
and
solutions
which
have
applauded
the
beta
options
or
preview
capabilities
like
if
you
want
to
use
the
dynamic
data
option,
you
would
have
to
use
the
plus
beta
switch
to
get
things
available.
There's
a
support
for
custom
generators,
so
you
can
actually
add
additional
options
to
the
wizard.
You
can
add
additional
files
and
modify
output
files
in
the
original
generator.
B
B
So
moving
on
on
this
one
step
at
a
time
right
now
we're
still
kind
of
a
in
the
in
the
ready
to
run
pretty
soon
or
ready
to
crawl
and
start
actually
building
this,
and
so,
but
pretty
soon
you
can
see
some
actions
and
initial
versions
available
in
the
generator
SPX.
It's
SP
FF
people
in
the
PNP
organization.
B
Eventually
we
were
released
and
a
known
in
paying
packets
on
this
one
and
you
don't.
You
can
install
that
one
which
has
a
10
dependence
on
out
of
the
box.
Sp
affects
humans
generator,
and
then
you
execute
this
one.
This
generator
and
you're
able
to
select
an
additional
options.
You're
able
to
select
angular
elements
of
you
chase,
just
as
the
framework
to
pay
provision.
So
pretty
cool
it
will.
It
will
require
stills
and
work.
Obviously,
because
there's
nothing
really
done
at
this
point,
but
it's
heading
to
the
right
direction.
B
Now
the
one
thing
what
I
promised
to
actually
talk
about
in
the
Twitter
like
10
minutes
before
the
score,
but
I
created
the
slides
slightly
earlier
today,
was
also
the
current
plan
for
1.6.
So
1.5
went
live
two
days
ago
on
Tuesday
one
point:
six
is
planned
to
go,
live
on
the
end
of
July,
so
not
too
far,
but
it's
like
what
two
and
A
one
and
a
half
months,
one
and
a
half
months
roughly
from
now.
But
what
we're
planning
to
do
now
is
that
1.7
is
then
coming
out
on
ignite.
B
So
hopefully
we
can
get
this
one
point
six
out
before
the
if
night
release
and
this
one
then
we'll
add
additional
capital,
it
is
like
the
tenant
by
deployment
of
shipment
framework.
Extensions
will
be
included
on
that
one,
but
looking
in
the
doing
GA
on
the
craft
and
third
party
API
calls
hopefully
on
this
one
and
ta
for
dialogue
framework,
which
is
still
in
beta
as
well.
It's
partly
technically
also
a
Miss
from
our
side.
It
should
have
actually
kanji
in
1.5,
but
officially
in
our
documentation
is
still
marked
as
the
beta.
B
So
we
will
absolutely
get
rid
of
that
in
ind.
Our
code
as
part
of
the
1.6
release
will
also
pump
up
the
reactor
version
to
16,
and
it
will
should
be
a
preview
version
of
the
socket
IO
capabilities
which
again
basically
they
it
will
make
you
easier
to
tie
your
code
in
the
changes
within
a
list
and
libraries
shape.
B
1
2019
support,
hopefully,
will
be
there
at
that
time
and
then
there's
quite
a
lot
of
other
things
which
are
in
the
let's
say
in
quotes
in
the
pipeline
and
but
I
can't
share
them
at
this
point
again,
but
there's
a
lot
of
interesting
stuff
available.
Hopefully,
like
said
by
end
of
July,
we
can't
promise
that
all
of
this
will
be
there.
B
It
might
be
that
there
will
be
some
other
significant
things
as
well
and
I
can't
promise
you
that
it's
end
of
July
it
might
be
early
August
because
well,
even
you
never
know
if
we
run
into
unexpected
situations
or
issues
here
and
there
and
so
and
those
always
in
vector
schedule.
But
this
is
the
current
plan
and
like-
and
it
looks
pretty
ok
and
all
of
the
capabilities
are
looking
well.
They
already
work
and
we're
already
working
on
making
everything
polished
and
ready
to
be
released
in
July.
B
So
there's
a
quick
question
from
Kevin
I've
missed
a
lot
of
the
questions,
probably
on
I
window,
but
Kevin
is
asking
on
the
eta
on
the
on
the
team.
Sweat
part
I
would
say
we'll
right
now.
The
target
is
get
the
team,
sweat
parts
in
the
creation
to
preview
in
ignite
so
1.7,
and
then
we
do
not
have
a
TA
timeframe
at
this
point,
because
obviously
we
might
hope
that
the
GA
and
in
production
support
will
be
by
Christmas.
B
But
what
if
we
were,
we
will
run
into
some
highly
unexpected
situation
or
your
feedback
is
horrible.
You
hate
us
and
we
get
it
and
reschedule
or
a
planned
the
whole
thing.
That's
why
we
cannot
actually
give
an
exit
date
because
we
can't
predict
the
future
and
your
paper
but
we're
getting
there
we're
getting
there
couch.
B
Look
how
quickly,
under
on
Giuliana's
question
what
it
means
to
socket
IO,
so
we
will
have
a
a
more
simplistic
way
for
you
to
subscribe
on
socket
IO
events
in
the
list
in
library.
So
you
can
basically
say
hey
this
list
that
that's
a
item
or
that
this
list,
whenever
something
is
out
there,
give
me
an
event
and
you
actually
get
that
to
happen
extremely
is
I
technically
you
can
do
that
already
today.
B
I
think
Giuliana
actually
has
a
great
sample
and
that
one,
if
I
remember
correctly,
but
we're
trying
to
make
that
as
simple
as
possible
for
other
people
as
well,
without
the
need
of
a
third
party
API
killing
hosted
somewhere
in
a
sure.
So
the
whole
point
is
the
simplification
of
all
of
the
all
of
the
needed
plumbing
huge.
A
A
quick
update
then,
on
the
PJs
client-side
libraries
we
did
announced
last
week
on
Tuesday
the
at
P
and
PSP
taxonomy,
really
invite
folks
to
give
that
a
try,
download
that
check
it
out.
It
gives
you
a
fluent
way
to
access
managed
metadata
in
SharePoint.
It
has
no
dependencies
outside
of
the
PNP
jeaious
libraries,
so
you
don't
need
to
include
the
s
P
dot,
taxonomy
or
any
of
that
stuff.
Do
please
check
that
out.
Give
us
some
feedback
I,
think
it's
a
great
addition
to
what
we're
doing
and
I'm
excited
to
have
gotten
it.
A
Fine
release
that
kind
of
was
teasing
it
for
a
little
bit
and
we
will
have
a
full
demo
of
that
on
the
community
call
which
is
next
Tuesday.
The
monthly
P
and
P
community
call
so
you'll
be
able
to
see
that
in
action
and
we'll
talk
through
that,
a
little
bit
on
that
call,
CD
nsj
support
is
still
in
the
works.
I
feel
like
I've,
been
saying
that
for
months,
because
I
have
at
this
point,
but
still
waiting
on
those
folks
to
get
things
updated
or
get
things
merged,
they're,
just
really
overloaded.
A
So
no
disrespect
to
them,
but
just
waiting
on
that
at
that
point
and
I
have
updated
our
pull,
requests
there
to
include
the
new
libraries,
so
the
SP
tacks
on
me
and
the
SP
client
SPC,
so
they'll
get
into
the
CD
nsj
once
that
stuff
gets
merged,
we
do
have
weekly
beta
releases
on
Fridays.
This
Friday
is
going
to
be
a
major
release,
so
you'll
have
version.
A
1.1.1
will
get
released
this
Friday
and
that
will
include
some
fixes,
but
not
a
whole
ton
of
stuff,
since
we
just
did
a
big
release
last
Tuesday,
but
we
have
we'll
have
some
good
stuff
in
there
and
then
do
check
the
changelog
we're
committed
to
keeping
that
updated
regularly
with
each
release
and
as
we
publish
the
betas,
so
that's
going
to
have
the
latest
of
what's
gotten
added
to
the
library,
so
a
big
reminder
SPP
and
PJs.
The
last
version
of
that
is
in
July.
So
it
is
time
if
you
have
not
migrated.
A
It
is
time
to
start
migrating
to
the
PM
PJs
libraries.
It's
not
a
big
deal.
We
do
have
a
transition
guide
and
the
short
video
to
help
you
there.
If
people
have
questions,
please
just
post
those
as
issues
we're
very
willing
to
help,
but
it
is
time
to
start
migrating.
So
after
July,
if
you
have
issues
with
SP,
P
and
PJs,
we
are
not
going
to
fix
them.
We
are
essentially
gonna
leave
that
library
in
place,
as
is
so,
it
won't
break
any
of
your
existing
projects.
A
You'll
still
be
able
to
run
and
install
and
and
work
on
your
existing
code,
but
will
no
longer
be
enhancing
or
updating
or
maintaining
SP
P
and
PJs
actively
after
July.
So
we've
been
warning
that
for
months,
so
a
little
bit
firmer
warning
here
today.
It's
time
to
start
migrating,
so
do
think
about
that.
Do
start.
A
Looking
at
moving
projects,
we
worked
hard
to
make
that
not
a
huge
huge
effort
on
your
part,
so
hopefully
that'll
be
fairly
smooth
for
folks
looking
to
migrate
and
again,
if
you
have
issues
transitioning,
please
let
us
know
we
definitely
want
to
help.
We
definitely
want
to
smooth
that
out
as
much
as
we
can
couple
links
down
there
at
the
bottom.
Pnp
github
got
it
you,
the
docs
for
the
PJs
libraries,
that's
a
great
place
to
start.
A
We've
got
guides
on
getting
started
with
each
of
the
various
components
how
to
get
things
installed
and
how
to
use
them
once
you've
got
them
installed.
As
always,
if
you
have
questions
or
you
find
stuff
missing
in
the
docs,
please
do
let
us
know
so
we
can
get
that
updated,
which
benefits
everybody.
The
hashtag
ppj
us
on
twitter.
You
can
always
follow
me
on
twitter
at
mediocre
bowler.
A
I
don't
post
a
ton
of
stuff,
so
you
don't
get
a
lot
of
spam
for
me,
but
that
is
how
you
will
hear
about
the
updates
and
releases
on
the
pjs
libraries.
So
that's
definitely
a
great
way
to
stay
up-to-date
on
when
things
update
on
our
side,
so
stepping
up
office,
365
CLI,
updates
new
version
released
this
week,
1.3
with
support
for
group
of
fiying
sites
managing
and
apply
themes,
managing
files
and
folders
sending
email
on
behalf
of
the
current
user
and
managing
Azure
ad
group
settings,
as
well
as
simplified
deployment
for
sharepoint
solution
packages.
A
So
some
really
outstanding
additions
to
the
office.
365
CLI,
which
keeps
getting
better
and
better
with
each
release.
This
is
also
a
great
opportunity
if
you'd
like
to
join
in
and
contribute
on
a
project.
The
office
365
CLI
is
a
great
way
to
do
that.
It's
got
a
lot
of
issues
and
issues
list.
Waldeck
has
done
a
great
job
of
putting
those
in
there
and
each
one
is
fairly
atomic
like.
So,
if
you
want
to
add
a
command,
you
don't
have
a
ton
of
extra
work
to
do.
A
A
B
A
We're
not
deleting
it
out
of
github
or
anything,
it's
not
disappearing,
but
it
is
it's
just
not
something
I'm
gonna
focus
on
anymore.
So
if
you
report
issues
and
wonder
why
nobody
is
responding,
that
is
why
I'll
tell
you.
It's
been
a
big
challenge
to
try
and
maintain
the
two
libraries
in
parallel
for
six
months.
I
think
it
was
the
right
thing
to
do,
but
I'm
excited
to
only
maintain
one
library,
let's
say
yeah.
A
Yeah,
absolutely
we've
got
a
bunch
of
folks
helping
out.
We
get
a
bunch
of
support
from
folks
and
pull
requests
and
really
appreciate
everybody
that
jumps
in
and
helps
out
there.
So
it's
not
just
me
but
on
behalf
of
everybody
I
think
we're
all
excited
about
maintaining
a
single
library,
so
no
update
on
the
reusable
controls
this
week
and
so
we'll
go
right
into
the
demos
and
Andrew.
If
you
are
ready,
AC
I'm.
C
A
C
So
I
sacrifice
to
the
Skype
for
business
demo
gods.
So
let's
hope
that
everything
should
be
okay.
Today,
sorry,
it's
the
first
things
of
all.
Thanks
for
a
give
me
the
opportunity
to
show
this.
This
is
I'm
gonna
do
my
best
Waldeck
impersonation
today
bees.
This
is
really
wild
example
that
I'm
filling
in
for
him
as
he
couldn't
he
couldn't
be
here
today.
C
First
of
all,
so
I'm
gonna,
explain
kind
of
what
dynam
did
is
real
briefly
I'm,
going
to
show
you
a
working
sample
of
it
and
then
I'm
gonna
walk
through
the
code
a
little
bit
here
and
all
this
code
you'll
be
able
to
grab
I'll
show
you
where
you
can
grab
that
in
just
a
bit.
So
first,
what
dynamic
data
is
all
about.
Is
it
gives
you
the
ability
to
have
one
component
on
the
page
that
acts
as
a
publisher?
C
It's
gonna
publish
notifications
that
it
things
within
it
have
changed
that
goes
up
to
the
SharePoint
framework,
and
the
SharePoint
framework
can
then
notify
any
other
component.
That
is
on
the
page,
and
it
wants
to
be
notified
when
those
things
change.
Those
are
our
consumers.
So
if
you
are
a
traditional
or
longtime
SharePoint
developer
and
you've
done
the
webpart
connections,
it's
a
very
similar
concept
to
that
I
like
to
think
of
it
as
almost
a
client-side
service
bus,
but
without
passing
data
back
and
forth.
Just
passing
notifications
that
things
change.
C
So
in
order
to
use
this
today,
when
you
go
to
create
your
project,
you're
going
to
need
to
add
in
this
plus
beta
on
the
yeoman
generator,
and
what
that's
going
to
do
is
that
when
that
creates
your
project,
it's
going
to
include
all
the
different
libraries
that
are
that
have
the
the
beta
features
available
to
us
in
the
the
SharePoint
framework
to
us.
So
that's
one
of
the
new
changes
that
messages
talked
about
with
respect
to
the
SharePoint
framework,
1.5
update.
C
So
let
me
show
you
first
how
this
works
and
ignore
this
whole
licensing
thing
up
here.
We
don't
we're
developers,
we
don't
care
what
the
licensing
stuff
right
now.
So
this
is
what
I've
got
is
I've
got
three
webparts
that
are
on
the
page
and
what
you
have
is
over
here.
We'll
have
a
list
on
on
this
site
called
events,
and
this
webpart
is
pulling
from
that.
The
web
part
here
on
the
left
that
says
upcoming
events.
This
is
pulling
from
those
different
from
that
SharePoint
list
called
vets
over
here
on
the
event
details.
C
C
Webpart
the
event
details
web
part
will
then
reach
over
into
the
events
web
part
and
say
give
me
the
event,
property
that
you'd
suppose
and
then
it'll
show
that
detail
over
here.
I've
got
another
web
portal
that
farther
down
here
from
map
and
he
works
basically
the
same
way.
It's
just
that
he's
got
a
being
API
key,
that's
been
set
and
his
property
isn't
bound
to
the
location
property
over
here
on
the
other
web
part.
C
C
You
can
see
the
data
changing
again
down
here,
clearly,
not
in
Tampa
anymore,
we're
now
in
where
does
that
say,
we're
now
in
San
Diego
and
then
switch
over
to
San
Francisco
and
see
them
in
San,
Francisco
and
sure
enough,
there's
San,
Francisco
and
any
streets
that
anybody
might
recognize
as
Howard
Street,
I
guess
Fremont
day
as
their
Fremont
Street
and
Folsom
alright.
So
how
does
this
whole
thing
work?
It's
there's
a
bunch
of
code
in
this
sample
here,
but
it's
actually
pretty
simple.
C
So,
like
I
said,
we've
got
I
created
this
or
this
is
created
using
the
plus
beta
flag
argument
on
the
yeoman
generator.
So
it's
got
three
webparts
inside
of
it.
This
data
folder
is
just
a
collection
of
a
bunch
of
different
interfaces
that
we're
gonna
end
up
using,
but
I
got
three
different
webparts,
so
I
have
my
events,
one,
which
is
the
one
that
you
saw,
that
was
on
the
left.
So
if
I
look
at
this
web
part
here,
let's
come
down
here
and
look
at
the
web.
C
Part
and
I'll
show
you
the
interesting
stuff
with
this.
So
it's
a
standard
webparts!
There's
nothing
really
fancy
about
this
guy,
but
right
here
you
can
see
where
I'm
importing
in
a
dynamic
data,
controller
interface
and
a
dynamic
data
property
death
in
her
face
and
then
on
the
web
part
itself,
I'm
implementing
the
controller.
C
Now
you
don't
have
to
do
this
on
the
web
part
itself
and
in
fact,
I
would
probably
recommend
that
you
don't
use
a
separate
class
to
do
this,
but
this
is
just
a
demo
to
make
it
easy
to
understand
how
this
stuff
works.
What
this
basically
does
is
by
implementing
this
dynamic
data
controller
I
need
to
override
a
couple
different
methods,
things
like
or
implement
a
couple
different
methods,
so,
for
example,
I
need
to
implement
this
gift.
Property
value
is
one
that
I'm
in
it
need
to
end
up
implementing
now.
C
Another
thing
that
it's
got
so
it
further
down
is
right
here
on
the
onon
bit
method.
I'm
gonna,
set
this
guy
up
and
what
I'm
doing
by
setting
him
up
is
I'm
simply
saying
the
part.
That's
interesting
here
for
an
item.
Data
is
I'm
using
on
the
current
context,
a
new
object
or
new
member
called
dynamic
data,
source
manager
and
I'm,
saying
initialize
the
source
for
a
provider
of
data
on
the
page
and
I'm
passing
in
this
web
part,
because
this
Web
part
implements
this
dynamic
data
controller.
C
So
if
I
did
this
in
a
separate
class,
I'd
want
to
pass
in
an
instance
of
that
class.
So
how
does
this
work
well
once
I've
done
that
if
I
come
down
here
to
my
render
method,
what
you'll
see
is
I'm,
adding
in
a
react
component
to
the
page,
and
the
interesting
part
about
this
is
that
it
has
a
method,
that's
being
exposed
called
on
event
selected.
So
let
me
just
show
you
inside
that
web
part.
What
it
does
is
down
here
in
the
rendering
for
it
down
here.
So
in
here's.
C
My
render
method
on
my
event
web
part
down
here
on
the
where
it's
actually
showing
the
list
view
of
all
of
the
different
events
I'm,
simply
saying
when
these
selection
changes
I
want
you
to
bind
that
to
this
method
called
get
selection.
So
if
I
scroll
back
up
to
find
get
selection
right
here,
you
can
see
that
what
this
one
is
gonna
do
get.
Selection
is
I'm
simply
going
to
be
calling
the
handler
of
anybody.
C
That's
bound
to
this
I'm
gonna
call
the
on
event
selected
method,
so
that
was
defined
in
my
properties,
for
my
react
component.
So
if
I
go
back
to
the
web
part
itself,
which
is
right
here,
you
can
see
that
I've
said
that
when
that
method
gets
raised,
so
when
someone
selects
an
event,
call
event
selected.
So
if
I
look
at
a
bit
selective,
what
is
that
going
to
do
that
is
right
up
here.
So
then
select
is
gonna,
get
passed
in
the
event.
C
I'm
gonna
grab
the
event
that
was
selected
and
keep
a
record
of
which
one
that
is
and
then
I'm
going
to
notify
all
the
subscribers
that
two
properties
just
change,
that
I
expose
I'm
going
to
notify
them,
but
the
event
property
and
a
location
property
just
got
changed
now.
What
that's
gonna
do
is
that
you
saw
an
example.
I
did
a
minute
ago,
that's
going
to
notify
the
event
details
web
part
and
it's
going
to
notify
the
map
web
part
that
the
this
property
change,
that
this
property
changed.
So
how
do
we
consume
that
information?
C
Well,
if
I
come
over
here
and
look
at
my
event,
details
web
part,
you
see
this.
One
is
also
just
a
standard
web
part.
There's
nothing
special
with
this
one.
There's
no
special
implementation
for
an
interface
or
anything,
but
if
I
come
down
a
little
bit
farther
inside
the
render
method
and
there's
a
lot
of
stuff
going
on
in
this
render
method.
I'm
just
know
how
this
stuff
that's
important
here:
the
render
method.
What
it's
going
to
do
is
it
doesn't
want.
C
We
don't
want
to
show
data
coming
from
a
consumer
when
things
are
clicked
until
this
thing
has
really
been
configured
so
there's
just
some
configuration
stuff
that
has
to
be
done,
but
what
you
see
here
in
the
configuration
is
I'm
saying
for
dynamic
data
I'm,
saying
register
when
a
property
changes,
let
me
know
based
on
the
source
ID
and
the
source.
Id
is
the
thing
that
is
I'm
consuming
from
and
I
want
to
be
notified
about
the
property
ID.
So
the
way
I
got
both.
B
C
These
options
is
that
when
we
did
an
edit
on
our
web
part,
I
had
the
data
source
and
I
had
the
the
property
that
I
want
to
be
notified
on.
So
those
just
that's
a
standard
web
part
stuff
of
letting
me
pick
which
those
things
I
want
to
be
notified
on.
So
it's
a
little
bit
farther
down
the
code,
but
it's
there's
nothing
special
with
dynamic
data,
there's
just
setting
a
certain
property
on
the
web
part
itself.
C
So
let
me
know
when,
when
the
when
this
provider
says
that
this
method,
that
this
property
has
changed
and
then
call
the
callback
that
I
want
to
do
is
the
render
map.
So
the
render
method
is
gonna
get
called
again
when
I
change
when
I
select
the
specific
event,
that's
gonna
skip
through
all
this.
It's
gonna
skip
through
the
need,
configuration
I'm.
Sorry,
then
it's
gonna
come
down
here.
It's
gonna
say:
oh!
C
If
we
don't
need
any
configuration,
which
means
that
we've
been
configured
we're
all
loaded
everything's
good
to
go,
then
what
I'm
going
to
do
is
I'm
going
to
say:
let's
go
get
the
network
we've
been
essentially
we've
been
called
again
for
when
the
date
has
been
changed.
So
I'm
gonna
go
back
to
my
context,
talk
to
the
SharePoint
framework
and
say
win
on
this
dynamic.
C
Gonna
try
to
get
the
source
that
was
specified
and
if
I
got
the
source,
you
see
right
here.
If
you
get
the
source,
then
I'm
gonna
go
get
a
property
value
called
property,
ID,
okay,
you
know,
assuming
I
get
it
and
I'll
come
back
to
that.
Just
a
second
assuming
I
get
it.
We
come
down
here,
a
little
bit
farther
and
I'm
simply
gonna
bind
that
event
to
my
event,
details
component
and
the
event
details
component,
if
I,
just
scroll
down
through
all
of
this
stuff,
is
just
configuration
stuff.
C
So
if
I
scroll
down
here
at
the
bottom,
it's
simply
going
to
display
the
details
of
the
event
that
was
passed
in.
So
let
me
jump
back
one
more
time
and
I
said
well
right.
Here's
the
line
I
want
to
call
up
for
a
second,
so
I've
got
a
reference
to
a
source
and
I'm
gonna
call
this
get
property
value.
This
get
property
value
event
here
or
this
method.
This
is
being
defined
on
my
source.
My
source,
if
you
recall,
was
my
event
web
part.
C
So
if
I
come
back
over
to
my
that
web
part,
he
should
have
a
method
called
get
property
value,
and
with
that
it's
gonna
say
what
property
do
you
want?
If
you
want
the
event
I
just
give
it
the
selected
event.
If
you
want
the
location,
then
I'm
gonna
figure
out
what
the
location
is
for
this
I'm
gonna
figure
out
based
on
passing
an
object
that
comes
back.
So
if
an
event
was
actually
selected,
go
pass
back,
a
JSON
object
that
has
a
city
property
and
an
address
property.
C
C
What
I
would
recommend
you
do
is
head
over
to
the
SharePoint
Organization
and
github
go
to
the
SP
dev
effects
web
parks.
You
go
into
the
samples
and
there
is
a
react,
react
events,
dynamic
data,
you
scroll
down
here
and
tells
you
how
to
get
it
up
and
running
the
one
thing
that
I'll
just
mentioned
it's
not
here
in
this
list
is
it
does
talk
about
the
fact
that
you
need
to
deploy
it
to
an
app
catalog
in
your
tenant.
This
isn't
going
to
run
local
because
part
of
the
provisioning
process
of
the
component.
C
It
creates
the
list
and
adds
those
three
events
inside
of
it.
So
if
you
try
to
run
this
in
your
local
workbench
you're,
just
gonna
get
a
bunch
of
spending
like
you
can't
show
me
data
and
it
looks
like
things
are
broken.
That's
not
the
case.
It's
just
that
it's
expecting
data
to
be
in
a
list,
and
this
sample
provisions
the
list
for
you
when
you
create
it.
So
every
everything
is
also
talks
about
how
to
set
it
up
and
all
that
so
with
that
I've
been
watching
the
oh
and
one
more
thing.
C
Actually,
when
these
fine,
if
you
go
to
the
CSB
dev
Docs,
and
if
you
go
to
I'm
sorry,
let's
go.
Let
me
jump
back
over
to
the
ducts
if
I
look
at
the
release
notes
really
quick
and
intro
to
dynamic
data.
So
there
is
a
page
here
inside
of
the
table
of
contents.
If
you
look
under
the
SharePoint
framework
documentation
under
guidance
connecting
components,
this
is
gonna
walk
you
through
a
detail.
Example
of
all
the
stuff
that
I'm
talking
about
right
here.
B
B
Week
for
that
one,
and
then
you
can
astoria
fine.
Can
you
hear
me
yeah?
Okay,
so
you
can
actually
steal
the
presentation,
while
you're
doing
that
strands
of
Gotham's
question.
Will
this
work
between
annexation
and
web
part
answer?
Is
yes
except
right
now,
no
slightly
complicated,
and
the
intention
is
that
the
dynamic
data
works
absolutely
between
extensions
and
extensions
and
web
part
and
extension.
It
doesn't
really
matter
what
the
component
is
right
now
there
are
known
API
issues
really
excuse
me
related
in
on
that
one,
but
we
are
in
preview.
B
D
I'm,
a
SharePoint
developer
and
today
we're
going
to
talk
about
unit
tests
with
pimpy
community
samples.
We
originally
created
up
here
and
it's
called
reactor
just
testing
and
it's
a
basically
set
up
for
you
to
start
doing
unit
tests
with
the
chest
testing
framework.
It
is
react
here
and
then
just
is
product
from
Facebook,
so
it
makes
it
a
perfect
fit
to
to
react.
D
But
it's
not
tied
to
react
only
so
you
can
use
the
object,
testing
framework
with
vanilla,
JavaScript,
angular
or
whatever
you
you
like,
but
basically
the
sample,
which
is
something
like
a
starter
kit
for
you.
So
you
can
have
a
look.
What's
there
and
I'll
jump
right
to
the
demo,
and
this
is
the
business
need
here.
D
So
the
business
need
is
a
web
part
where
we
have
a
PNP
ice-cream
shop
and
we
order
ice
cream
here
and
if
I
select
something
like
a
lot
of
just
order
of
the
new
ice
cream
and
I'll
change
the
quantity
here
and
you
can
see
how
the
price
changes.
So
we
try
calculate
something
on
the
back
end
if
I
order
something
it
will
just
show
success.
I
just
ordered
six
from
no
ice
creams
here,
so
this
information
comes
from
SharePoint
lists.
That's
one
SharePoint
list
here
with
the
defendant
ice
cream
flavors.
D
There
is
not
a
list
that
stores
the
orders.
So
there
you
go
one
placed
here
that
stores
the
flavors
and
another
lease
here
to
store.
The
orders
I
already
have
13.
If
I
refresh
I,
will
get
the
14
here.
So
it's
a
working
web
part
a
typical
business
case,
typical
business
requirement,
where
you
have
a
form
you
have
some
business
rules
and
calculations
around
that
form,
and
it's
it's
a
really
good
thing
to
unit
is
that
and
how
this
works.
So
I'll
go
through
the
code,
video
really
quickly,
just
a
normal
web
part
here.
D
These
are
my
test
Suites
here,
and
this
is
the
react
component
on
the
left
very,
very
quickly
going
through
the
code
because
we
don't
have
fun.
The
reactive
component
is
using
the
newest
and
coolest
MPGs
libraries,
so
we're
pulling
information
from
the
lists
on
when
the
component
loads
here
down
below.
Just
we
have
a
title
and
we
render
the
lists
and
updated
with
a
bunch
of
handlers
whenever
you
select
something
from
from
from
the
latest.
Here
it
recalculates
the
price.
D
If
you
change
the
quantity
it
recalculates
that
pull
up
the
price,
when
you
hit
the
Buy
button,
it
just
creates
a
new
item
in
a
SharePoint
list.
Nothing
really
interesting,
while
you're
not
seeing
the
PGA's
libraries,
because
there
is
an
extra
extra
abstraction
layer
here
that
I've,
created
and
I
have
my
own
ice
cream
provider
here,
and
you
can
see
all
my
providers
on
the
Left
where
we
are
actually
having
the
PM
peaches
provider
and
then
we're
injecting
it
here.
D
But
all
the
PM
peaches
call
this
year
we're
using
search
query
to
created,
lists
and
pull
the
flavors,
and
we
are
also
whenever
you
click
on
that
buy
button
you're,
adding
new
item
to
to
another
list
here.
This
is
the
web
part
typical
business
case.
As
I've
said
now.
We
have
the
tests
here,
separated
by
the
different
test
Suites
here,
but
I
will
just
run
the
test.
Show
you
how
it
works,
so
I
will
type
NPM
test
and
the
test
run
will
start
and
see
how
I
run
NPM
test
not
go
test.
D
This
is
important
because
we
need
to
run
NPM
test
instead
of
go.
Please
go
please
real.
Will
fire
the
out-of-the-box
testing
framework,
that's
based
on
mocha
I
guess,
but
we
are
using
a
completely
different
setup
with
the
just
testing
framework.
That's
why
the
command
is
different
here
down
below.
You
will
see
all
my
test,
Suites
executed,
and
we
have
that
nice
green
mark
here
to
say
that
all
my
tests
are
passing
here.
D
We
have
like
in
total
seven
test,
Suites
and
seven
passed,
and
we
have
in
total
2020
many
tests
across
those
seven
Suites
and
they
all
passed
down
below.
We
have
the
coverage,
and
here
is
my
ice
cream
shop
react
component
that
you
are
seeing
here
on
the
left
and
you
can
see
the
coverage.
So
the
coverage
is
a
hundred
percent
coverage
on
statements,
branches
functions
and
lines
down
below.
We
have
tested
our
providers
as
well
and
and
some
good
information
is
here.
D
You
can
see
that
my
coverage
here
is
not
a
hundred
person
and
it
shows
you
exactly
which
ones
of
your
code
are
not
covered
by
any
yummy
tests.
So
it's
a
nice
usable
information
and
you
can
go
there,
see
what's
there
and
try
to
create
a
unit
test
for
for
those
lines
there
now.
Another
interesting
piece
of
information
is
that
coverage
here
per
and,
as
you
can
see,
my
NPM
the
NPM
process
exited
with
error.
D
Although
all
my
tests
passed
still
I
have
an
extra
quality
gates
here,
and
those
extra
quality
gates
failed
the
process,
because
the
coverage
on
the
statesman's
lines
and
functions
should
be
hundred-person
and
those
quality
gates
are
not
made
here.
So
this
is
an
extra
as
I
said:
I've
extra
coverage,
quality
gate
that
I'll
talk
about
later,
how
we
can
configure
it
and
fell
based
on
our
coverage.
D
Ideally,
we
want
a
green
for
your
project.
You
want
to
start
with
a
hundred
percent
coverage
and
keep
it
all
the
time.
That's
why
the
sample
has
a
hundred
percent
coverage
and
he
fails
if
it
drops
below
a
hundred
person.
Now,
let's
go
to
the
pests
and
see
what
is
there
just
and
I'll
go
to
the
first
part
here
at
the
start,
we're
putting
in
just
a
usual
library,
so
it
can
spin
up
the
test.
D
Then
we
have
before
each
and
after
each
hooks,
which
you
can
do
some
setups
before
you
run
the
tests,
and
then
this
is
basically
setup
before
each
test
and
finally,
at
the
end
we
have
the
tests
here.
So
if
I
expand
one
of
the
tests
here,
the
test
starts
with
it,
and
you
have
a
description
here
now
for
all
familiar
with
just
me
or
mocha,
exactly
the
same
syntax,
because
basically
this
is
just
me
under
the
hood
of
the
the
just
testing
framework.
D
So
if
you
use
that
with
any
kind
of
JavaScript
projects,
the
syntax
is
the
same.
But
here
let's
just
have
a
look
at
our
unit
s
here.
So
we
have
an
arrange
statement
here
where
we
will
be
using
a
selector
h1
to
check
if
our
title
is
correct.
If
I
go
back
to
my
web,
part
I
will
be
checking
just
the
wording
for
title
here
and
after
fine
dub
h1
within
my
web
part-
and
here
is
my.
This
is
my
react
component
and
I'll.
D
The
only
missing
piece
here
is
where
it
up
react
component
key
from
and
it
came
from
the
before
each
set
up
so
I'm
mounting
the
reactor
component
on
for
each
group
here,
and
you
can
see
that
I'm
creating
that
element
I'm
using
my
port
here,
a
bunch
of
properties
to
to
to
just
create
the
element
and
then
uncontestable
later
here.
So
this
is
the
certain
part
or
the
expectation
part.
We
will
compare
the
text
we
found
in
the
component
with
the
string,
but
here
you
have
bunch
of
more
helpers.
D
D
Good
now,
let's
try
to
read
this
kit
that
once
again
through
the
visual
studio
code,
because
I've
prepared
three
configurations
here,
three
J's
configurations,
so
you
can
use
the
debugging
capabilities
here
and
just
all
will
run
all
the
tests.
The
same
the
same
I
did
with
NPM
test
there
adjust
what
we'll
watch.
If
you
do
a
change
just
watch
or
what?
If
you
do
change
somewhere
and
we
do,
it
will
execute
all
the
tests
again,
but
we
don't
want
to
do
that
in.
There
is
an
interesting
setup
here
that
says
just
watch.
D
I'll
just
run
that
one,
because
it's
really
important.
If
you
have
plates
thousand
of
thousand
of
unit
tests,
you
want
to
run
only
the
tests
that
you
are
changing
or
your
you're
building
new
tests
and
you
want
to
invest
them
and
Jeff
will
automatically
recognize
that
you
have
changed
only
one
or
two
files
and
if
you
try
to
run
on,
we
lose
this
here.
Let's,
let's,
let's
see
how
it
works.
D
D
D
That
will
increase
your
productivity
and,
as
I've
said,
that
may
be.
The
most
important
thing
for
me
is
executing
only
only
the
code
that
you've
changed
on
the
fly,
so
you
don't
need
to
run
all
the
tests
or
wait,
go
compilation
or
something
else.
At
least
that
might
be
a
time
consuming
now
how
this
is
set
up.
I've
prepared
few
parts
of
unit
tests
here,
but
we
won't
have
time
to
cover
at
least.
D
Cover
those
on
a
separate
meeting
and
go
through
all
these
tests,
but
for
now
I'll
just
say
that
the
tests
are
here
and
you
can
have
a
look.
The
sample
is
uploaded
to
the
PMP
samples
and
you
can
see
how
we
can
use
PI's
most
herbs.
You
can
see
how
you
can
even
step
the
the
newest
PPG's
libraries,
so
maybe
something
that
it's
useful
because
we
use
the
new
click
widgets
keval
in,
and
we
need
to
do
things
like
that.
D
Now
all
the
setup,
how
you
set
up
the
chest-
and
this
will
be
my
last
thing-
on
the
talk-
the
dependencies
here
in
the
packages
adjacent
fall-
you
can
find
only
the
PNP
libraries
or
the
PNP
packages
here
down
below.
You
have
all
the
gist
packages
here,
and
this
is
a
must-have
if
you
want
to
run
tests.
Tests
and
I've
included
those
helper
libraries
to
improve
the
performance,
not
the
performance
but
productivity
as
well,
but
we
don't
have
time
to
cover
them.
So
what
you
need
for
Jess
is
Jess
types,
the
gist
library
itself.
D
He
is
just
so
you
can
work
with
typescript
identity
object
proxy.
So
you
can
fake
that
sass
compilation.
Then
you
have
reacted
to
test
runner
that
is
required
by
jest.
These
are
the
packages
and
then
the
object,
configuration
itself
comes
right
after
the
packages.
We
have
a
chest
section
here
and
you
can
see
that
the
gist
we
will
try
to
use
those
extensions
to
run
the
tests
against,
because
I'm
using
typescript
I,
don't
even
need
the
JavaScript
expansion
here.
But
it's
here
for
your
own
for
your
information,
then
that's
important
the
source
mapping.
D
D
So
if
you
put
a
hundred
percent
coverage
from
branches
functions,
lines
and
salesmen's,
it
will
fail.
If,
if
you
don't,
if
you're,
not
if
you're,
not
within
that
threshold,
this
is
the
whole
setup.
It's
pretty
easy
to
use
and
then
setup
and
then
give
it
a
try.
And
maybe
we
can
do
a
separate
session
for
for
the
different
types
of
tests
here
with
metal.
I.
Think
that's
it
cool.
B
Or
a
battery,
can
you
close
up
on
the
slide?
So
now
we
thank
you,
Belling
really
great
stuff
and
let's
actually
follow
up
on
on
those
additional
demos
and
coverage
on
this
one,
because
the
unit
testing
is
absolutely
a
vital
thing
when
you're
writing
an
enterprise
ready
code.
So
some
people
value
these
kind
of
stuff.
Some
people
just
wanna,
have
cool
looking
stuff.
B
A
But
as
folks
are
dropping
off,
do
you
want
to
mention
our
next
SPF
XJS
meeting
will
be
June
21st,
that's
the
day
before
my
birthday.
If
anybody
wants
to
get
me
anything
so
do
check
us
out.
We
do
the
next
general
SharePoint
dev
special
interest
group
will
be
next
Thursday,
June
14th,
so
join
us
for
that
as
well.
Very
much
I
want
to
thank
everybody
for
coming
to
the
meeting.
Thanks
a
see
thanks
to
velan
for
the
awesome
demos
and
I.
A
Think
you're
gonna
see
more
and
more
on
testing
as
SharePoint
framework
becomes
solidified
as
an
enterprise
solution.
You'll
be
required
as
part
of
many
of
your
projects
to
to
have
some
kind
of
a
solid
testing
platform.
So
thanks
everybody
and
like
I,
said
vase.
I
can
stick
around
for
a
little
bit.
I
can
stick
around
for
a
little
bit
if
folks
have
questions,
but
thanks,
as
always
everybody.
The
community
have
a
great
rest
of
your
week.