►
From YouTube: PnP SPFx and JavaScript SIG Weekly Meeting 20161222
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
to
the
last
JavaScript
and
SharePoint
framework
special
interest
group
for
the
year
2016.
It's
been
a
really
exciting
year
and
we're
going
to
kind
of
talk
about
that
on
today's
call
a
little
bit
as
well
as
some
of
the
normal
updates,
but
welcome
everybody,
and
we
will,
but
so
real
quick
just
to
remind
everybody
at
this
point,
I
think
we're
all
fairly
familiar,
but
sometimes
we
get
some
new
faces.
So
we
do
want
to
kind
of
go
over
this
on
each
call.
A
What
is
the
SharePoint
framework
and
JavaScript
special
interest
group
all
about,
so
we
are
part
of
the
larger
SharePoint
patterns
and
practices
program
which
now
exists
under
SharePoint
engineering
in
the
product
group.
So
the
pnp
stuff
is
getting
very
much
more
tightly
tied
into
engineering
and
being
part
of
that
roadmap
and
part
of
that
actual
planning.
That
goes
on,
as
opposed
to
something
that's
a
little
bit
more
external
and
the
purpose
of
the
special
interest
groups
was
as
the
patterns
and
practices
was
growing.
A
We
saw
a
need
to
condense
or
allow
folks
to
focus
a
little
bit
more
in
certain
areas.
So
we
started
this
one
around
the
idea
of
the
SharePoint
framework
and
the
client-side
development,
and
so
we're
here
to
facilitate
an
open
discussion
around
kind
of
all
of
those
topics,
so
the
shared
my
framework,
client-side
development
in
general
and
then,
of
course,
the
JavaScript
library.
You
know
we're
building
to
help
folks
in
the
client-side
development
space.
So
kind
of
those
are
the
topics
of
the
call
there's
two
great
ways
to
get
involved.
A
You
got
links
down
there
at
the
bottom
to
do
the
microsoft
tech
community
is
that
top
wing,
SP,
p
and
p
dash
community
and
the
bottom
link.
There
is
your:
is
your
starting
page
for
kind
of
everything,
SharePoint,
so
dev
dot
office,
calm,
/,
sharepoint
and
that's
for
the
new
SharePoint
framework,
there's
great
tutorials
and
really
all
the
rest
of
sharepoint
development
as
well.
A
So
if
you're
not
ready
to
jump
into
SharePoint
rain
work
or
you
have
questions
on
the
ad
in
model
or
even
full
trust
code,
you
know
the
sort
of
development
resources
there
as
well,
so
check
that
out
great
starting
place
for
everything.
Sharepoint
development
I
started
going
to
talk
about
today.
As
usual,
our
updates
are
the
latest
on
the
SharePoint
framework
basis,
got
some
cool
stuff
come
in
there
and
for
the
JavaScript
core
component,
we're
going
to
do
a
little
bit
different
today.
A
What
we're
going
to
do
is
we're
going
to
take
a
look
back
at
what
we
did
in
2016
and
then
we're
going
to
talk
a
little
bit
about
where
we're
headed
in
2017,
and
we
don't
have
any
demos
today
we're
going
to
leave
the
end
of
the
call
open
for
discussion.
So
if
folks
have
questions
or
just
kind
of
things,
they
want
to
talk
about,
especially
regarding
the
roadmap
for
2017.
Things
like
that.
Welcome
that-
and
this
might
up
might
end
up
being
a
slightly
shorter
call
than
normal,
but
that'll
be
just
fine.
B
Thank
You
Patrick,
taking
over
the
presentation,
and
there
we
go
so
moving
on
on
things
so,
first
of
all
for
the
Christmas
time.
Typically,
if
you
are,
if
you
have
any
free
time,
people
are
quite
often
interested
on
spending
time
on
learning
and
watching
new
stuff
and
learning
new
stuff.
So
one
thing
what
we
finally
got
sorted
out
early
this
week:
it's
a
simple
location
where
you
can
actually
go
and
filter
down
existing
samples.
What
we
have
on
the
shipment
framework
and
this
location
is
actually
in
the
depth
of
the
comment.
B
So
if
you
go
HTTP,
akms,
SPF
X
as
samples
and
I'm
going
to
show
you
this
one
in
practice
in
a
demo
in
a
second
you're
able
to
actually
filter
down
all
of
the
ship
on
favor
examples
what
we
have
available
within
our
github
repositories
in
the
sharepoint
organization-
and
these
are
essentially
samples
which
are
partly
coming
from
engineering
or
becoming
from
the
community
MVPs.
Another
commune
remembers-
and
this
will
be
all
updated
to
the
release
candidate
level
whenever
we
get
the
release
candidate
out
for
the
SharePoint
framework
right
now.
B
One
of
these
samples
are
there.
Well,
it's
lightly
dependent.
Is
this
what
the
version
of
the
sample
is
actually
using,
but
let's
have
a
look
on
that
one
in
practice
in
a
second
but
a
kls,
akms
SPF
examples
is
the
URL
to
remember
so.
Let
me
share
my
screen
and
show
this
one
in
practice
so
related
on
sharepoint
framework,
so
I'm
going
to
share
my
monitor
tree
because
I
do
you
have
three
different
monitors
on
my
set
up
and
and
Patrick?
You
don't
probably
confirm
whenever
the
screen
sharing
works
on
my
side?
B
B
Inside
of
the
SharePoint
organization,
we
have
the
SPF
FX
web
parts,
and
these
are
essentially
bit
parts
which
week
on
true
together
with
engineering
I'm
from
engineering
as
well,
but
a
lot
of
these
hearts
submit
it
by
the
community
members
now,
there's
quite
a
lot
of
them
yeah
and
quite
often,
if
you're
looking
into
for
a
specific
functionality,
this
might
get
actually
quite
overwhelming.
So
what
you
can
do
is
to
go
to
that
address,
which
was
like
a
ms
SPF
x
samples.
B
It's
super
super
fast
come
on
and
while
awaiting
that
to
happen
just
to
clarify
the
situation
also
in
in
this
side,
so
right
now,
one
of
the
things
what
we
did
for
all
of
the
samples,
what
we
have
within
the
within
the
github
you're
able
to
check.
What's
the
trop
version,
that
sample
has
been
created
for
so
as
an
example,
the
Microsoft
bot
framework
of
a
web
chat
a
client-side
web
or
is
created
currently
with
the
top
number
five,
and
like
mentioned
we're
looking
into
immediate
element
of
release
candidate
goes
out,
which
is
early
January.
B
Next
year
we
were
looking
into
doing
that
actually
before,
unfortunately,
it's
not
sleeping
early
January,
and
but
we
will
upgrade
all
this
accepts.
The
existing
samples
that
are
released
candidate,
0
well
the
first
release
candidate
at
level
well,
obviously
ping.
The
persons
who
created
the
sample
I
say
if
they're
interested
of
doing
that
upgrade
if
they're
not,
then
we
will
do
that
upgrade
for
them
to
the
release
candidate
and
the
URL.
B
Yes,
thank
you,
Thank
You,
Patrick
and
for
some
reason
lifted
off.
Song
is
super
super
super
slow
yeah,
so
it's
actually
still
loading
that
I
should
have
should
have
learned,
should
have
download
it
or
request
that
the
URL
before
come
on,
but
black
nation
on
the
sample
level
on
the
on
the
metadata
or
the
readme
of
the
sample
yeah.
We
do
have
a
lot
of
stuff
on
these
samples.
B
This
is
a
really
good
example
to
react
to
the
basic
and
the
readme
is
themselves
quite
often
have
a
key
funimation,
which
is
explaining
how
the
functionality
works.
This
particular
sample
is
showing
a
lot
of
a
lot
of
different
capabilities
in
react,
so
it's
actually
explaining
and
providing
additional
insights
on
the
readme
file
as
well,
so
explaining
how
things
are
working.
How
we're
doing
the
all
of
this
views?
B
How
we're
taking
stuff
into
use
in
this
case
as
an
example
I'll
be
using
the
display
loading
indicator
with
system
showing
the
loading
to
do's,
and
there
we
go
if
you
can
actually
see
that
in
my
screen
share
or
how
do
we
do
placeholders
and
how
do
we
present
the
placeholders
or
how
do
we
load
different
utilities
and
so
on?
So
one
of
these
samples
have
really
really
great
insights
on
how
things
are
working
huge.
B
B
So
we
will
only
see
the
ship
and
flavor
of
samples
in
here
and
if
I
want,
for
example,
I'm
interested
on
angular
samples,
I
can
filter
them
down
like
by
clicking
the
angularjs
and
after
that
we
should
get
a
filtered
result
of
the
angular
angler
with
pods
in
here
with
awesome
demo
effect.
So
let
me
try
to
do
that.
One
more
time
clicking
react
and
it's
not
actually
filtering
things
properly.
Is
it
no?
It's
not
what's
happening.
It
seems
to
be
that
the
lifted
off
that
go
missing
holiday
mode.
B
So
it's
not
actually
able
to
do
that.
Unfortunately,
but
anyway,
it's
listing
all
of
the
SharePoint
framework
samples
and
you're
able
to
have
a
look
on
what
they
are,
how
they
behave
and
what
are
the
insights
around
the
particular
sample
if
I
open
up
any
of
these,
let's
say
that
I'm
opening
up
as
an
example,
what
would
be
a
cute
one,
knockout
taxonomy
one?
It
is
actually
giving
me
the
insights
in
the
context
of
the
of
the
left
office
at
home
and
from
here
I
can
actually
jump
to
the
github
itself.
B
Now,
in
our
case,
tests
come
back
in
on
this
one
as
well.
There
is
quite
a
lot
of
individual
samples,
this
one
repository,
and
there
is
a
reason
why
we
wanted
wanted
to
do
this.
Somebody
might
say
that
why
didn't
you
actually
have
a
non
repo
with
the
one
sample
which
would
have
resolved
it?
The
SharePoint
organization
should
be
how
we
were
good,
that's
quite
a
big
mess.
B
So
there
would
be
samples
and
individual
repos
and
getting
up-to-date
samples
would
be
really
hard
for
you
and
the
reason
why
we
want
to
use
the
one
repo
for
numerius
samples
is
that
whenever
would
push
updates
to
all
of
these
samples,
you
can
go
and
just
pull
our
latest
version
of
the
of
the
repo
or
update
your
fork.
In
a
kid,
and
after
that,
you
have
all
of
the
needed
updates,
and
so
all
of
the
samples
are
then
in
the
right
level.
B
So
you
don't
have
to
need
to
go
one
by
one
to
individual,
repos
and
update
them,
because
that's
a
really
painful
thing
as
well,
but
which
I
need
to
follow
up
with
with
ethical
office
that
guys,
why
aren't
actually
the
results
getting
filtered
properly
because,
as
an
example,
in
this
case,
I'm
using
the
react,
filter,
prime
still
saying
the
angular
to
prototype
sample
in
here
good?
That
was
a
really
quick
demo
on
that
one.
So
AKA,
ms
s,
BF
x
samples.
That
should
be
something
what
you
remember.
B
It's
only
filters
filter
only
the
first
option,
interesting,
okay
anyway
I'll-
follow
up
with
a
width,
the
width
of
adapted
office.com,
guys,
who
are
responsible
of
that
service,
so
we'll
make
sure
that
that's
actually
fixed
properly
and
I'll
switch
back
on
the
slides
to
do
a
quick
summary
under
where
we
are
with
chevron
framework
and
let's
wait
awhile
and
patrick.
You
can
confirm
whenever
you
see
the
slide
as
well.
I
just
got
it.
I
got.
A
B
Cool
now,
a
few
kind
of
a
pin
points
on
the
status
where
we
are
we
did
really
is
the
trop
stick,
has
dropped
a
six
pack
in
the
delayed
November
and
we'll
be
looking
into
getting
to
release
candidate
out
before
Christmas,
but
unfortunately,
we
were
successful
of
doing
so.
There
were
some
complications
in
the
process
and,
and
it
was
now
delayed
until
early
January-
it's
going
to
happen
pretty
early
in
January,
which
is
fine
all
of
the
documentation
and
labs.
B
So
the
datoria
lyst
in
the
deathbed
of
stuck
on
sloth
sharepoint
have
been
now
updated
on
a
trope
sixth
level.
So
you
start
by
looking
into
or
running
through
the
tutorials
and
the
existing.
There
was
some
issues
which
related
on
the
new
troops,
which
were
not
updated
on
the
on
the
tutorials,
all
of
them
on
no
updated
the
videos
have
not
been
updated
yet
so
the
videos
which
we
have
recorded
for
the
tutorials
will
be
updated
immediately
when
it
gets
a
release
candidate
out
and
after
that,
you
can
actually
see
the
updated
video
recordings.
B
What
else
they
have
pretty
extended.
The
first
least
announced
well
that
was
actually
done
as
part
of
the
top
six
a
release,
so
that
was
late
November.
But
it's
a
good
thing
to
remember
so
any
first
release
tenant
can
actually
use
already
to
deaf
preview
of
chevron.
Favorite
bonds
and
the
ship
on
framework
of
webparts
do
work
with
the
modern
sites
and
the
classics
and
as
well
release
candidate.
Like
mentioned
the
coming
early
january,
we're
looking
into
updating
the
samples
we
are
looking
into.
B
Killing
started
with
SharePoint
framework
training
package
is
in
the
works.
That's
not
actually
English,
that's
Finglas
and
put
it.
What
it
means
is
that
we're
working
on
a
training
packets,
which
is
called
getting
started
with
SharePoint
framework,
and
we
keep
on
updating
that,
and
this
is
something
what
we
are
getting
out.
B
I
say
sorry,
SI,
videos,
presentations,
laps
and
all
that
so
you're
able
to
actually
go
to
the
kids
hump
and
pull
the
whole
thing
down
and
the
videos
will
be
most
likely
shirt
from
the
youtube
channel
and
there
will
be
actually
a
lot
of
material
with
that
one.
I'm
going
to
show
you
the
all
of
the
individual
things
in
the
following
slide,
but
it's
in
the
works
and
we
are
planning
to
get
a
first
version
out
of
that
training.
B
Packets,
early
January,
so
hopefully
pretty
much
quite
fast
after
the
release
candidate
is
is
out
as
well,
and
then
we
keep
on
updating
that
whenever
we
go
to
GA
and
there
are
more
samples
on
the
ship
on
github
organization.
So
we
actually
did
have
a
quick
look
on
that
one
in
in
my
screen
sharing
session.
But
it's
to
get
up.
That
comes
the
ship
once
last
SPD
FFX
webparts
and
more
samples.
If
you're
interested
on
contributing
your
samples
to
some
potent
welcome.
B
And
then
you
get
credited
in
our
monthly
releases
and
multi
communications
on
the
work.
What
you're
doing
and-
and
there
are
more
articles
in
q4,
the
gifted
of
the
consulship
on
so
we
have
no
3
articles
currently
in
the
voice
and
technical
review,
and
those
should
be
coming
out
relatively
fast
as
well.
This
additional
article
somewhere
are
more
around
hey.
How
do
I
reference
an
external
javascript
libraries?
How
do
I
use
an
external
CSS
within
my
web
parts?
How
do
I
do
stuff
efficiently
and
so
on?
B
There's
a
question
from
cage:
are
you
open
for
communities
I'm
hitting
the
SPF
example?
What
plants
did
include
it
to
the
sample?
Sweeper?
Absolutely,
that's
the
whole
idea
these
existing
samples,
but
we
have
within
the
that
repository
of
maturity
of
them
are
actually
coming
from
the
community.
There's
only
few
web
parts
which
have
been
created
by
SharePoint
engineering
as
a
reference,
implementation
and
obvious.
We
want
to
kind
of
show
different
aspects.
B
So
if
you're,
whatever
contribution
or
a
web
part,
isn't
actually
showing
anything
new
and
you
can
absolutely
keep
it
in
your
own
github
profile
and
as
a
known
kit
hub
repository.
But
if
you
see
that
you
have
something
what
you
can
actually
act
on
top
of
the
existing
samples
absolutely
welcome
to
get
additional
samples
in,
and
we
would
highly
appreciate
that,
because
that's
highly
helpful
for
anybody
else
in
there
in
the
in
it
as
well.
B
B
And
the
getting
started
with
SharePoint
framework,
so
the
killing
started
with
SharePoint
framework
training
package
no
I've
mentioned
scheduled
to
roughly
on
the
mid
January.
It
will
go
out.
It
will
have
eight
modules.
Those
eight
modules
are
split
to
a
smaller
sections,
so
one
individual
module
is
not
really
a
one
and
a
half
hours,
video
and
a
training
session.
B
We
wanted
to
split
that
in
a
more
reusable,
smaller
sections,
so
the
sections
are
kind
of
a
sub
sections
of
a
module,
but
those
are
those
all
of
these
sections
have
an
individual
presentation,
video
and
labs
and
all
of
them.
We
do
have
presentations,
demos,
labs
and
recorded
videos
coming
up
for
all
of
this,
and
if
this
will
be
shared
in
a
key
tub
for
anybody.
B
So
if
you
are
looking
in
the
training
material,
you
want
to
redeliver
this
material
for
your
internal
customers
or
your
external
customer
or
if
you're,
an
mct,
meaning
trade,
a
trainer
company.
You
can
just
pull
the
training
packets
down
choose
which
of
the
pieces
you
want
to
actually
use
and
then
re
deliver
the
training
as
much
as
possible.
B
Well,
they
will
be
probably
the
most
typical
myself
copyright
thing,
but
we
don't
actually
care
if
you're
going
to
take
individual
slides
from
these
decks
and
reuse
them
anywhere
like
we
don't
care
if
you
use
that
for
the
for
the
presentations,
but
we
share
from
the
DMV
side
as
well
and
as
you
can
see,
those
are
the
individual
sections.
What
we
have
so
there's
like
40
individual
presentations,
which
are
coming
up.
B
B
I
just
wanted
to
make
sure
that
everybody
knows
that
we're
working
on
this
one
and
that
it
then
it
is
also
coming
out
relatively
soon
and
the
reason
why
we
haven't
released
this
one
yet
is
simply
because
we're
not
yet
in
a
release,
candidate
level
or
energy
a
level.
So
there
will
be
some
prey,
can
change
this
when
we
were
jumping
from
a
drop
sticks
to
the
release
candidate
and
the
the
less
material
which
we
have
released
the
easier
it
will
be
to
us
to
update
that.
B
But
when
we
go
to
the
release
candidate,
we're
looking
into
minimizing
off
the
breaking
changes
in
the
future,
going
crack
going
closer
to
the
GAA
and
getting
the
the
ship
on
framework.
Finally
out,
it's
going
to
happen
pretty
soon,
which
is
super
cool
cool
yeah.
That's
pretty
much!
The
quick
update
from
a
ship
on
frame
website,
quick
and
quick
I,
still
use
20
minutes,
I,
always
just
20
minutes
all
most
of
the
presentations
to
Patrick
jumping
to.
C
A
Thanks
face
a
great
updates,
I
think
really
exciting
for
the
community
to
see
what's
coming,
looking
forward
to
early
January
and
getting
that
release
candidate
0
out
there.
So
now
we
got
a
quick
end
of
your
update
summary
on
the
JavaScript
core
component.
As
always,
we'll
start
off
by
saying,
thank
you
to
everybody.
That's
contributed
you're,
going
to
hear
me
over
the
next
few
minutes.
Talk
about
community
a
lot,
so
it
really
looking
at
40
people
on
this
call
today
and
seeing
all
the
people
that
have
contributed
over
the
year
is
fantastic.
A
So
thank
you
to
everybody.
You
all
have
have
made
this
work
possible
so
and
I
think
it's
a
really
big
deal
that
inside
a
year
we
kind
of
stood
up
and
gotten
this
many
folks
to
be
interested
in
participate.
Real
quick
do
want
to
mention
opportunities
to
participate
in
this
special
interest
group
demo,
a
web
part
if
you
develop
a
SharePoint
framework
web
part
and
want
to
show
it
off
on
this
call.
A
So,
if
you're
working
on
something
cool
get
in
touch
with
myself
or
visa
and
we'd
love
to
get
you
lined
up
for
to
demo
that
on
one
of
these
weekly
or
bi-weekly
calls
also,
if
you
happen
to
be
using
the
core
library
in
a
project
that
doesn't
happen
to
be
a
SharePoint
framework
web
part,
certainly
welcome
demo
around
that
as
well.
I've
had
a
couple
cool
ones.
A
Let
us
hear
that
feedback
so
really
going
to
be
working
to
drive
community
participation
next
year.
That's
going
to
be
a
big
focus
for
me,
so
hopefully
we
can
get
everybody.
They
would
like
to
involve
a
little
bit
more.
So
looking
back
on
the
year,
where
have
we
been?
If
you,
if
you
forget,
we
started
this
entire
special
interest
group
effort
back
in
February
of
this
year,
so
we
started
from
zero
from
nobody,
even
knowing
we
were
doing
this
to
now.
41
we
get
people
continue
to
join
the
call
started
from
zero.
A
We've
grown,
both
a
library
and
a
community
in
that
time.
So
I
want
to
again
thank
everybody
for
being
a
part
of
that
journey.
Throughout
that
time
we
had
163
pull
requests
and
113
issues,
so
that's
fantastic,
so
that
represents
great
work
both
from
the
community
and
giving
back
through
the
pull
request
and
giving
back
through
reporting
issues
they
might
find
with
the
library
or
ideas
for
enhancements
and
hopefully
that
great
feedback
you
guys
have
all
seen.
A
It's
been
a
great
journey,
I
know
for
myself
and
it's
interesting
to
have
been
the
first
special
interest
group
and
then
for
it
to
have
worked
out
as
well
as
it
has
is
always
a
nice
treat
and
the
other
kind
of
side
effect
is
we
helped
SharePoint
developers
begin
to
transition
the
SharePoint
framework
web
dev
model
without
even
telling
you
guys.
Why
and
a
lot
of
people
went
on
that
journey
with
us,
which
is
fantastic
and
I
know.
I
can
speak
for
myself
and
hopefully
for
a
lot
of
the
rest
of
you.
A
I
know:
I
learned
a
lot
in
this
last
year,
both
about
sort
of
open
source
development
in
general
as
well.
As
you
know,
all
various
technologies
were
using
and
again
two
links
down
at
the
bottom
there
for
getting
involved
in
the
community
and
then
the
j
s
core
library
is
on
git
er
as
a
great
place.
If
you
have
quick
questions
to
jump
in
and
get
involved
as
well,
we
try
and
be
as
responsive
as
we
can
to
all
these
forums
so
do
get
involved.
Do
let
us
hear
your
voice?
A
Do
let
us
you
know,
hear
your
ideas,
your
thoughts,
your
feedback.
Let's
keep
that
going
so
I
didn't
want
to
show
you
guys
some
numbers
for
the
the
last
year,
and
these
are
we
talked
about
this
I
guess.
We'd
probably
first
talked
about
it.
In
August
we
introduced
tracking
we've
been
doing
tracking
in
the
Java
in
the
sorry
in
the
sea,
psalm
core
component
now
or
a
number
of
months
and
basic
usually
talks
about
those
numbers
in
the
monthly
calls
for
the
sea,
psalm
library.
A
So
I
wanted
to
bring
up
the
same
numbers
for
us
for
the
javascript
call
and
talk
about
what
those
numbers
look
like
for
our
library,
all
of
them,
I
think,
are
really
exciting
and
really
positive
in
the
sense
that
we're
seeing
growth
sort
of
across
all
these
metrics.
Now
we're
not
quite
at
the
billion
requests
a
month
that
the
sea
psalm
core
component
is
getting
but
we're
working
on
it
and
we're
making
great
progress
and
I
think
that's
really
exciting
to
see
so.
A
So
we're
not
looking
at
specific
versions
were
just
as
anybody
using
any
version
of
the
the
JavaScript
core
component
library,
so
we
started
in
August
with
one
which,
if
you
go,
do
some
research
was
me
testing
that
out
and
then
we
jumped
up
to
84
138
and
we
ended
up
it's
in
December
and
we
saw
have
a
week
in
december,
but
214
tenants
are
now
using
in
some
capacity
the
javascript
core
library,
which
I
think
is
really
exciting
to
see.
Yes,
that's
incredible:
growth
from
August
September.
It's
it's
something!
A
A
And
then
looking
at
the
next
graph,
if
you
move
to
the
right
is
the
unique
total
requests
per
month,
and
so
that's
just
raw
requests
per
month
and
so
we're
over
three
million
now
so
we're
going
kind
of
1
million,
two
million
three
million,
hopefully
in
January,
we'll
get
to
a
billion.
So
that
would
be
another
great
jump
but
in
all
seriousness,
really
impressive
growth
for
something
that
is
really
I,
think
keyed
much
more
towards
the
SharePoint
framework
and
much
more
towards
the
client-side
development.
A
So
a
lot
of
folks,
it
might
not
be
part
of
their
daily
development
life.
Yet
we're
still
seeing
great
uptake
and
that's
a
really
attributable
with
a
great
work
that
all
of
you
in
the
community
have
been
doing
as
well
to
help
us
on
this
journey
and
we
wouldn't
be
growing
as
well
without
the
feedback,
and
so
the
big
graph
in
the
bottom
is
kind
of
a
combination
of
those
twos.
A
B
I
have
to
do
a
quick
comment
on
that,
one.
So
in
the
November
for
the
PMP
PowerShell
and
the
PMP
chasin
court,
the
c-sharp
core
we
were
really
close,
hitting
1
billion
is
that
it
be
request.
We
were
not
quite
sure,
so
we
were
super
tempted
to
actually
have
a
a
scheduled
web
job
which
would
be
doing
stuff
in
the
loop.
We
didn't
do
that
and
we
still
passed
1
billion
HTTP
requests
for
the
cheese
harp
components,
so
that
was
super
cool,
but
rising.
A
But
so
really
really
impressive
numbers
so
and
I
do
want
to
thank
Bert,
actually
put
the
power
bi
dashboard
together.
That
I
got
all
this
from
so
really
fantastic
work
from
Bert.
So
thanks
to
him
for
that,
and
then
one
thing
I
think
is
really
cool
about
the
JavaScript
core
library
is.
If
you
look
at
the
request,
count
that
list
over
on
the
right
of
this
slide.
A
B
Know
just
that
quick
note
on
this
one,
because
I
think
people
in
a
call
or
watching
the
video
might
be
like
hey.
How
would
you
know
this
information
which
at
a
a
fair
question
so-
and
let
me
quickly
explain
how
to
do
this
so
whenever
you're
using
the
PM
pjs
core
and
they
were
using
the
client
tag
property
as
well:
hey
hitter
in
the
HTTP
request.
So
whenever
you
are
posting
anything
against,
you
haven't
online
we're
actually
adding
a
small
hitter
using
the
client
tag
hitter,
which
is
then
getting
stamped
or
getting
included
in
this.
B
Did
they
pay
requests
because
we
are
actually
sharepoint
online?
So
we
are
the
shipment
engineering
and
in
the
SharePoint
Online
we
do
actually
track
a
lot
of.
We
do
have
really
strict
metrics
and
tracking
in
the
sharepoint
online.
On
the
usage,
we
are
obviously
tracking
those
individual
HTTP
requests
on
the
other
side,
and
then
what
we
built
as
part
of
our
analytics
in
the
pnp
is
that
we
essentially
go
through
this
massive
and,
let's
say,
data
warehouse
system
and
we
crawl
all
of
those.
B
It's
ddb
requests
where
that
particular
hitter
has
been
actually
stamped
and
from
that
information
we're
able
to
then
troll.
Essentially
the
conclusions
out
of
this
many
tenants.
These
are
the
countries
or
these
are
the
countries
where
the
tenants
have
been
registered.
We
don't
actually
know
where
the
traffic
is
coming
as
such,
but
it
has
been
hitting
a
tenant
where
the
tenant
has
been
registered
to
a
certain
country.
As
an
example.
A
Yep,
that's
great,
and
we
do
talk
about
that.
A
lot
more
in
depth
of
I
forget
which
recording
it
is,
but
one
thing
I
want
to
stress
along
with
what
basis
said
is
we?
This
is
all
aggregate
numbers
we
get.
We
don't
see
any
details
about
what
the
requests
were
or
who
is
making
the
request.
I
mean
we
know
the
tenant,
but
we
don't
know
user
data.
We
don't
know
names,
we
don't
know
any
of
your
data.
A
B
A
Yep
so
transitioning
a
little
bit
from
sort
of
our
growth
in
this
last
year.
To
where
are
we
going
to
be
going
in
2017?
So
20
is
going
to
come
out
in
early
2017.
That's
going
to
be
tied
closely
to
the
release
of
the
release,
candidates
for
SharePoint
framework,
so
I'm
waiting
on
the
release
candidates
to
double-check
that
some
things
with
the
sort
of
the
builds
and
the
type
and
what
not
are
fixed.
A
But
now,
if
you
look
at
the
dev
branch
of
our
library,
that
branch
is
now
at
two
datos,
so
you
can
check
out
the
dev
branch
and
play
with
that
and
give
feedback,
and
things
like
that
and
I
have
not
yet
written
any
of
the
blog
posts
or
anything
describing
those
changes,
but
did
want
to
get
that
out
there
for
folks
that
might
be
curious
over
the
holidays
and
have
some
time
and
want
to
play
with
that.
You'll
need
to
update
your
local
dev
environment.
A
A
little
bit
you
need
to
update
to
the
node
69
got
whatever
the
current
thing
is
for
the
long
term
support
version
that
has
a
lot
of
the
es6
features
in
it
and
you'll
need
to
delete
and
recreate
your
node
modules.
Folder
is
kind
of
the
easiest
way,
so
just
delete
node
modules
and
do
an
NPM
install
once
you
pull
down
the
latest
project,
but
so
the
two
Otto
is
coming
check
it
out
on
the
dev
branch,
welcome
early
feedback
on
that,
but
understand
it's
still
a
work
in
progress.
A
So
we're
not
a
hundred
percent
done,
but
do
take
a
look
and
if
you
have
ideas
or
feedback.
Definitely
let
us
know
we're
gonna
focus
on
in
the
next
year
on
a
little
bit
tighter
integration
with
SharePoint
framework,
and
so
what
does
that
mean?
So,
as
SharePoint
framework
is
released,
it
becomes
GA
and
folks
really
start
using
that
in
their
day-to-day
development
life
for
enterprise
production
code,
my
expectation
would
be
we're
going
to
hear
a
lot
of
cool
feedback
around
man.
A
It'd
be
great
if
X
was
easier
or
why
was
easier
or
why
can't
I
have
something
that
helps
me.
Doozy
and
that's
what
we
want
to
start
building
into
the
core
library,
so
just
in
the
way
that
the
sea
salt
library
grew
finding
you
know
making
it
easier
for
folks
to
do
sort
of
common
tasks.
Add
lists
things
like
that,
as
the
uptake
grows,
I
figure,
we'll
get
more
feedback
and
as
folks
to
use
the
SharePoint
framework,
more
will
aim
to
make
our
library
more
helpful
when
working
with
the
SharePoint
framework.
A
So
that's
one
goal.
Another
goal
is
focusing
on
driving
samples,
documentation
and
enhancements.
So
I
think
at
this
point
we've
got
a
fairly
mature
library
in
the
sense
that
I
think
we've
got
a
lot
of
the
rest
api
covered,
though
bring
it
in.
Let's.
A
Gonna
mute,
Frank,
real,
quick,
so
focusing
on
those
samples
documents
and
enhancements
and
then
driving
the
community
involvement,
a
contribution
so
like
I
mentioned
earlier,
we've
had
great
interest
from
the
community.
Great
participation
for
the
community
and
I
want
to
see
that
grow
even
more
in
the
next
year,
so
hoping
to
get
more
folks,
demoing
stuff
on
these
calls.
So
once
again,
SharePoint
framework
goes
GA,
I
figure
more
folks
will
be
using
it.
A
So
an
opportunity
to
see
what
more
folks
out
the
community
are
doing
so
I
think
that's
going
to
be
really
exciting
and
then
hoping
to
bring
more
people
into
contributing
to
the
library
and
then
we're
going
to
continue
to
drive
our
priorities
based
on
feedback
from
folks
in
the
community.
So,
like
I,
said
earlier,
if
you're
using
SharePoint
framework
and
there's
some
task
you're
doing
over
and
over
again,
that
you
wish
could
be
a
little
easier
or
a
little
more
automated.
A
That's
the
kind
of
thing
we'd
like
to
hear
and
we'd
like
to
see
what
we
can
do
to
help
so
keep
giving
us
that
great
feedback
and
will
continue
to
be
responsive
to
that
feedback
and
seeing
how
things
progress
with
the
library
and
finally
I
did
want
to
mention
for
those
of
you
that
were
on
last
week's
call.
I
talked
about
how
we
took
provisioning
out
of
the
core
or
JavaScript
library
for
2
dot
0.
So
we
have
now
created,
but
it
is
empty.
A
But
it's
going
to
be
two
separate
libraries
which
I
think
makes
a
lot
of
sense
in
terms
of
development
strategy
as
well
as
prioritization,
and,
as
I
mentioned
before,
that's
a
place
are
we
in
the
core
team
are
really
looking
to
the
community
that
if
there's
genuine
interest
out
there
and
sort
of
driving
a
provisioning
engine,
you
can
run
in
node
we'd
love
to
be
supportive,
but
it's
not
something
we
currently
have
the
folks.
You
know
to
dedicate
to
that.
A
It's
just
a
resourcing
challenge
since
for
a
lot
of
us,
we
do
this
in
our
go-to
mounts
to
our
free
time.
So,
looking
for
folks
in
the
community,
if
you're
really
interested
in
provisioning
or
that's
a
use
case,
you
see
a
lot
of
use
for,
would
love
to
have
you
join
in
and
work
on
the
provisioning,
which
is
something
we're
very
supportive
of,
but
that's
going
to
really
be
driven
by
a
community
effort.
A
So
moving
forward,
like
I
said
we
don't
have
any
demos
in
this
call
other
than
the
what
visa
showed
us
earlier.
So
I'm
gonna
open
the
floor
up
to
an
open
discussion
around
what
we've
got
in
terms
of
coming
up
the
next
year.
If
you
have
questions,
ideas
would
love
to
hear
them.
You
can
come
off
mute
yeah,
you
can
type
in
the
IM
window.
A
I
am
not
sure
I
wasn't
watching
on
a
scroll
up
a
little
bit
and
see
if
there
are
any
questions
for
me
directed
at
me,
but
so
I'll
just
kind
of
open
the
floor
so
see
if
anybody's
got
anything
I.
C
B
C
C
B
Yeah,
that's
absolutely
understandable,
so
many
of
those
actually
that
many
of
the
implementations
are
at
part
of
the
the
office,
you
I've
a
quick
react
components
so
from
a
functionality
perspective,
they
are
actually
available
and
I
think,
but
maybe
not
as
advanced
or
not
as
mature
as
they
are
exposed
within
the
form
such
as
such,
but
we're
looking
into
getting
a
lot
of
this
stuff.
The
modern
experience
is
open,
sourced
or
source
open
in
a
github
as
well
and
those
that's
a
really
good
input
around
the
components
and
like
to
like
to
individual
field
editor's.
B
So
it
would
be
great
to
be
able
to
use
them
within
your
custom
implantation,
but
the
office,
you
I
fabric
components,
I'm
just
looking
into
link
for
that.
These
are
so
everything
what
we
built
within
the
modern
experience
is
are
built
using
these
things
and
we
do
have
a
date
picker
as
an
example
in
the
fabric
component.
So
you're
able
to
actually
do
then
built
your
own
UI
sand
relatively
easily
and
gifted
of
Stockholm
is
super
super
slow
today,
and
so
let
me
get
that
link
into
iron
window.
B
C
B
Absolutely
and
no
doubts
we're
looking
into
doing
that
right
now.
The
key
objective
for
us
is
the
is
to
get
stuff
released
immediately.
When
we
get
more
stuff
on
the
ga,
then
we
will
start
looking
into
open
sourcing
the
individual
components,
individual
things
elements
on
the
on
the
SP
FX,
like
the
yeoman
templates,
are
going
to
be
open
sourced
at
some
point,
so
the
people
are
able
to
at
their
own
stuff
from
them
as
well
and
when
and
how
fast
that
has
not.
C
B
Wouldn't
actually,
no
that's
I
would
actually
have
to
go
and
look
at
on
the
source
code
of
the
UF
Eric
react
components
so
what
we
actually
have
currently
available
and
that's
evolving
very
fast
as
well.
So
if
we,
if
you
have
a
look
on
the
key
top
of
the
officer,
I
fabric
react
and
there
are
daily
edits
and
and
change
this
all
the
time,
but
I
wouldn't
know
for
I,
don't
know
how
to
I
cannot
answer
that
question
directly.
Unfortunately,.
A
And
then
back
to
the
ad
the
API
to
check
if
his
user
isn't
a
group,
that's
on
the
user
voice,
that's
I,
don't
think
either
myself
or
vase.
It
would
have
any
exact
more
to
share
on
that,
but
that's
the
right
forum
for
it.
So
hopefully
folks
will
see
that
more
votes,
more
votes,
more.
B
A
A
Api
is
always
getting
enhanced,
so
I
mean
I.
Think
part
of
the
issue
is
very
expensive
operation
to
start
traversing
security
groups,
which
might
be
limiting
that.
That's
just
a
guess
on.
My
point
are
on
my
part,
but
yeah
more
votes,
but
that
question
is
in
the
right
place
and
the
right
folks
do
look
at
the
user
voice.
Pardon
me
so
that's
a
great
place
for
feedback
and
requests
like
that.
I
want
to
thank
everybody.
Our
next
meeting
is
January.
Fifth
of
2017
is
hard
to
believe.
A
It's
already
been
a
year
again,
really
appreciate
all
of
you
being
part
of
the
journey
and
look
forward
to
continuing
it
next
year.
Thank
you.
Thank
you.
Thank
you.
Everybody
have
a
Merry
Christmas,
a
Happy
Holidays
whatever
that
means
to
you
and
look
forward
to
talking
to
you
in
the
next
year.
Thanks
everybody.