►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 1st of March. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
You can download an invite to this bi-weekly call from https://aka.ms/sppnp-js-sig-call.
A
Hello
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group.
It
is
March
1st
2018
I
want
to
welcome
everybody
to
this
week's
call.
My
name
is
Patrick
Rodgers
and
I'm
excited
to
get
into
the
call.
Today,
we've
got
a
lot
of
great
stuff
to
cover
and
some
really
excellent
community
demos
again
from
folks
out
there
so
excited
to
see
those
as
well.
As
always.
We
do
like
to
begin
for
folks
that
might
be
new
to.
A
This
call
are
new
to
watching
the
videos
on
the
YouTube
channel
about
what
this
call
is
and
why
we're
holding
it
and
sort
of
the
topics
we're
gonna
cover.
So
we
are
part
of
the
larger
SharePoint
patterns
and
practices
program
and
we've
started.
These
special
interest
group
calls
oh
gosh
about
a
year
ago
now,
I
want
to
say,
because
we
had
really
grown
beyond
what
we
were
able
to
cover
in
our
single
monthly
call.
But
you
said
too
many
things
going
on
with
the
client-side
development
server-side
development.
A
You
know
the
see
solid
development
things
like
that.
We
just
couldn't
cover
it
all
on
a
single
call,
so
we
broke
out
into
these
special
interest
groups,
and
we
of
course
invites
you
to
attend
as
many
of
these
calls
as
you
have
interest.
So
we
do
on
a
rotating
basis
right
now,
you're
in
the
client-side
development
call
next
Thursday
at
this
time
is
gonna,
be
a
PowerShell
and
see
some
special
interest.
A
Group
call
so
we'll
alternate
back
and
forth
like
that
every
other
week,
and
then
this
one
we're
gonna
cover
open
discussion
on
SharePoint
framework
and
the
client-side
development
patterns
associated
with
SharePoint
framework,
but
also
just
with
SharePoint
client-side
development
in
general
as
well.
Not
all
SharePoint,
client-side
development
happens
inside
SharePoint
framework,
though
of
course
we
do
encourage
that
two
years
ago.
B
A
Wow,
sorry,
just
the
lots
happened
in
two
years.
Yes
must
be
why
I
look
the
way,
I
look,
but
so
anyway,
but
so
all
the
client-side
development
patterns
and
discussions
around
sharepoint
and
then
as
well.
We
talk
about
the
the
javascript
libraries
we've
all
developed
together
as
a
community
to
help
with
these
efforts,
so
they're
designed
very
well
to
work
with
inside
SharePoint
framework,
as
well
as
outside
SharePoint
frameworks.
A
So
if
you're
doing
stuff
in
a
script
editor
web
part
or
something
along
those
lines
and
in
a
SharePoint
hosted
add-in
or
provider
hosted
at
in
and
as
well
and
nodejs,
so
we're
looking
to
cover
all
those
kind
of
environments
and
help
everybody's
development
efforts
out
there.
So
two
links
down
there
at
the
bottom.
Excuse
me:
aka,
MSSP,
P
and
P
community
takes
you
to
the
Microsoft
tech,
community,
SharePoint
development
area.
That's
an
excellent
place
to
ask
general
development
questions
stuff
like
how
do
I.
A
You
know
things
like
that.
You
know
how
would
you
do
this
certain
part
of
a
project
that
might
not
necessarily
be
related
to
any
specific
library
or
be
an
issue
with
any
specific
library?
It's
a
great
place
for
general
development
questions,
and
a
lot
of
folks
in
the
community
are
very
happy
to
jump
in
and
help
out
in
those
places.
The
bottom
link
there
AKMs
SP,
dev
Doc's,
takes
you
to
the
official
documentation
for
all
of
SharePoint
development.
A
So
it's
gonna
be
a
SharePoint
framework
if
you're
looking
to
get
started
with
that
or
you're
already
using.
It
need
a
quick
refresher
on
something,
as
well
as
the
documentation
for
see
some
style
development,
and
even
you
know,
the
classic
WSP
managed
code
style
development,
even
though
we're
not
seeing
quite
as
much
of
that
anymore.
Lots
of
folks
are
still
doing
that.
A
Lots
of
folks
are
still
on
premises,
so
that's
still
happening,
but
all
those
Doc's
are
being
consolidated
into
that
one
location
so
check
out
those
links,
I'm
a
great
place
to
get
started
as
an
in
try
entry
into
the
community.
So
our
agenda
for
this
call.
Today
we
have
an
engineering
update
on
SharePoint
framework
and
then
we've
got
updates
around
the
JavaScript
client,
libraries,
the
office,
365
CLI
and
then
as
well.
A
The
patterns
of
practices,
reusable
client
controls
for
SharePoint
framework
that
have
been
developed
so
we'll
have
updates
on
those
and
then
we've
got
three
community
demos
today,
all
three
of
which
I'm
very
excited
to
see.
The
first
will
be
by
Austin
Breslin,
and
actually
he
had
asked
we're
gonna
change
this
order
around
a
little
bit,
but
we've
got
Austin
Breslin
with
an
offline
first
example
for
react.
So
how
to
mock
up
stuff
and
use
things
in
the
offline
manner.
A
Rodrigo
Silva
is
doing
a
Q&A
chat,
bot
demo
using
cognitive
services,
another
very
cool
thing
to
see,
and
then
Ramon
Roman
Ahmadi
is
doing
a
react
file
upload
example,
and
so
I
haven't
seen
him
on
the
call.
So
if
he
does
join,
please
just
let
me
know
we'll
get
him
promoted
to
presenter,
but
another
very
cool
example
of
doing
a
file
upload
in
react
in
SharePoint
framework,
so
excited
to
see
that
as
well.
Oh,
there
is
awesome,
I'll
get
you
promoted
in
just
a
second
and
then
at
the
end.
A
If
we
have
time
we'll
do
a
QA
and
open
discussion
so
before
we
get
to
the
meat
of
the
call,
I
always
do
like
to
bring
up
opportunities
to
participate,
because
we
get
a
lot
of
questions
about
the
stuff.
You're
doing
looks
really
cool
and
awesome,
but
how
do
I
get
involved?
How
do
I
participate?
How
do
I
be
part
of
what's
happening
and
really
the
way
to
do
that
is
to
just
get
involved.
I
know
that
sounds
a
little
ominous,
but
the
ways
to
do
that
is
on
this
call.
A
We
love
to
have
the
community
demo
so
demo
an
SPF
X
solution
or
something
around
the
JavaScript
client,
libraries
or
something
that
is
none
of
those
things,
but
does
client-side
development
inside
SharePoint
in
some
manner
or
nodejs
development
against
sharepoint
in
some
manner.
We'd
love
to
see
these
community
demos
and
I
think
they're,
one
of
the
most
valuable
parts
of
these
calls.
A
A
If
you
submit
a
new
sample
there
will
usually
ask
you
if
you
want
to
demo
it
on
the
call,
so
really
appreciate
the
folks
who
do
the
demos,
don't
email
me,
please
don't
so
definitely
check
out
those
demos
or,
if
you're
interested
reach
out.
Let
us
know
you
want
a
demo
and
we'll
definitely
get
you
a
place
on
a
call,
so
demoing
I
think
is
one
of
the
more
valuable
things
we
do
here.
Contributing
on
github,
so
contribute
on.
A
Github
can
be
submitting
issues
you
found
or
suggestions
for
enhancements
with
some
of
with
the
libraries
or
any
of
the
you
know
various
other
work.
We
do.
We
always
appreciate
that
feedback
on
github,
I
will
say:
we've
got
a
couple
of
issues
lately
that
have
been
just
fantastic
for
the
amount
of
detail
that
was
included
with
screenshots
and
code
samples,
and
that's
really
helped
us
pinpoint
the
issues
and
understand
what
folks
are
seeing
so
I
wanted
to
say.
Thank
you
for
that
and
the
more
the
more
information
you
can
give
us
with
your
issue.
A
Submission
the
easier
it
is
for
us
to
kind
of
get
that
you
know
resolved
in
some
fashion,
whether
it's
an
enhancement
or
just
understanding.
What's
going
on,
because
often
context
is
tough,
you
know
without
seeing
exactly
the
code
you
might
be
working
on
and
then
as
well,
finally
provide
us
feedback,
whether
even
if
it's
not
through
github,
we
do
appreciate
the
feedback
we
get.
How
we're
doing
on
these
calls,
how
we're
doing
with
the
the
libraries
we
do,
how
the
work
with
sheriff
Lloyd
framework
is
going.
We
really
really
do
take
that
feedback
to
heart.
A
We
can't
always
act
on
every
piece
of
feedback
immediately,
so
please
don't
be
discouraged
by
that.
It's
just
a
priorities
thing
and
a
you
know,
life
thing
and
a
work
thing,
and
all
that
I
think
we
all
understand.
You
know
juggling
balancing
all
those
things,
but
we
do
appreciate
that
feedback.
So
let
us
know
if
you
have
thoughts
ways
we
can
do
things
better,
make
things
better,
make
things
more
clear,
make
things
more
open,
you
know
whatever
it
might
be.
We
do
appreciate
that
feedback.
A
B
You
animate
myself,
there
we
go
so
I'm
going
to
take
over
their
presentation
and
few
slides
from
the
engineering
side.
We
are
kind
of
up.
We
do
have
three
sessions
today.
That's
all
right,
three
demos
today,
so
I'm
not
going
to
do
any
specific
demos,
but
certain
things
again
to
repeat
from
a
sharepoint
engineering
side.
So
two
typical
slides
a
reminder
of
these
things
for
everybody,
a
kms,
s/pdif
Docs
and
the
new
location
for
all
of
the
official
sharepoint
and
development
documentation.
B
If
something
isn't
there
and
it
should
be
there,
please
let
us
know
easiest
way
to
actually
let
us
know
that
something
is
missing
is
tend
to
use
a
kms
SP
dev
issues
list.
So
this
is
really
your
tool
to
report.
First,
any
technical
issues
which
might
be
in
shape
on
development,
SharePoint,
API
SharePoint
framework,
rather
than
let's
say
renting
in
Twitter
or
social
media,
complaining
that
SharePoint
people
don't
get
it
we
well.
It
might
be
that
we
just
missed
the
box.
B
So
please
let
us
know
by
going
a
MSS
bit
of
issues,
but
also,
if
there's
any
gaps
in
our
documentation,
mistakes
in
a
documentation.
This
is
a
great
location,
for,
let
us
know,
that's
so
variable
to
them
schedule
those
in
our
roadmap
and
to
address
the
gaps
themselves.
Now,
please
please,
please,
whatever
you
find,
please
use
this
issue
list
here,
because
we
do
triage
that,
basically
on
day
to
day
basis
and
together
with
engineering.
B
As
an
example,
I
think,
last
time
people
were
asking
around
the
eventing
pates
eventing
mechanism
or
challenges
around
that
one
for
more
on
pages
in
the
context
of
extensions,
and
that
is
now
getting
I
think
that
was
actually
checked
in
yesterday.
So
the
fix
is
coming
quite
soon
within
the
SharePoint
Online.
Now
one
thing
but
I
wanted
to
pinpoint
in
here.
This
is
kind
of
a
almost
a
running
joke,
but
please
please
please,
please
do
not
I
knew
repeat,
do
not
send
emails
to
me.
B
That's
not
the
fastest
way
of
getting
any
support
around
ship
on
development.
Trust
me
there's
no
way
for
me
to
follow
up
on
my
inbox
anymore.
So
that's
one
of
the
reasons
why
we're
trying
to
use
these
consolidated
locations
either
the
Stack
Overflow
or
the
tech
community,
or
the
issue
list
if
it's
actually
a
buck
within
a
SharePoint
or
a
gap
within
our
existing
things.
Now
moving
on
on
other
things,
so
one
thing
what
I've
been
always
updating
here
and
twice
in
all
of
the
community
costs
is
the
growth
of
the
SharePoint
framework
usage.
B
Now
I
probably
missed
some
comments
and
I
am
stream.
I
do
apologize,
I'll
get
back
on
those
after
my
section
now
one
thing
and
what
I
still
kept
in
here
from
a
last
time
as
well,
because
this
just
happened
last
time.
So
in
as
part
of
the
one
point
four
point,
one
release
or
SharePoint
framework,
which
came
out
two
weeks
ago.
B
In
the
future,
as
well
now
a
quick
update
on
the
roadmap,
we
have
quite
a
lot
of
slides
to
go
through
still
not
that
many
changes
in
here
since
the
last
two
weeks.
Maybe
a
small
update
here,
it
seems
to
be
that
hub
sites
and
hub
api's.
We
will
actually
start
to
preview
relatively
soon.
So
last
week
we
had
a
special
interest,
is
called
interest
group
call
for
SharePoint
development.
B
It's
slightly
longer,
so
it's
not
gonna
be
released
at
the
exactly
the
same
time,
but
the
target
is
still
to
go
live
during
this
month
for
both
of
this,
at
least
for
now-
and
there
might
be
still
change
this
on
this
in
practice,
a
lot
of
people
have
been
asking
that
ok
you're
running
out
of
things
on
your
roadmap,
which
is
absolutely
true.
So
the
next
big
announcement
timing
will
be
SBC
18,
so
the
SharePoint
conference
in
Las
Vegas,
where
we
will
then
announce
the
next
set
of
things.
B
What
are
we
actually
right
now,
building
or
what
I
was
starting
to
build
and
and
then
potentially
something
might
be
ready
or
ready
to
release
on
SBC
and
then
the
big
release
timeline
is
actually
they
ignite
in
autumn.
That's
how
it
works
in
in
our
site,
one
more
slide
on
my
site,
just
quickly
summary
of
changes
on
the
SharePoint
frame
website
or
more
on
the
actually
on
the
SharePoint
PMPs
items.
B
Let
me
clarify
the
slightly,
but
we
have
now
extended
our
SharePoint
BMP
community
team
with
three
additional
persons,
so
two
entries
so
entry,
C
and
entry,
K
I
think
both
potentially
are
in
the
score,
and
then
we
call
Swenson
are
part
of
the
SharePoint
MVP
team
and
just
quickly
explaining
what
this
actually
means.
So
we
in
SharePoint,
community
or
SharePoint
in
the
development
we
actually
built
our
community
and
guidance
and
samples
and
all
of
this
stuff
together
with
community
and
one
of
the
things
one
of
the
reality
is.
Is
that
there's
so
many
contributions?
B
And
there
are
so
many
people
active
in
a
key
table
and
also
in
documents
and
all
that
we
actually
can't
keep
up
with
our
engineering
resources,
plus
the
fact
that
no
offense
for
engineering
people,
including
me
as
well
eyewear
from
Richmond
or
beer
from
Microsoft?
We
don't
necessarily
always
understand
the
latest
and
greatest
and
all
stuff
to
date,
things
what
happens
actually
at
the
customer's
life.
So,
therefore,
we
need
people
who
can
who
are
more
up-to-date.
B
What
actually
happens
in
the
customer,
the
customer
facing
development
and
that's
why
we
actually
have
then
a
special
SharePoint
BMP
team,
which
includes
then
internal
Microsoft
people
and
also
external
people,
and
we're
looking
into
extending
this
team
in
the
future
as
well.
So
getting
more
and
more
people
MVPs
included
in
this
team,
which
will
then
help
us
on
this
journey
on
on
making
sure
that
you
have
a
sufficient
amount
of
documents
and
and
sufficient
amount
of
samples
showing
how
to
be
successful
with
SharePoint
development
cool
and
the
one
thing.
B
What
I
forgot
I
already
mentioned,
that
that
I
completely
forgot
it,
but
a
shape
and
framework
turned
one
year
old
year
week
ago,
so
week
ago,
Friday
on
23rd
of
February
7th
Framework
had
a
one-year
anniversary
anniversary,
forty-eight
announcement,
which
is
kind
of
cool
and
so
Patrick
from
a
calculating
at
the
times.
We
have
had
this
actually
call
already
two
years,
which
is
pretty
interesting.
So
time
flies
when
you're
having
fun.
It's.
B
Can
go
back
on
the
channel
nine
recordings
two
years
ago?
Probably
it
would
be
interesting
to
see
what
was
there
but
anyway,
I
think
and
that's
enough
from
my
side,
so
nothing
too
major
on
a
SharePoint
framework
side
from
now
we
are
looking
into
releasing
the
hub
sites
hub
site
api's,
which
will
be
then
available
for
SharePoint
development
and
Krupa
files.
Still
in
this
quarter
and
then
the
next
announcements,
most
likely
will
have
to
wait
until
s
PC
to
forget
anything
additional
Orbiter
but
Patrick.
Please
take
it
away
under
PMP,
J,
stuff.
A
Great
and
I
did
want
to
just
make
sort
of
a
general
comment.
There's
been
a
discussion
going
in
the
in
the
comment
window
around
one
of
the
samples
gonna
get
updated
stuff
like
that
and
honestly
it's
it's
a
time
issue.
We
on
the
core
team
are
already
swamped,
so
it's
it's
very
hard
to
sort
of
with
prioritizing
doing
the
new
work
and
the
community
work.
Circling
back
to
update
samples
agree,
they
should
be
updated,
but
that's
a
great
way
to
contribute
and
it's
a
fairly
easy
way
to
get
started
contributing.
A
So
if
you
have
some
time
or
see
a
sample,
that's
valuable
to
you
and
wish
it
was
updated.
Maybe
pull
that
down!
Do
the
update
push
that
in
we'd
love
to
give
you
the
credit
love
to
thank
you
for
doing
that?
It's
and
it's
very
much
not
that
we
are
ignoring
needing
to
update
those
samples,
but
it
really
is
just
a
time
thing
for
all
of
us:
we're
all
juggling
the
time
schedule
with
with
our
lives
and
with
work
and
all
that
stuff.
A
So
just
keep
that
in
mind
if
you
do
have
a
few
moments
and
want
to
update
a
sample
generally,
it
doesn't
take
too
much.
You
know
to
update
a
single
sample
and
we
very
much
appreciate
it
again
on
our
side
from
the
core
team.
Those
little
bits
of
help
go
a
really
long
way
to
help
the
whole
community.
So
I
just
wanted
to
sort
of
say
that
and
again
we
do
appreciate
everybody
that
has
contributed
and
has
updated
samples,
because
I
know
there's
folks
out
there
doing
that.
So
thank
you
for
that
work.
A
It's
very
much
appreciated,
so
stepping
into
a
quick
update
on
the
client-side
libraries
again,
the
libraries
github.com
slash,
P
and
P
slash
PNP,
a
upcoming
release,
March
2nd,
which
is
actually
if
you're
counting
tomorrow,
but
that
might
actually
be
Monday
depending
I've
got
a
couple
outstanding
issues.
I
think
will
be
nice
to
get
fixed
and
I'm,
not
sure
I'll
have
them
by
tomorrow,
and
we
are
now
as
a
group
as
a
PNP
core
team
for
all
our
projects.
A
Doing
a
change
log
file,
so
changelog
dot
MD
in
the
root
of
the
project,
is
we're
all
doing
that
and
we're
all
we've
all
adopted
a
standard
format
so
for
in
our
PNP
client-side
libraries
example,
you
could
check
out
the
change
log
and
see
what's
gonna,
be
upcoming
for
the
next
release
and
that's
true
now
across
all
the
libraries
so
check
that
out
and
we'll
be
updating
that,
obviously
with
each
release,
but
that'll
be
the
way
to
track.
What's
new,
we
did
want
to
mention
CD
NGS
support
is
still
in
the
works.
A
We're
still
approved
we're
just
in
their
cue.
They
they
have
a
lot
of
stuff
to
get
through
they're.
Obviously,
a
huge
huge
project
Peter
does
an
amazing
work
over
there,
but
so
that
is
not
done
yet,
but
we're
still
tracking
to
have
that
done
and
we're
going
to
talk
about
numbers
on
the
next
slide
a
little
bit,
but
I
felt
it
was
very
much
worth
mentioning
and
saying.
Thank
you
to
all
of
you
in
the
community
that
have
chosen
to
use
the
client-side
libraries.
A
Apparently
two
years
ago,
to
get
is
out
there
for
the
community
and
really
help
folks
get
into
the
client-side
development.
A
little
bit
deeper.
I
wanted
to
mention
the
roadmap
we
are
working,
so
this
will
not
be
for
the
immediately
next
release,
but
maybe
the
release
after
that
it
improved
ad
client.
A
So
some
more
end
to
end
not
just
the
documentation
code
snippets,
but
some
actual
you
know
sample,
share
my
favorite
rib
parts
or
share
port
framework
extensions
or
node
apps.
Something
like
that,
but
some
some
real
sort
of
end
to
end
samples
and
as
well
I
always
want
to
invite
people.
If
you
have
ideas
that
would
be
valuable
to
you,
we'd
love
to
hear
those
we
could
put
those
into
the
roadmap
help
prioritize
them.
A
But
as
basa
mentioned,
we
are
as
much
in
the
field
customer-facing
anymore,
so
we
don't
know
in
the
same
way
we
all
used
to
what
are
the
pressing
problems
we're
trying
to
solve
for
customers
that
you
all
are
trying
to
solve
for
customers.
So
definitely-
and
let
us
know
we
can
help
work
that
stuff
into
the
library
and
if
you
haven't
check
out
the
docs
PMP
github
is
slash.
P
and
P.
A
Get
you
the
docs
for
the
the
new
libraries
it's
a
great
way
to
get
started
with
them
and
really
encourage
folks
to
start
transitioning
as
soon
as
you
get
an
opportunity
that
July
is
going
to
come
pretty
quickly,
and
so
that's
when
SP,
P
and
PJs
will
cease
to
get
updates,
so
look
to
transition
when
you
can
and
then
subdue.
Such
information
always
like
to
share
this
at
the
end
of
the
month.
So
these
numbers
are
missing
either
one
or
two
days,
but
we've
consistently
been
over
a
billion
requests.
A
We
dropped
a
little
bit
in
December,
obviously
the
holiday
season
there,
but
we're
at
1.2
billion
requests
the
last
two
months,
January
February,
and
we
increase
the
number
of
tenants
month-over-month
consistently.
Now
so
again,
that's
a
thank
you
to
all
of
you
out
there
in
the
community
who
are
using
the
library
in
your
projects,
evangelizing
that
and
getting
your
customers
to
have
that
uptake.
So
just
want
to
say
thank
you
again.
A
There
we've
had
sixty
three
hundred
downloads
from
NPM
and
we've
had
7500
readme
views
of
the
readme
file
and
that's
something
we
just
started
tracking
this
month
of
February
and
that's
actually,
second
only
to
the
PowerShell
library
inside
the
patterns
and
practices
ecosystem
so
really
exciting,
again,
just
to
get
usage
and
uptake
and
finally
wanted
to
share
the
map
at
the
bottom,
which
is
something
personally
I'm
super
excited
about.
That's
where
those
views
came
from.
So
it's
kind
of
worldwide
folks
are
finding
the
work.
A
We've
all
done
together,
build
up
and
are
using
that,
and
so
it's
super
exciting
and
just
a
small
plug
since
there's.
Obviously,
a
lot
of
views
from
Europe-
you
can
see
me
say
words
at
the
European
collaboration
summit
coming
up
there
in
May,
so
we'll
have
a
couple
different
sessions,
and
you
can
tell
me
to
my
face
everything:
that's
wrong
with
the
libraries
so
office,
365
CLA
CLI,
some
great
updates
again
this
month.
I
am
a
real
person.
I
might
be
part,
robot
we'll
see,
but
office
365
CLI,
the
next
release.
A
They're
gonna
go
up
to
v1
in
a
matter
of
days,
so
updates
to
the
SharePoint
Docs,
so
managing
site
collection,
app
catalogues,
ALM
api's,
as
well
as
tenant
properties,
so
recently
added
support
for
graph
managing
offices,
five
groups
and
then
working
with
sites,
lists
and
files
and
then
in
so
the
February
numbers
as
compared
to
January.
So
these
are
the
month.
Over
month,
growth
is
36%
in
NPM
downloads,
34
percent,
month-over-month,
Docs
users
and
then
61%
GOx
visits
month
over
month.
A
Growth
so
really
excited
to
see
the
growth
in
the
uptake
of
office,
365
CLI,
another
great
tool
for
everybody
out
there
to
put
in
your
tool
belts
and
then
down
at
the
bottom.
You
can
use
the
tag
office.
365
CLI
on
Twitter
there's
a
git
er
channel
for
the
office,
365
CLI
and
then
as
well.
That
akms
link
will
take
you
to
that
git
er
channel.
So
if
you
haven't
checked
out
the
office,
365
salon.
B
C
That
s
Patrick
said
we're
going
really
hard
towards
you,
one.
We
have
more
and
more
help
from
folks
who
contribute
who
spend
their
time
contributing
commands
or
even
expanding
existing
Doc's,
giving
feedback
and
ideas
for
for
new
commands.
So
this
is
really
really
great
to
see
how
it
grows,
how
many
people
start
using
it
more
and
more
and
more
so
yeah
I
can
only
say
again
really
big,
big
big
thanks
to
you
guys
to
everybody
who
chimes
in
spends
their
time
offers
help
and
yeah.
C
If
you
are
on
Windows,
on
a
Mac
or
or
or
on
Linux,
it
does
not
really
it
does
not
replace
PowerShell,
it's
just
another
way
of
managing
your
tenant.
If
you
prefer
to
UCL
I
use
that
if
you
like
to
use
PowerShell,
you
use
that
right.
So
it's
just
another
tool
that
you
can
use
to
manage
your
tenant
and
with
that
again
big
thanks
to
everybody
who
contributes
and
give
me
a
Patrick.
C
A
So
check
out
the
office,
365
CLI
as
I
and
waldek
have
said
it's
a
very
cool
tool
to
add
to
your
tool
belt.
Moving
on
to
update
on
the
SharePoint
framework,
reusable
components.
So
excuse
me:
we
are
at
1.30
for
the
SharePoint
framework,
property
controls
with
two
new
controls:
they're,
the
property
field,
multi
select
and
a
property
field
number
and
those
you
can
see
examples
of
both
of
those
there.
A
On
the
slide,
we've
got
a
couple
of
enhancements
as
well
in
the
latest
version,
the
property
field
term,
picker
introduced
property
to
specify
to
show
or
hide
the
term
store
name
and
then
as
well
property
where
terms
were
unselected
based
on
ID
of
instead
of
paths,
so
two
great
enhancements
as
well
as
two
new
controls.
There.
B
A
So
now
we
are
ready
for
the
demo,
so
we
have
three
demos
and
we
got
30
minutes
to
get
them
in
so
I'll.
Let
everybody
do
the
math
on
that.
But
Raman,
are
you
ready
to
go
yep
excellent?
Well,
if
you
want
to
take
over
as
presenter
yes
and
so
Raman
has
got
a
react
file
upload
example
that
I
think
is
really
cool.
So
let's
check
that
out.
B
A
D
Take
it
away,
could
you
see
my
screen?
Yes,
sir?
Okay,
all
right,
I'm
really
happy
to
be
among
you
guys
and
today
I'm,
going
to
show
you
how
the
file
uploads
that
part
works.
Let's
just
quick
jump
to
the
demo.
This
is
our
web
part
react
file
output.
There
are
some
pretty
piece
that
you
can
change
here.
D
You
want
to
upload
files
to
a
document
library
or
if
you
want
to
operate
it
as
attachment
to
an
existing
item
in
a
list,
so
you
can
just
change
the
property
and
I.
This
is
the
list
picker
control
that
you
can
just
use.
It
really
easy,
and
this
is
the
are
firefights
that
user
allows
to
upload
to
SharePoint,
and
if
you
want
to
attach
advice
to
an
item,
you
can
just
specify
the
query.
String
parameter,
for
example,
item
id
id
any
other
parameters
that
we
want
to
use.
So,
let's
start
with
documents.
D
Okay-
and
this
is
a
drag
drop
zone
that
you
can
just
drag
your
files
here,
as
you
can
see
files
a
bucket
here,
but
it
is
not
a
reason.
I
created
this
sample
actually
I
created
this,
because
I
need
a
way
to
add
attachments
to
item
to
list
item
because,
as
you
know,
if
you
use
powers
before
Paris,
the
lessons
allow
you
to
add
attachments
to
it
to
a
list
item
currently.
But
if
I
can
move
here
with
this.
D
D
So
in
the
code
we
have
some
properties,
as
you
can
see
here,
as
we
use
some
reusable
controls
for
these
speaker.
It's
just
because
here
property
field
is
speaker
and
also
when
you
want
to
attach
a
file
to
document
library.
Your
this
item,
you
need
to
get
permission
so
here
in
on
any
function.
I
just
create
some
code.
Add
some
code
to
get
the
ID
I
just
cash
from
the
page,
so
we
can
use
it
when
we
want
to
add
a
suffice
to
a
document,
library
or
release
item.
D
So
this
is
a
conflict.
This
is
the
header
we
need
to
a
specific
program.
We
want
to
use
REST
API
to
upload
files,
and
this
is
the
digest
property
that
we
pass
to
this
component,
and
there
are
some
other
functions
that
you
can
use
by
the
way
we
are
using
their
up
drops
on
J's
library
for
uploading
files.
So
there
is
some
out-of-the-box
even
handle
that
we
can
use,
for
example,
in
processing.
D
We
just
changed
the
URL
to
a
REST
API
that
we
to
open
files
up
to
the
factory
document
library-
or
you
know
this
item
and
also
I
used
p.m.
PJs
to
remove
a
file.
So
when
you
click
on
remove
I
use,
PMPA
is
to
remove
it
from
the
deaf
cumin
lightweight
and
after
you
remove
it.
You
can
just
add
some
some
other
comments
here
also-
and
this
is
an
actual
component
that
we
have
here
and
you
can
just
customize
it
whatever
you
want.
There
are
two
CSS
files
here
that
you
can
customize
the
Riu.
B
Cool
and
this
one
is,
is
also
in
the
sample
gallery.
So
let
me
actually
play
a
link
on
that
on
SPF,
FX
webparts
came
in
actually
earlier
this
week
there
was
a
small
delay
on
processing
some
of
the
poor
requests
in
Akita
because
due
to
again
time
related
issues,
but
let
me
actually
get
the
link
that
one,
maybe
it's
in
here
and
then
we
can
move
I,
think
for
a
fika.
So
there's
the
link
on
the
some
oka
sample
gallery
on
having
a
close
look
on
that
one.
A
E
A
E
So
I
know
I've
been
here
before,
but
for
people
who
didn't
attend
so
I'm
just
going
to
introduce
my
to
introduce
myself
quickly,
so
my
name
is
Rodrigo
Silva
I'm,
an
independent
sharepoint,
developer
and
technical
architect
and
I'm
currently
working
in
over
Dublin.
The
warm
fuzzy
Dublin
for
a
company
named
storm
technology,
and
here
are
the
links
for
someone
who
wants
to
follow
me
and
now
I'm
going
to
jump
into
the
presentation.
So
first
things.
First,
if
you
go
to
the
sample,
you
have
some
favorite
prerequisites.
E
You
have
two
useful
links
here.
This
one
is
basically
just
a
video
showing
you
how
to
do
what
I'm
going
to
do
today
and
this
one
is
actually
for
the
cognitive
services,
the
the
Q&A
maker,
which
is
basically
this
page
not
going
to
talk
much
about
the
Q&A
itself,
but
it's
basically
part
of
the
cognitive
services.
This
one
is
free
to
use
API.
Hence
the
reason
why
I
decided
to
do
and
it's
basically
it's
its
main
objective-
is
to
to
transform
those
old,
boring,
FAQ
pages
into
more
dynamic
things
such
as
a
chat
bot.
E
So
basically,
this
receives
as
an
input
either
I
need
any
type
of
file
or
you
can.
You
can
pass
a
URL
and
then
he
processes
it
and
it
then
forms
knowledge
base
and
from
that
moment
on,
you
can
start
used
in
a
so.
If
you
follow
the
link
here,
you
go
to
this
page,
which
is
the
Q&A
maker
itself.
You
would
log
in
with
your
account
and
you
would
create
a
new
service,
so
basically
you
give
it
a
service
name.
You
pass
the
euro
of
the
FAQ
page.
E
You
have
and
I'm
just
not
going
to
do
it
now,
because
I
have
a
service
already
but
yeah.
You
just
passed
the
URL
there.
You
can
upload
the
files
here
as
well
and
when,
when
it's
ready,
just
click
create
in
my
case
I
already
have
two
here
and
for
this,
then,
what
we're
gonna
use
this
one
so
just
going
to
show
the
settings
quickly.
E
So
basically,
after
I
just
press
this-
this
quick
page
here
this
this
is
the
the
Microsoft
one.
So
we
have
FAQ
about
Windows
and
about
office,
and
we
have
few
here
so
I
didn't
pass
any
files
and
this
basically
created
this
knowledge
base.
So,
as
you
can
see,
there's
two
types
of
sources
here:
one
is
the
editorials
or
the
ones
that
we
manually
input
and
the
other
one
is
the
one
that
was
actually
retrieved
from
from
the
URL
I've
specified.
E
So
we
have
all
the
order
pairs
here
or
they're,
all
the
questions
and
answers,
and
after
having
after
being
satisfied
with
with
our
knowledgebase
as
you
can
see,
I
added
this
one
as
well.
Why
is
P
and
P
and
I'll
just
grab
a
quick
introduction
so
after
when
you
satisfied
with
your
knowledge
base,
you
then
have
this
table
where
you
can
set
your
your
book,
so
you
can,
you
can
chat,
you
can
say
hello,
and
this
doesn't
recognize
hello,
but
we
wicked
potentially
passed
that
so
let's
say
so
this
key
okay.
E
E
And
it's
going
to
take
a
minute
and
then
publish,
and
if
before
just
before
we
publish
this
gonna
is
gonna.
Ask
you
to
review
your
changes.
So,
okay,
I'm
happy
with
that
so
I'm
kind
of
published-
and
these
are
the
important,
the
two
important
things
that
we
need
for
this
demo.
So
one
is
the
knowledge
base
ID,
which
is
here
and
the
other
one
is
the
subscription
key.
So
all
sets
we
have
our
knowledge
base.
We
trained
we
happy
with
with
the
results,
and
then
we
grab
these
two
values.
E
Okay,
so
let
me
now
just
jump
into
the
code.
So
I'll
show
the
code
we
detail
a
little
bit
later,
but
for
now,
just
and
and
the
services
I've
created
is
this
table.
So
this
is
basically
because
I
like
to
isolate
my
data
services,
so
here,
as
you
can
see
in
the
in
the
in
the
beginning
of
look
of
this
class
I,
this
is
where
you're
gonna
put
your
subscription
key
and
your
knowledge
base
ID
and
we
good
to
go.
So
let
me
just
I'm
gonna
use,
actually
this
the
the
site
I
used
last
time.
E
So
it's
already
there
as
you
can
see.
So
it's
because
it's
easy,
it's
a
SharePoint
framework
extension.
So
it's
away
there
it's
our
PMP
Q&A
chat
chat,
so
we
can
say
hi
and
hi
I'm,
pretty
sure
recognizes,
and
a
really
cool
thing
is
I,
don't
generally,
if
you
could
see
them,
but
in
here
in
my
knowledge
base,
I
had
so
I
had
what
is
P
and
P,
but
if
I
actually
go
here
and
just
say,
was
PNP.
E
So
it's
going
to
give
me
the
same
answer
because
it's
using
cognitive
services,
so
it's
he
knows
how
to
deal
with
normal
language.
So
basically
it
goes
and
picks
up
the
the
right
answer.
Once
again.
If
he
wasn't
the
right
answer,
you
can
go
and
train
and
that's
it
well,
that's
pretty
pretty
much
it
so
I'm
going
to
show
the
code.
Now
it's
a
very,
very
simple
sample.
So
we
have
basically
I've
created
this
the
service
here
which
I
call
cognitive
services
I.
E
Basically,
my
class
just
has
to
to
chookies
the
knowledge-based
idea.
The
subscription
key
and
then
I
just
have
only
I,
have
one
only
one
method
which
is
get
Q&A
answer
and
basically
receives
the
question.
So
basically
I
create
the
post
URL
using
the
knowledge
base,
ID
and
then
buddy.
This
is
free,
pretty
standard
and
then
I
append
the
subscription
key
to
the
header
and
I'll
make
the
request
and
basically
because
I
wanted
something
more
friendly.
E
E
That
would
wipe
out
the
extension
so
basically
on
in
it
I'm
calling
the
method
render
filter
I'm
instantiating,
the
new
cognitive
services
here,
I'm
passing
these
contacts
because
it's
part
of
its
configuration
and
then
basically
just
appending
this
element
to
to
to
the
Dom
and
the
element
itself
is
pretty
pretty
simple
because
well
I,
like
if
other
people
develop
really
cool
components.
Why?
Why
should
I
reinvent
the
wheel?
So,
basically
less
that's,
really
cool,
there's
a
really
cool
sample
called
widget,
so
I'm,
just
using
that
reaction.
Widget
it
receives
it
receives.
E
B
Is
super
powerful,
but
the
implementation
is
simple,
no
doubt
so
yeah,
that's
great
and
that's
it
for
me.
Vism
excellent,
really,
really
great
demo
and
and
the
link
has
been
already
into
our
Windows
few
times.
We
will
put
it
in
the
video
notes
like
Patrick
mentioned,
but
Patrick
I
can't
help
myself.
You
have
to
host
I
should
not
jump
on
these
things.
A
Another
fantastic
demo,
so
thank
you
for
that.
Rodrigo
I
will
as
we're
switching
the
slides
over
just
say
to
folks,
if
you're,
not
looking
at
AI
and
cognitive
services
and
working
these
kinds
of
things
into
your
projects,
it
really
is
something
that's
gonna
just
grow.
So
looking
at
the
investments
that
Microsoft
as
well
as
many
other
companies
replacing
it
into
AI,
it's
definitely
an
area
to
have
a
look
at.
A
B
F
So
now
that
so
to
begin,
I
have
put
a
breakpoint
here,
and
this
is
before
it
will
make
any
HTTP
requests.
So
we
can
see
this
working
in
slow,
pretty
much.
In
that
case,
I
have
clear,
I'll,
clear,
the
storage
so
that
we
know
that
there
is
no
storage
and
refresh
the
page.
So
there's
nothing
loaded.
Yet
we
should
had
a
breakpoint
and
then
I
am
going
to
turn
it
off.
You
know
disconnect
from
the
internet
on
my
browser
continue,
you
will
have
a
field.
F
If
you
see
to
be
request,
I
will
end
on
a
reconnect
to
the
internet.
It
then
detected
that
I'm
now
back
on
the
internet
and
it's
right
back
at
the
exact
same
breakpoint.
So
it's
gonna
make
a
hasty
TP
request
again
and
there
it
is
success.
So
I'm
gonna
turn
on
cache
so
that
the
next
time
I
load,
the
page.
It
will
give
me
a
three
or
four
on
request,
so
breathe
load.
F
F
Yeah
there's
a
bit
of
a
bug
in
chrome:
where
index
TV?
Doesn't
it's
not
live
like
you
can't
say,
give
the
clothes,
the
actual
console
thought
will
continue
with
this
part
of
the
demo,
so
it
retrieves
it
from
a
flying
undisplaced
to
the
user.
Then
it
had
our
breakpoint
and
then
actually
retrieved
it
from
online.
F
So
let
me
close
it
and
I
can
show
you
how
it
works
in
the
background,
so
indexdb
after
I
closed
the
developer
tools
and
reopened.
It
is
back
up
and
running.
So
there
is
two
two
indexeddb
here:
one
is
called
the
queue,
and
this
is
supposed
to
only
contain
failed
requests
for
post
request
field,
get
request,
updates,
deletes
I,
think
that's
all
of
them,
and
then
the
live
is
what
you
can
do.
F
One
restore
here
from
what
you
don't
want:
the
user
to
read
Lord
and
it's
quite
important
to
decide
to
be
very
decisive
about
it,
because
there
are
limits
on
it
and
I.
Think
Chrome
and
Firefox
only
a
live,
a
50
megabyte
limit,
so
don't
store
everything
only
store
what
the
user
will
require
locally.
So
if
you
got
like
a
an
advert,
you
don't
really
want
to
store
the
advert
offline
users.
Don't
care
if
your
advert,
those
are
doesn't
Lord
but,
as
you
can
see,
this
is
where
it
got
all
the
PMP
Bree
Busch.
F
So
this
is
a
list
of
all
of
the
PMP
Drupal
repos
on
github
and
I
used
github
API,
because
it's
a
nice
cross
origin
and
it's
it's
easy
to
use.
So
that's
it
there
locally,
all
30
of
them
actually.
So
that's
a
lot
and
time
to
the
cord,
I
literally
just
installed
the
jaws
to
do
on
my
machine.
There's
your
Cydia
cord.
F
F
So
what
we're
saying
here
is
we
get
from
local
first,
and
this
is
this-
is
what
the
offline
first
is
about
its
retrieve
it
from
local,
and
even
if
the,
if
the
user
is
not
online,
they
still
will
see
a
result,
and
then
we
like
to
set
state
and
react
when
we
get
the
result.
So
we
set
the
state
when,
after
after
this
data
set
using
the
set
state
callback
option,
we
then
have
a.
F
Component
that
met
with
local
as
what
I
call,
because,
as
you
seen,
my
paused
before
I
had
the
HTTP
request,
the
user
could
already
see
some
results
and
then
later
when
it
makes
the
HTTP
request,
that's
well
actually
do
assets
that
again.
So
normally,
this
is
your
normal
component
that
mounts.
But
this
time
it's
come
to
component
that
mounts
as
you
can
see,
but
one
is
for
offline,
which
is
the
normal
life
cycle
component.
That
means,
and
the
second
one
is
when
the
user
is
on
line.
F
So
even
this
this
gives
the
user
a
perceived
performance
increase.
It's
not
an
actual
performance
increase,
but
react
makes
it
even
faster
because
it
won't
redraw
if
it's
the
exact
same
HTTP
request
with
the
exact
same
results.
So
in
my
scenario
with
it
using
get
hope
this
actually
didn't
cause
every
render
and
then
the
other
way
piece
of
magic
that
I
would
say,
we've
seen
was
actually.
F
Was
in
the
offline
event
sort
of
when
when
I
went
online
and
offline,
so
these
two
event
listeners
are
the
key
to
that
they
just
trigger
when
a
person
is
is
online
or
offline.
There
just
doesn't
work
on,
as
you
can
see
up
here,
it
doesn't
work
on
older
Firefox
browsers.
It
doesn't
work
in
Internet,
Explorer
11.
There
is
a
polyfill
available
for
that
online,
but
they
didn't
put
it
into
the
sample.
F
It's
that's
the
same
to
change.
Sync
changes
to
server,
so
this
will
then
read
the
cue
in
the
application
and
the
indexdb.
It
reads
the
cue
and
if
there
is
anything
in
the
queue
it
will
then
try
to
clear
that
out
because
they
are
failed,
HTTP
requests
and
it
just
lips
through
it,
but
it
does
a
different
lip
depending
on
if
it's
a
post
to
the
server
or
a
get
gets
a
relatively
simple,
it's
the
posts
that
are
different
but
pretty
much
it's
about
perceived
performance,
and
it's
about
it's
about.
Reading
English
stored
data
offline.
F
B
I
think
Austin
I'm
just
conscious
about
the
time,
so
we're
getting
pretty
close
on
the
on
the
hour,
but
super
cool
stuff,
and
there
was
people
super
happy
on
the
demo,
and
that
was
the
whole
point
of
the
submission
and
the
web
part
itself.
That's
blue
and
it's
rendering
white
text.
That's
not
the
whole
point.
B
The
point
is
the
pattern,
and-
and
this
is
except
this
is
really
great
contribution
and
something
what
we
love
to
have
as
part
of
the
sample
Carol
calorie
as
well,
because
it
concentrates
on
showing
a
technique
rather
than
hiding
a
awesome
technique
behind
of
a
complex.
Let's
say
you
ice
and
all
that.
So
these
are
absolutely
welcome,
say
technology,
demos
in
the
in
the
sample,
coloring.
A
Cool
and
it's
it's
definitely
a
pattern
as
well.
Thank
you
for
that
Austin,
a
pattern
as
well.
We've
discussed
in
the
past
on
these
calls
with
the
idea
of
storing
stuff
on
the
the
client-side
at
the
local
storage
or
the
indexdb
there's
different
techniques
to
help
with
performance
as
well
in
a
real
sense
past.
Just
the
UI
sense
is
also
a
possibility.
So
a
really
important
pattern
of
something
to
keep
in
mind
so
I
wanted
to
say
thank
you
to
Raman,
Rodrigo
and
Austin.
A
Great
demos
today
really
appreciate
everybody's
time,
putting
those
together
and
doing
them
on
the
call
for
us.
If
you
would
like
to
do
a
demo
like
I
said
previously
just
get
in
touch.
Our
next
meeting
is
going
to
be
March
15th,
so
that's
not
next
Thursday,
but
the
Thursday
after
and
next
Thursday
will
be
the
general
SharePoint
development
special
interest
group
on
March
8th.
So
thank
you.
Everybody.
Everybody
have
a
great
weekend
and
look
forward
to
talking
soon
bye,
bye,.