►
From YouTube: PnP SPFx Summer Camp Call #1 - 3rd of July
Description
This is a recording of the SharePoint Framework and JavaScript Summer Camp Call #1 from 3rd of July. These calls are hosted by Andrew Connell (Voitanos) during July 2019 as the Microsoft community calls are on a summer break.
Call contains typical update cross SPFx, PnPjs, Yeoman generators etc.
A
A
A
A
A
A
A
A
A
A
A
You
click
way
too
loud.
That
might
be
somebody
saying
they
can
hear
me
cool.
So
it's
not
like
people
can
hear
me.
You
can
hear
me
and
see
my
screen
awesome.
Thank
you
very
much.
All
right.
We
got
about
two
minutes
left
to
go
before
we
get
this
started
and,
while
we'll
be
back
in
just
a
minute,
so
we're
going
to
give
it
another
minute
or
two
here
before
we
get
started.
A
A
A
So
this
first
of
all,
thanks
for
showing
up
everyone
should
be
able
to
see
my
screen.
You
should
be
able
to
hear
me.
There
is
a
way
that
you
can
actually
raise
your
hand
in
the
chat
I
can
see.
People
are
actually
telling
me
that
they're
that
they
can
see
in
here.
So
that's
good,
so
everything's
going
this.
Let
me
go
ahead
and
first
explain:
you
know
what
we're
doing
here.
A
I'll
go
through
in
just
a
minute,
and
I
also
want
to
give
you
a
little
bit
of
a
kind
of
overview
on
the
on
the
zoom
client,
because
it's
a
little
bit
different
than
what
we're
used
to
doing
for
those
of
you
who
are
new
here.
So
this
is
the
first
of
two.
What
we
calling
the
summer
camp
calls.
The
first
call
that
we
have
here
that
we're
doing
this.
These
are
stand-ins
for
the
JavaScript
and
SharePoint
framework
community
calls
that
are
generally
are
usually
held
by
Microsoft
and
the
pattern.
A
The
SharePoint
patterns
and
practices
group,
you're,
probably
familiar
with
them-
that
Patrick,
Rodgers
and
best
you've
been
in
or
the
two
that
generally
run
these,
and
they
record
them.
I
will
explain
kind
of
why
we're
doing
this
in
just
a
minute,
but
that
is
being
recorded.
This
is
being
recorded
and
it
also
will
be
posted
to
the
YouTube
channel.
A
The
sharepoint
patterns
and
practices
YouTube
channel
I'm
at
least
I'm
90%
sure
that
we
I'm
90%
sure
that
that
is
the
case
that
will
be
published
before
we
get
too
deep
into
this
or
make
sure
that
everyone
understands
how
this
works.
This
is
we're
using
zoom
for
the
client,
so
I
know.
In
the
past,
we've
always
used
the
Skype
for
business
to
conduct.
A
These
calls
we're
using
I
use
zoom
for
my
business,
but
and
that's
why
I'm
hosting
it
here,
making
it
easier
for
everybody
to
hear
best
to
just
confirm
to
that
we're
doing
stuff
on
YouTube.
So
let
me
first
one
little
thing
just
to
kind
of
highlight
with
this:
that's
a
little
bit
different
from
house:
Skype
works,
you're
gonna,
have
you
have
a
zoom
client
that
you
have
up
and
running?
A
You
have
the
ability
to
just
do
a
chat,
the
same
way
that
you
do
inside
the
Skype
for
business
client,
and
you
can
also
view
the
screen
share
that
I'm
doing
as
well.
I
can
see
some
people
have
already
figured
out
how
the
chat
works.
There's
a
little
there's
a
button
where
you
can
hit
to
say
to
open
up
the
the
chat.
Please
feel
free
to
go
ahead
and
pop
that
up.
You
can
actually
pin
stripe
it
off
into
its
own
little
window.
If
you
want
to
see
it
as
well.
A
I
may
not
be
able
to
stay
on
top
of
the
chat
while
I'm
going
through
some
stuff
and
that's
where,
if
you
post
a
message
to
me,
you
may
not
get
an
answer:
it's
probably
better,
if
you
post
it
to
all
panelists
and
attendees,
let
everybody
see
it,
let
everybody
jump
in.
If
you
need
to
send
a
private
message
to
me,
then
you
can.
Obviously
you
see
there's
a
way
that
you
can
do
that.
Okay,
now,
let's
look!
That's
the
housekeeping
stuff!
It's
all
out
of
the
way.
A
The
other
thing
too,
is
that
this
also
does
a
really
good
job.
Zoom
does
a
really
good
job
of
delivering
these
kind
of
webinars
and
stuff.
Some
big
big
fan
of
this
client
everything,
let's
spare
all
of
the
the
question
oh
I,
like
I,
mean
if
you
do
like
zoom,
hey,
that's
great,
but
let's
not
do
the
whole.
Oh,
we
should
start
using
zoom
for
the
sharepoint
patterns
and
practices.
Calls
that's
not
gonna
happen.
A
Microsoft
has
a
great
solution,
that
is,
for
Microsoft
teams
and
eventually,
as
asbestos
said,
we're
going
to
be
moving.
These
calls
to
Microsoft
teams
once
they
have
the
support
for
a
couple
of
features
specifically
being
able
to
have
the
notion
of
presenters
and
attendees,
so
that
some
random
person
that
joins
can't
just
hide
I
can
start
showing
stuff
on
their
screen.
A
A
We're
gonna
have
another
one
of
these
summer
camp
calls,
and
you
know
I
think
in
two
weeks
and
for
that
I
definitely
would
you
know
like
to
reach
out
and
if
you've
got
an
idea
for
a
demo.
I
would
love
to
invite
you
to
join
in.
To
be
honest,
this
one
kind
of
came
together
a
little
bit
quick
at
the
end
and
I
wasn't
exactly
sure
how
well
that
was
gonna
work
with
having
somebody
else
join
in
into
a
demo,
and
so
I
didn't
want
to
risk
it
for
this
first
one.
A
Maybe
at
the
very
end
we
can,
if
we
have
some
time,
I'm
happy
to
go
through
to
open
it
up
as
well.
Someone
does
have
a
demo
just
send
me
something
in
the
background,
but
please
just
you
know
if
you
have
an
idea
for
a
demo,
please
feel
free
to
go
ahead
and
post
it.
What
I'm
gonna
do
for
the
demo,
though,
is
I'm
gonna.
Give
you
a
little
bit
of
an
update
on
the
issue
list
that
we
have
for
SP
dot.
A
And
I
see
someone's
got
a
questionnaire
about
something
wrong
with
the
new
invite
for
the
SharePoint
framework.
Sig
calls
the
other
ones
work,
but
the
SharePoint
frame
one
doesn't
work.
It
doesn't
add
anything
to
the
calendar.
The
button
for
that
is
missing.
We
will
look
into
that.
Okay,
so
that's
the
agenda
today.
So
let's
go.
Why
are
we
doing
something
a
little
bit
different?
A
Why
do
we
have
this
one
off
and
I'm
really
glad
that
30
people
so
far
have
figured
out
that
if
things
are
a
little
bit
different,
this
time,
hopefully
we'll
be
able
to
get
up
to
over
100
or
200
like
we
did
like
we
do
for
the
special
interest
group
calls,
but
we'll
see,
apparently,
I
don't
have
as
much
of
a
draw
as
the
as
the
Microsoft
calls.
So
what's
going
on.
Why
are
we
doing
this?
A
So
in
the
last
call
or
the
last
two
calls
besa
and
Patrick
have
shared
that
the
SharePoint
development
community
activity,
specifically
the
three
scheduled
calls
that
are
done?
There's
a
monthly
call
and
there's
two
bi-weekly
calls
that
happen.
Microsoft
is
taking
the
month
of
July
off
and
the
reason
for
this.
It's
pretty
simple.
A
Most
of
the
people
that
are
running
these
calls
are
they're
all
their
different
family,
vacations
and
stuff,
and
just
the
stars
did
not
align
to
have
somebody
be
able
to
host
the
call
and
for
the
Microsoft
side
not
only
do
they
have
to
host
the
call.
Somebody
from
Microsoft
has
to
be
there
to
host
the
call,
but
then
someone
also
has
to
be
there
to
to
start
the
recording
for
it
and
they
weren't.
Nobody
was
gonna,
be
there,
and
so
they
just
said
you
know
what
it's
gonna
be
easier.
A
A
This
is
a
strictly
a
community
thing.
I'm
doing
this
as
a
community
person,
I
didn't
steal
the
slides
they
were
borrowed,
but
we're
calling
them
the
summer
camp
calls.
So
what
we're
doing
here
is
we're
doing
two
of
these
calls.
One
of
these
is
going
to
be
today
as
well
duh
on
July
the
3rd,
and
one
of
them
is
on
July
now
I.
A
So
I
took
the
liberty
of
saying
you
know
if
I'm
hosting
it
we're
gonna
move
it
to
the
3rd.
So
that's
why
we're
doing
one
today?
The
next
one
is
on
July
18th.
That's
a
Thursday!
That's
roughly
two
weeks
from
tomorrow
and
they're,
both
held
at
the
exact
same
time
that
we
usually
hold
them
so
try
to
keep
things
as
consistent
as
we
normally
do.
How
can
you
learn
more
about?
You
know?
Where
are
the
calls
and
everything
and
the
different
invites
for
them?
The
link
that
I
have
there.
A
I
saw
David
Werner
posted
this
in
the
chat
just
a
minute
ago.
A
link
to
the
community
calls
is
shown
there
on
the
slide.
If
you
go
to
that
that
location,
which
is
pretty
easy
to
just
go
to
the
SharePoint
on
development
Docs
and
on
the
left-hand
side
down
towards
the
bottom
of
the
the
table
of
contents,
navigation,
you'll
see
a
community
link
and
then
in
there
there's
a
deeper
link
for
community
calls.
A
You'll
see
two
sections,
usually
there's
one
now
there's
two,
the
first
one
is
the
official
Microsoft
calls
that
the
patterns
and
practices
group
hosts.
That's
the
one.
That's
gonna
have
the
updated
links
for
the
calls
going
beyond
August
I,
see
that
someone
who's
already
Christian
and
best
have
already
gone
back
and
forth.
That
there's
a
bit
of
an
issue
with
one
of
the
invites
Microsoft
is
gonna.
Look
into
that,
but
then
we've
added
in
another
section
for
with
invites
to
these
calls
as
well.
The
summer
camp
calls
so
welcome
you
to
join.
Please
socialize
them.
A
Let
the
world
know.
Hopefully
we
can
get.
You
know
a
nice
good
crowd
showing
up
on
July,
18th
or
start
tweeting
about
it
right
now
and
tell
people
they're
missing
out.
Okay.
So
a
couple
things
here
are
different
opportunities
to
participant
in
the
patterns
and
practices,
both
the
sharepoint
framework
and
javascript
special
interest
group.
A
Let
us
know
that
you're
interested
in
doing
something
it
helps
if
you
can
the
best,
if
you
can,
you
know,
push
as
much
and
put
as
much
of
a
description
around
what
you
want
to
end
up
demoing
with
the
SharePoint
framework
as
possible.
If
you
can
you
know,
what's
the
what's
the
value
add
what
do
you
have
to
offer
there?
If
you
have,
maybe
it
if
you
want
to
do
that
is
like
a
two
or
three
minute,
screencast
of
you
just
explaining
here's.
A
What
I
want
to
show
that's
great
that
helps
and
we
just
try
and
keep
things
try
to
avoid
from
doing
things
that
are
overtly
commercial
and
son.
You
know
here's
the
product
that
we
build
and
we
sell
it
for
this.
We
don't
want
to
do
stuff
like
that
in
the
community
call
same
deal
with,
like
anything,
that's
just
general
patterns
and
practices.
Stuff.
Are
you
working
with
the
patterns
and
practices?
Javascript
library?
Are
you
working
with
the
office
365
si
le
CLI
Steely,
the
CLI.
A
Are
you
working
with
the
SharePoint
framework,
reusable
controls,
both
the
ones
for
the
property
pane
or
for
web
part,
or
are
you
working
with
the
community,
a
generator
that
we
have
for
yeoman
that
Estefan
Bauer
has
worked
on,
but
done
so
much
great
work
around
those
are
great
demos.
All
those
things
would
be
fantastic.
Please
feel
free
to
go
ahead
and
submit
to
these.
They
would
be
absolutely
awesome.
A
The
next
thing
is
about:
how
do
you
want
to
contribute?
Do
you
want
to
contribute,
in
terms
of
with
with
the
patterns
and
practice
group
and
around
SharePoint
reporting
issues,
letting
us
know
with
things
that
you
see
something
you
think
is
wrong
an
issue
in
the
documentation.
Hey.
If
you
see
an
issue
documentation,
you
can
fix,
it
submit
a
pull
request
that
would
work.
That
would
be
absolutely
awesome
as
well.
That
helps
it
to
that.
Helps
us
as
well.
I'm
gonna
go
a
little
bit
into
that.
A
I'll
show
you
some
of
the
examples
of
stuff
that
we've
done
recently
to
make
things
a
little
bit
better
and
I've
specifically
made
some
changes
to
the
labels
and
I.
Think
it's
gonna
make
things
a
little
bit
better
for
us
and
then
again
give
us
some
feedback.
Do
you
like
these
calls?
Do
should
I
completely
scrub
the
the
second
summer
camp
call
because
I
absolutely
am
terrible
as
a
web
as
a
web
cast
host.
My
my
finish
is
terrible.
Do
we
have
documentation
gaps?
What
kinds
of
things
can
be
there?
A
We,
let
us
know
what
you
think
constructive
criticism
is
always
welcome.
It's
the
best
way
to
learn
on
what
things
are
going
on.
What
things
are
working
or
not
working?
Let
us
know
what
you
do
really
like
about
stuff,
too.
You
know
it's
it's
kind
of
hard
when
you
do
these
things
and
you
kind
of
broadcast
up
and
people
consume.
Hey,
that's
fine!
You
know
we're
not
trying
to
when
I'm
trying
to
make
you
know
money
off
these
things,
but
getting
some
sort
of
feedback.
You
know
what
things
resonate.
A
Even
if
it's
something
you
think
is
good.
You
know.
Let
us
know
that
you
that
things
are
good
there,
because
you
know
if
we
don't
see
people
saying
it's
classic,
you
know
anything
if
you,
if
you
don't
see
people
telling
you
or
get
feedback
that
says
hey.
This
is
a
great
thing
that
you
guys
are
doing
or
hey
this.
This
documentation
is
great
or
this
special
interest
group
is
fantastic.
If
you
don't
hear
those
things,
then
maybe
when
we're
trying
to
figure
out
you're
planning
things
in
the
future,
well,
nobody
really
says
they
like
it.
A
So
we
may
just
go
ahead
and
cut
it.
You
know
if
there's
nothing
there,
we
don't
really
have
any
data
points.
So
let
us
know
if
you
like
stuff,
let
us
know
if
you
don't
like
stuff.
Let
us
know
if
I
don't
know
just
let
us
know
stuff
all
right.
So,
let's
first
start
and
I'm
into
SharePoint
framework
stuff.
Now
I'm
not
this
is
it
says
the
latest
from
SharePoint
engineering
I
am
NOT
as
a
disclaimer
I'm,
not
I,
do
not
work
for
Microsoft,
not
in
SharePoint
engineering.
I.
Don't
have
anything
new
to
share
here.
A
This
is
a
rehash
of
the
stuff
that
has
already
been
presented
at
the
last
special
interest
group.
For
those
of
you
who
are
new
to
the
call.
This
is
nothing
you
know:
I'm,
not
gonna,
I'm,
not
going
to
announce
anything
in
here.
Okay,
it's
not
my
role.
First
of
all,
a
couple
things
if
you
want
to
go
through
and
you
want
to
learn
more
about
the
SharePoint
development,
you
want
to
learn
more
about
the
documentation
or
you
want.
If
you
want
to
dive
into
the
documentation,
you
got
a
quick
little
AKMs
link
a
short
link.
A
You
go
to
SP
dev
docs.
That
will
take
you
to
the
SharePoint
development
documentation.
You
can
find
SharePoint
framework
Doc's.
You
can
find
true
the
older
development
models,
documentation,
there's
things
about
site,
designs
and
site
scripts,
there's
all
kinds
of
Doc's
that
are
in
there.
If
you
want
to
see
previous
videos
that
have
been
done,
both
recordings
of
the
different
special
interest
group
calls
different
demos,
different
I,
think
with
desa
and
Waldeck
do
their
dev,
weekly,
podcast
or
videocast
video,
whatever
you
want
to
call
it.
That
is
also
posted
up
there.
A
A
Issue
list
now
that
issue
list
is
for,
like
general
SharePoint
development
issues
that
don't
fall
into
another
bucket
and
what
I
mean
by
that
is
like
we
have,
which
you'll
start
to
see.
You
may
have
already
seen
this
already,
but
certain
projects
that
have
their
own
repositories
in
the
either
patterns
and
practices
or
the
SharePoint
organization
on
github.
If
we
have
a
repo
that
has
a
specific
project
and
you
post
something
to
the
SPG
abducts
issue
list,
we
may
transfer
that
issue
over.
A
If
it's
in
the
same
organization,
then
we
can
transfer
the
issue
from
this
issue
as
to
another
one.
So
a
good
example
of
that
is
the
provisioning
stuff.
You
may
have
seen
a
bunch
of
issues
disappear
from
the
provisioning
or
from
this
SP
dev
Docs
issue
list
and
they've
all
been
moved
over
to
the
to
the
provisioning
repo,
because
there's
a
whole
team.
That
kind
of
is
involved
with
that
and
with
the
provisioning
project,
and
it
makes
more
sense
to
have
those
issues
over
there.
A
Some
issues,
though,
can't
be
transferred,
and
that's
simply
because
they're
in
different
orgs,
so
I
believe
like,
for
example,
the
CLI,
the
office
360,
Li
and
I
believe
the
ppj
s
is
also
in
the
PNP
org,
and
so
you
can't
like
we
can't
as
easily
transfer
those
issues
over.
But
what
we
end
up
doing
is
we
will
you
know
post
a
message
saying
hey
that
makes
more
sense
over
here,
and
then
we
close
the
issue.
So
we
don't
try
it
we're
trying
to
keep
things
very.
A
You
know
all
the
like
issues
together:
okay,
so
a
couple
of
things:
if
you're
not
familiar
with
this,
the
SharePoint
frame,
the
SharePoint
engineering,
has
a
it
shows
the
it
has
a
training
package
related
to
SharePoint
framework.
These
are
nine
different
modules
that
are
provided
by
the
by
the
the
SharePoint
engines
by
Microsoft
for
kind
of
self-paced,
hands-on
training
for
the
SharePoint
framework,
and
it
goes
everything
from
doing
your
very
first
SharePoint
framework
component
to
learning
how
to
build
web
parts.
A
Extensions
working
with
content
and
SharePoint
like
working
with
the
SharePoint
REST
API
working
with
third
party
API,
is
like
the
Microsoft
graph
for
calling
an
azure
ad
secured
API
I.
Think
in
that,
in
that
one
we
actually
call.
We
actually
call
the
Microsoft
graph
because
it's
secured
with
Azure
ad,
but
we
also
have
one
that's
specific
for
the
Microsoft
graphic
as
well
that
we
have
another
project
as
well.
How
do
you
how
to
get
a
quick
little
ramp
up
on?
A
You
know
how
to
work
with
react,
how
to
work
with
the
fabric,
react
components,
deployment
things
and
then
also
working
with
Microsoft
teams
within
the
context
of
SharePoint
framework.
These
are
all
things
that
I
mean
I've
worked
on.
I've
worked
on
these
with
VESA
and
I,
made
sure
that
you
know
this
content
is
all
been
refreshed.
We
refresh
it
every
quarter.
A
It
recently
got
refreshed
in
the
last
and
last
couple
weeks,
which
means
that
somebody
has
has
had
eyes
on
this,
and
it's
been
all
the
stuff
has
been
tested
and
we
made
sure
that
everything
still
works
and
it's
all
using
the
latest
version
of
the
SharePoint
framework,
as
it
is
today.
Sharepoint
framework
version,
1.2
and
we'll
do
that
again
in
the
next
couple
months
as
well.
We
do
that
once
a
quarter
to
make
sure
this
stuff
is
always
current.
A
Unlike
the
previous
ones,
we
had,
which
had
gotten
a
little
bit
outdated
and
long
in
the
tooth.
So
you
can
learn
more
about
that
at
a
kms,
/s
pfx
training
you'll
find
a
hands-on
lab.
You'll
find
some
slides
and
you'll
find
a
link
to
a
screencast
of
someone
presenting
the
slides
and
the
demo
if
they
were
standing
up
at
a
user
group
doing
it.
So
these
are
great
for
self-paced
learning,
they're
great
B,
to
take
to
your
local
user
groups
and
use
them
in
your
own
presentations.
A
The
demos
inside
the
inside
the
the
the
screencast
and
in
the
slides,
that's
the
actual
result
of
the
exercise
in
a
hands-on
lab.
That's
in
the
same
module,
so
you
can
do
the
presentation
someone
says:
well,
how
did
you
build
that
web
part
managed?
You
showed
it
to
me,
but
how'd
you
build
it.
You
like
go
to
the
lab.
There's
a
hands-on
thing.
You
can
do
it
yourself.
A
No
it's
next
with
the
SharePoint
framework,
all
right.
So
the
next
thing
that
we
have
is
chef
weight
framework
version
1.9.
This
is
latest
that
Microsoft
has
shared.
This
is
planned
to
be
released
on
July
the
9th.
What
is
that
next
Tuesday?
So
keep
your
eye
out
for
that.
What
is
that
gonna
do?
What
stuff
is
this
gonna
have
there's
a
couple
things
that
they've
talked
about?
That's
gonna
include
in
it.
So
one
thing
is
the
library
component,
which
is
introduced
as
a
dev
preview
capability.
A
A
What
they're
doing
is
they're
there's
been
some
issues
if
you,
if
you've
noticed
this
inside
the
issue
list,
some
people
who
have
been
working
with
the
Marc
subgraph,
really
anything
that
requires
and
an
access
token
an
OAuth
token
to
call
a
secure
third-party
endpoint.
So
that's
gonna
be
anything
that
uses
the
azure
ad
HTTP
client
object
and
the
Microsoft
graft
client.
Both
of
them
use
the
same
interest
infrastructure
to
obtain
an
access,
token
people
who
have
been
using
those
in
SharePoint
no
problem.
A
People
who've
been
trying
to
use
those
same
things
inside
of
a
SharePoint
framework
web
part,
that's
running
as
a
tab
inside
of
Microsoft
teams.
It
works
in
the
browser,
it
doesn't
work
in
the
clients
and
then
it
also
has
had
issues
where
these
components
that
have
been
created
and
been
deployed
where
we're
having
issues
with
them.
A
Also
within
the
within
the
mobile,
the
SharePoint
mobile
client
Microsoft
has
been
working
on
that
they've
been
working
on
the
fixes
for
that
there
is
a
workaround
that
we
have
that's
inside
that's
listed
inside
the
issue
us,
however,
they're
working
to
clean
that
stuff
up
and
and
address
that
challenge
that
should
be
in
1.9.
Also,
we've
noticed
that
there
are
some
issues
with
the
isolated
web
part
model,
specifically
this
for
the
support
with
them
when
you're
running
them
when
you're
running
an
isolated
web
part
as
a
inside
of
Microsoft
teams.
A
Well,
that's
gonna
get
fixed
in
1.9
and
then
there's
some
also
improvements
with
Microsoft
teams
integration,
but
they
are
adding
what
details
of
those
I
don't
know,
I'm
just
the
messenger.
On
this
case
they
say
the
next
update
or
the
next
release
for
SharePoint
framework
is
gonna
be
on
and
on
August
the
13th
is
that
19.1
is
that
1.10
I,
don't
know
we'll
see
how
that
goes.
A
Other
things
that
they're
they're
working
on
under
the
covers
that
are
behind
the
scenes
being
able
to
do
the
same
thing
that
we
can
do
with
webparts
and
Microsoft
teams
as
custom
tabs
they're
looking
to
do
that
same
kind
of
an
infrastructure
with
office.
Add
ins
so
you'll
be
able
to
leverage
of
sharepoint
framework
development
inside
of
office
add-ins
as
well
improvements
around
content
security
policy.
A
I
see
some
dotnet
standard
release,
a
story
for
the
store
option
for
your
sharepoint
framework
solutions
from
being
able
to
have
a
better
way
to
sell
and
distribute
your
customizations
additional
content,
extensions
for
modern
pages.
This
is
kind
of
cool,
but
think
of
this
is
like
a
significant
improvement
around
sharepoint
framework
application
customizers.
I
don't
know
how
much
I
can't
remember
exactly
how
much
they
might
have
to
share
with
us.
I'm
not
entirely
sure
what
what
they've,
what
they've
shared
there
so
I'm
gonna
leave.
A
A
Also,
one
thing
that
a
bunch
of
us
is
I'm
working
on
are
a
bunch
of
getting
started,
videos
that
are
coming
soon.
These
are
going
to
be
kind
of
drip
released
over
the
summer,
and
the
idea
here
is
that
they're
all
less
than
10
minutes,
that's
good
to
see
that
they're
10
minutes,
because
I
thought
at
first
there
were
looking
five
minutes
and
so
far
my
videos
have
been
like
10.
Let's
say
that
they're
less
than
10
ish
minutes,
because
I
know
one
of
mine
is
11.
A
The
idea
here,
though,
is
you
don't
to
go
through
some
big
training
and
all
this
stuff?
If
you're,
just
like
you
know
what?
Let's
just
let
me
see
really
quick
demo
of
something
working,
it
show
me
how
you
did
it,
that's
what
these
are
for,
and
so
it's
supposed
to
be
something
really
quick.
So,
like
I
did
one
on
working
with
Microsoft
graph
and
I
did
one
on
something
else
that
I
just
now
forgot,
but
there's
a
bunch
of
them
that
we've
done.
A
We
got
stuff
around
site
designs
that
have
been
done
and
a
whole
bunch
of
other
things.
There's
a
long
list
so
expect
to
see
more
of
this
stuff
getting
dripped
out
in
the
coming
weeks
throughout
the
summer.
Okay.
So
now
let
look
at
that
rabbit.
Now,
let's
talk
about
some
stuff
related
to
different
components
that
are
out
there
that
we
have.
So
what
things
do
we
have
that
that
we
can
divide
that
are
updated,
that
we
can
share
with
you
so
from
the
p.m.
PJs
library.
The
latest
release
that
we
have
for
that.
A
We
have
flying
bunnies.
The
latest
release
we
have
for
that
is
1.3
dot
4
that
was
released
on
July
that
12th.
The
two
updates,
so
Patrick
asked
me
to
share
some
stuff
with
this
they're
doing
a
lot
more
updates
work
is
continuing
throughout
the
summer
on
the
v2
of
p.m.
PJs.
You
can
get
involved
by
going
to
this
link
that
you
see
this
listed
here.
That's
where
they're
working
on
the
updates
and
sharing
their
progress
all
out
in
the
open.
You
can
see
the
stuff
that's
going
on
around
p.m.
PJs,
so
really
great.
A
It's
a
good
library
for
accessing
SharePoint
a
lot.
It's
like
a
fluent
based
API
to
access
like
SharePoint
rest,
but
then
also
talking
to
the
Microsoft
graph
and
other
things
as
well.
Alright,
that's
that's
the
big
business,
the
big
pieces.
As
you
see,
you
can
learn
more
about
it.
If
you
go
to
PMP
github
io
/
p.m.
PJs
I
can
see
David
just
posted.
Something
would
love
some
more
love
to
get
more
people
involved
that
want
to
help.
You
can
learn
more
about
the
about
v2.
A
A
It's
kind
of
a
simplified
login,
as
was
one
of
the
big,
focuses
of
that,
as
well
as
a
bunch
of
reorganize
and
restructure
commands.
You
can
get
that
by
you
by
installing
a
global
package
using
NPM,
install
global
or
just
at
G,
and
then
saying
at
PMP,
slash
office,
365
CLI
that'll
give
you
the
art
that
1.2
2.0
version,
if
you
put
the
@
next
on
the
end
of
it,
that
will
give
you
the
next
version
or
the
v2
version
of
it.
A
Alright,
let's
talk
about
reusable
components:
I
love
the
little
clipart
in
the
bottom
right
hand
corner
it's
like
those
people
are
reusable,
so
we
can
pick
them
up
and
we
can
put
them
wherever
we
want
to
use
them.
So
I'm,
gonna,
try
and
grab
I'm
gonna
try
and
grab
the
guy
on
the
left
there
to
do
my
my
financial
stuff,
it
looks
like
he's
kind
of
more
studious.
A
Although
the
red
pants,
the
black
shirt,
that's
a
little
edgy,
so
I'm,
not
sure
if
I
want
my
finance
guy
doing
that
anyway,
back
to
the
regularly
scheduled
program
trying
to
channel
my
inner
Chris
Kent
humor
there,
which
I
doing
a
very
poor
job,
we're
missing
the
warrior
horses
today,
I
wish
I
had
a
slide.
That
was
just
for
warrior
archers.
A
If
you
guys
don't
know
what
that
what
that
joke
is
about
about
the
warrior
horses
and
you're
totally
missing
out
on
these
calls.
Okay,
so
this
is
a
project
that
Elios
truth
is
is
behind,
or
it's
actually
a
pair
of
projects
that
it
was
strippers
behind.
What
he's
done
is
there
are
some
reusable
controls
that
you
can
use
inside
of
your
sharepoint
framework
projects.
A
Specifically,
these
are
for
webparts,
and
what
we
have
here
is
that
you've
got
one
set
for
components
that
you
can
use
inside
your
your
your
react
based
SharePoint
framework,
webparts
and
then
there's
another
project
you
can
use
where
you
can
use
the
components
inside
that
any
kind
of
web
part
because
they're
designed
to
only
be
used
inside
the
property
pane.
So
the
property
pane
controls.
A
So
you
can
just
pick
from
a
list
and
it
saves
you
having
to
write
all
that
business.
Logic
of
you
know:
initializing
the
drop-down
control
to
pick
a
specific
list,
so
these
are
good
for
any
web
part.
It
doesn't
matter
if
you're
using
a
web
framework
or
not
because
everything
that
goes
inside
the
property
pane
is
react
based.
These
are
all
react
based
as
well
as
they
work
they
work
really.
Well,
then,
the
second
controller
G
or
the
second
list
of
a
second
project
you
see
listed
there.
The
controls
react
version.
A
So
if
you
add
a
webpart
to
the
page
and
it
needs
a
lot
of
setup
stuff,
but
you
know
say
you
maybe
need
to
pop
up
in
a
wizard
or
maybe
you
need
to
go
work
with
the
property
pane
that
that
one
that
you
see
there
in
the
middle
but
configure
your
web
part,
that's
the
place,
holder
control.
So
someone,
as
is
a
page.
It's
kind
like
the
image
image
control
the
image
web
part
where
you
add
to
the
page,
you
kind
of
pick
an
image.
A
Otherwise
it's
kind
of
useless,
so
that's
all
set
up
as
well.
So
you
can
learn
more
about
those
at
these
two
lengths.
You
see
there
on
the
slide
versions.
For
those
there
has
not
been
a
new
version,
since
the
last
patterns
and
practices
call
so
yeah,
so
those
are
the
new
versions
or
there's
a
current
versions.
Now
let
me
talk
a
little
bit
about
the
yeoman
generator
these
the
times
and
practices
yeoman
generator
that
Stefan
Bauer
has
done.
This
is
a
again
similar
to
the
the
last
ones.
This
is
the
same
version
version.
A
18.0
is
the
same
version
that
was
available
during
our
last
call,
and
what
this
is
is.
This
is
a
superset
of
what
we
already
can
do
with
the
yeoman
generator
for
sharepoint
or
the
sharepoint
generator
that
we
have
for
yeoman
that
we
use
for
sharepoint
framework
projects
that
Microsoft
provides.
What
this
does
is.
A
This
is
a
generator
that
inherits
from
the
Microsoft
one
and
it
what
it
does
is
it
allows
you
to
do
a
lot
more
stuff
to
your
project,
so
it'll
it
can
do
some
setup
for
things
like
template
setup,
a
templates
for
your
project
for,
if
you're
using
view
or
if
you're,
using
knockout
or
handlebars
or
angular,
not
just
react
and
knockout,
which
we
normally
get
from
a
SharePoint
framework
project,
but
it
does
a
whole
lot
more
stuff
as
well.
It
has
the
ability
to
set
up
things
testing
up
in
your
project.
A
It
has
some
CI
NCB
stuff,
that's
built
into
it,
allowing
you
to
add
jQuery
to
it
as
well.
There's
there's
a
whole
lot
of
stuff,
but
this
adds
to
your
project.
This
is
not
a
replacement
for
the
one
that
Microsoft
provides
this,
because
when
you
install
this,
it
is
using
the
micro
one
that
Microsoft
provides
it's
just
adding
in
extra
stuff
after
Microsoft
does
the
provisioning
of
their
project
so
think
of
this.
A
It
I
like
to
think
of
this
and
I
hope
that
step
one
doesn't
take
offense
to
this,
because
I
think
of
this
is
a
good
way
to
describe
it.
To
me,
this
generator
is
like
a
macro
for
your
existing
product.
For
the
other
generator
you
install
the
generator.
You
have
the
original
generator,
which
creates
the
project
that
you
need,
and
then
this
one
can
do
a
bunch
of
other
stuff.
In
addition
to
it,
the
nice
thing
is,
is
that
when
you
run
this
generator,
the
PMP
SPF
X
generator,
it
automatically
runs
the
Microsoft
one.
A
First,
based
on
the
questions
that
you
ask
or
you
answer,
and
then
it
will
do
a
bunch
of
other
stuff
so
like
today,
if
I
told
someone,
here's
how
you
do
real
testing
with
react,
because
we
don't
have
that
by
default.
Inside
of
the
react,
template
webpart
project
in
a
SharePoint
framework
from
the
SharePoint
framework,
generator
we
have
from
Microsoft
I
would
say:
go
first
create
your
react
based
web
part
project.
A
Once
that's
done,
you
need
to
install
just
and
you
need
to
install
all
these
other
dependencies
or
there's
a
preset
that
I've
created
that
I
put
out
there
that
you
can
use
to
paying
on
the
version
of
react
you're
using.
You
then
need
to
install
this
preset
and
then
go
make
this
configuration
file
and
then
go
modify
the
package.json
file
to
do
these
other
things.
The
nice
thing
is:
is
that
what
this
does?
It
does
all
that
stuff
for
you,
so
it
makes
your
life
a
heck,
a
lot
easier.
A
A
Let's
come
over
here
to
oh
there's,
a
doc,
so
one
more.
What
I
want
to
show
you
this?
That's
right!
If
you
come
over
here
to
the
SharePoint
developer,
documentation
so
I'm,
just
over
here
at
the
which
of
the
SharePoint
dev
Doc's
right
here
at
the
core
of
the
development
piece
down
here
at
the
bottom.
You
see
that
there's
a
community
link
if
I
go
to
community
and
then
click
on
community
and
then
over
here
on
the
right
hand,
side
you
see,
we've
got
two
sections
one
for
community
calls
and
one
for
summer
camp
calls.
A
Here's
the
community
calls
here
are
the
links
to
the
community,
calls
that
are
available
to
us.
I've
been
watching
a
little
bit
of
a
back-channel
conversation
as
well
from
when
I
believe
it
was
Christian.
W
said
there
was
a
problem
with
this.
These
calls
really
not
this
one.
This
one,
the
SharePoint
framework,
call
besa
and
Patrick
Rodgers.
Have
been
looking
into
it,
they
noticed
a
little
something
weird,
but
they're
still
they're
still
looking
into
it.
This
went
a
little
bit
farther
down.
These
are
the
calls
that
I
refer
to
as
the
summer
camp
calls.
A
Well,
this
is
the
one
we're
doing
right
now.
This
is
the
one
that
we'll
be
doing
and
roughly
two
weeks
and
the
community
column
is
updated.
Microsoft
Eames
Mandy,
they
will
be
they
I.
Don't
I
I
think
that
the
I'm
gonna,
let
vests
a
comment
on
that
or
a
Patrick
comment
on
that
yeah,
so,
okay,
I'm,
gonna,
I'm
gonna.
A
Let
best
to
comment
on
that
and
a
chat,
because
I
can
see
he's
doing
that
the
chat
he
says:
okay,
so
first
to
Christian
test
the
SharePoint
for
invite
they
just
recreate
the
ACS
file
and
updated
MS
links
to
the
background.
It
should
work
with
any
issues
but
we'd
love
to
get
confirmation.
Download
and
save
your
caliber
should
work
now.
My
understanding
is
also
tune
in
D
is
that
these
are
also
going
to
be
I
think
these
are
the
team's
invites
and
I
believe
these
are
the
team.
A
Yes,
these
are
the
team's
invites
cool,
so
they
will
be
okay,
so
we
just
need
to
go
back
and
update
the
docs
so
that
these
say
direct
Skype
link
they'll
be
direct
team's
link
cool
alright.
So
that's
those
now,
let's
come
over
here
to
the
dev
doc,
so
Mike
over
here
to
github.com,
slash
SharePoint,
so
SP
dev,
Doc's
I.
Never
can
remember
those
aka
done
MS
links.
A
A
There
we
go
so
when
it's
time
so
right
now
you
get
you
go
to
this
and
when
it's
time
bestest
saying
that
like
in
August,
they
will
they're
gonna
update
the
AKMs
to
point
to
the
actual
team's
invite
so
right
now,
they're,
not
the
team's
n
bite,
but
this
is
where
it
is
so,
there's
no
changes,
they're
gonna
route,
the
request
automatically
got
it
cool,
actually,
David.
Let's
not
do
we
don't
want
people
to
go
to
go
to
that
link
right
that
we
want
to.
We
want
to
use.
A
We
want
everybody
come
from
here,
because
they're
gonna
change
that
a
kms
links
to
point
to
the
right
one.
Okay,
so
all
right
there
we
go
so
now.
Let
me
go
back
to
my
dogs
and
where
was
I
I
was
on
github
docs.
There
we
go
okay,
so
now
this
is,
let
me
show
you
something
changes
we've
made
to
the
SharePoint
Deb
ducks
here
and
yeah
I've
kind
of
been
I've
been
busy
lately,
so
I've
been
going
through.
All
the
triage
is.
Let
me
show
you
some
of
the
changes
we
made.
A
So
one
of
the
changes
we
made
thanks
to
is
he
on
the
call
no
Vincent
on
during
a
recent
call.
I
did
a
demo
on
working
with
the
issue
list
and
giving
people
a
little
bit
of
an
update
on
some
stuff.
One
of
the
things
where
the
bits
of
feedback
we
got
was
hey
would
be
nice
if
the
descriptions
of
all
of
these
labels
were
filled
in
so
guess
what
they're
all
filled
in
or
they're
all
well
at
least
the
ones
that
make
sense
are
all
filled
them,
which
is
most
of
them.
A
So
I
got
here
by
seeing
the
difference
for
what
these
things
are
right
here
on
this,
where
it
says
the
labels
right
here,
I'm
just
clicking
on
labels
and
I
can
see
a
list
of
all
the
labels
that
are
available
to
us.
So
these
areas-
these
are
things
like
think
of
this,
as
like
a
category
so
I'm
just
going
to
explaining
what
these
things
are,
what
you
can
expect
to
see
from
these
different
items,
if
I
scroll
down
a
little
bit,
show
you
some
of
the
changes
that
we've
made.
A
A
In
the
description
of
this
video
when
it's
posted
in
youtube.
If,
ideally,
though,
I
could
just
I'm
gonna
try
and
put
it
as
the
whole
body
of
the
chat,
I
just
don't
know
if
it's
gonna
get
truncated
off
good
question,
though
Tristan,
let's
see,
so
we
did
that
here's
some
of
those
stuff
that
we
did
so
in
the
past.
We
made
some
changes
here
on
this
needs
section.
A
So
what
you'll
see
here,
we've
also
we've
always
had
this
author
feedback,
which,
if
you
recall
what
author
feedback,
does
it's
a
way
for
if
someone's
posted
an
issue
and
then
somebody
from
Microsoft
or
somebody
else
says
you
know
hey,
we
need
more
information.
The
originating
author
or
the
original
poster,
which
you
see
is
referred
to
as
Opie.
If
they
mean
to
respond
to
us
and
they
need
to
give
us
additional
info
and
we
will
put
this
needs,
this
needs
offer
feedback,
and
what
that
does?
A
Is
that
kicks
off
a
workflow
that
will
wait
for
seven
days
for
the
author
to
respond?
If
they
don't
respond,
it
will
flag.
The
issue
is
under
as
no
activity
and
put
a
message,
put
a
comment
in
the
issue,
and
then
it
will,
after
another,
seven
days
if
they
still
respond
to
go
and
automatically
close
the
issue,
because
apparently
it's
either
the
original
posters,
not
gonna,
present,
isn't
engaging,
and
so
there's
really
nothing
for
us
to
really
act
on
if
we
need
more
information.
A
One
thing
changes
that
I
did
make,
though,
was
that
you
see
here
that
we
have
this
mean
to
reproduce
steps.
So
we
used
to
have
this
a
different
label
that
was
referring
to
reproduction
like
reproducing
the
issue
about
reproduction
that
doesn't
sound
right.
We
have
another.
We
had
another
label
about
giving
us
a
repro
of
the
issue
that
you're
having
I
think
it
said.
Like
internal
slash,
read
throat
no
repro,
it
was
a
little
cryptic
and
I
just
said.
Well,
really,
you
know
what
it
is.
A
It's
a
request
for
us
back
to
the
original
poster,
and
so
we
change
that
label
to
be
means,
reproduced
steps
and
a.
We
need
to
be
able
to
reproduce
the
issue,
and
then
you
can
see
a
list.
We
bought
moving
and
moved
all
those
issues
over
to
it
and
then
now
we
also
have
another
one
here
where
you
know:
there's
a
I
do
this
myself
and
I've
got
it.
We
got
a
couple
of
people
on
the
on
the
core
team
of
the
parents
and
practices
who
have
rights
to
be
able
to
label
things.
A
If
you
sometimes
there's
things
that
you
know
most
of
time,
we
can
resolve
something
or
we
can
figure
out.
The
problem
is,
but
sometimes
it's
like
hey
this.
Isn't
this
isn't
me
this
isn't
something
that
I
can
do,
and
so
we
need
Microsoft
to
jump
in.
We
need
engineering
to
jump
in
when
you
Besta
jump
in
when
you
Patrick
to
jump
that
we
need
somebody
to
jump
in
to
give
their
input
on
it,
and
so
we
now
have
this
new
label
here
for
needs.
Microsoft
Review.
A
So,
for
example,
I
know
that
there's
one
of
these
issues
that's
out,
there
is
around.
Where
is
it?
It
is
this
one
this
this
item
potent
issue
is
site
scripts
and
it
was
a
question
that
came
up
about
hey.
This
doesn't
seem
to
work
the
way
it's
intended
to
and
the
docs
are
exactly
they
don't
tell
us
what's
going
on,
and
so
we
went
through
and
we
started.
We
were
looking
at
this
and
said.
Well,
you
know
this
isn't
really
something
that
the
community
can
answer.
A
This
is
something
that
the
people
at
Microsoft
they're,
the
engineers
need
to
say:
yes,
they're
doing
what
they
need.
They're
supposed
to
be
doing.
It's
not
an
issue.
The
docs
are
just
a
little
ambiguous.
So
after
we
hit
this
little
dialog
going
back
and
forth,
we
ends
up
saying.
Well,
you
know
what
this
isn't
something
we
can
resolve.
This
is
something
they
have
to
do
instead,
so
we
tagged
it
as
needs
review.
A
A
We
don't
know
if
it's
a
bug
if
it's
confirmed
a
bug
from
Microsoft
or
if
it's
really,
we
think
it
might
be
a
bug,
and
so
what
we
did
was
we
created
two
separate
labels,
one
to
show
that
things
are
we're
not
really
sure
if
it's
a
bug
or
not,
and
so
we
have
this
bug
suspected
and
once
something
is
confirmed
as
a
bug,
then
we
go
through.
We
do
a
bug
confirmed
and
we
go
through
and
then
lock
that
up
periodically.
A
We
also
go
in
and
look
and
see
if
the
bug
where
we
have
bug
confirmed
these
are
the
some
nice
issues
go
through
and
look
up
where
you
see
bug,
confirmed
and
working
on
it
or
bug,
confirmed
and
tracked.
That
means
that
Microsoft
is
aware
of
it.
They've
confirmed
it's
a
bug
and
they
now
have
something
on
their
own
internal
system
where
they
have
an
issue
and
it's
been
assigned
to
an
engineer
and
they're
watching
it.
They're
gonna,
they're,
gonna
manage
it
or
hey,
look
they're
actually
fixing
the
problem.
A
Now
we're
working
on
it
and
once
they've
rolled
the
problem
out,
then
they
can
say:
hey
has
been
fixed
or
it's
being
fixed
in
the
next
crop
in
general.
What
fix
next
drop
means?
It
means
the
next
version
of
SharePoint
framework
is
going
to
include
this
fix,
or
it's
that
the
fix
is
a
server-side
that
is
starting
to
roll
out
through
the
target
release,
Springs
and
the
standard
release
as
well
periodically.
Then,
over
time
we
look
at
the
things
that
are
listed
as
fixed
and
fixed
next
drop.
A
We
confirm
that
those
things
have
been
fixed
and
then
we
go
in
and
we'll
close
those
issues.
These
things
right
here
where
you
see
the
status
tracked.
These
are
important
that
we
don't
close
these
both
you
and
the
community,
don't
close
your
own
issue.
This
list
is
tracked
same
thing
on
our
side
as
well.
We
don't
close
them
and
the
reason
why
is
because,
if
we
close
them
in
the
github
side,
that's
tracked,
then.
A
A
It's
all
fixed
then
put
a
comment
in
there
and
just
say:
hey
this
thing
has
been
fixed
and
call
out
me
or
call
out
that's
or
call
call
somebody
out
and
let
them
know
that
hey
this
has
been
fixed
and
then
what
we
do
on
our
side
behind
the
scenes
is
we
just
make
sure
that
Microsoft
knows
hey.
This
issue
can
be
closed,
but
you
guys
probably
want
to
close
yours
internally
and
when
you
do
that,
then
close
the
issue.
So
we
don't,
we
don't
do
that
for
them.
A
So
these
are
all
some
of
the
big
changes
that
we've
made
with
this
and
then
again
as
I
mentioned
earlier,
we
are
also
starting
to
move
things
out
of
this
list.
So
if
we
see
things
like
like
this
one,
so
this
right
here
this
is
clearly
a
provisioning
thing.
I'm
not
currently
logged
in
so
I'm
gonna.
Do
this
in
just
a
minute.
I'll!
Do
this
a
little
bit
later,
but
this
guy
right
here
when
I
when
I
go
to
when
I.
A
When
I
look
at
this
issue,
there
will
be
a
there's,
an
option
that
we
have
over
here
for
some
people.
That
will
that,
where
we
can
say
transfer
the
issue
and
what
we'll
end
up
doing
is
what
transfer
this
over
to
the
provisioning
repo,
so
that
now
it
won't
be.
It
won't
be
listed
inside
of
this
repo
and
then
the
issues
still
exist.
The
user
will
be
notified
that
things
have
moved
around
it's
there.
Things
will
be
in
good
shape.
A
A
So
come
on,
go
fullscreen
again
that
is
my
demo.
That
I
had
to
show
you
guys-
oh
I'm,
also
working
on
a
wiki
page
that
we
will
link
to
and
each
one
of
the
issues
that
will
cover
some
of
the
high
high
high
value
items
that
I
mentioned
in
the
call
a
couple
in
one
of
these
calls
I
believe
it
was
like
two
weeks
ago.
Maybe
it
was
four
weeks
ago
where
I
talked
about.
A
You
know
how
to
create
a
good
issue:
how
to
create
a
good
pull
request
stuff
like
that
all
right,
so
we
will
have
a
wiki
page.
It
shows
a
lot
of
stuff
I
wanted
to
get
the
labels
done
first,
because
it's
gonna
essentially
be
our
documentation.
For
that
page,
quick
reminder
here.
The
next
SharePoint
framework
in
JavaScript
special
interest
group
these
or
the
the
summer
camp
call
will
be
on
July
18th.
That's
in
two
weeks
from
tomorrow.
A
If
you
want
to
learn
more
about
the
patterns
and
practices
group,
you
go
to
a
kms
and
now's
our
time
for
any
open
QA.
So
if
anybody
has
any
questions
so
we've
lost
some
people
may
have
any
questions.
Oh
now
would
be
a
good
time
to
go
ahead
and
post
them.
It's
not
I.
Give
it
a
I.
Give
another
couple.
Minutes:
I,
don't
see
anything
come
in,
then
we
will
go
ahead
and
wrap
the
call
up
any
questions.
A
A
A
Look
at
that
rhyme
Healy
people
know
these
things,
so
the
link
that
you
shared
that
went
to
something
that
doesn't
exist.
Ryan
on
I,
conformed
fabric
assets,
so
I,
don't
know
that
would
be
something
you
would
want
to
go
ping
the
fabric,
the
betrayal,
our
team,
I,
think
you
want
to
check
it
from
the
check
those
check
out
with
those
guys,
let's
see,
you're
welcome
and
Ruby
thanks
for
thanks
for
jumping
in
Mike
Z
on
the
SharePoint
framework,
sample
extensions
and
github.
A
All
of
them
are
supposed
to
work
with
three
basic
commands
get
bundle
package.
No,
those
aren't
the
commands,
so
the
commands
are
it's
gonna
be
you're,
gonna
want
to
first
clone
it,
and
then
you
should
be
able
to
do
get
build,
get
bundle
and
get
package
solution.
However,
all
of
those
projects,
as
you
see
here,
let
me
go
back
to
my.
A
You
notice
over
here
look
at
the
date
on
when
these
were
so
there's
some
like
this
one
was
updated
for
the
release
candidate
1.2,
your
your
mileage
will
vary.
These
are
samples
that
have
been
provided
by
the
community.
We
have
not
gone
through
and
made
updates
to
every
single
one
of
these
to
make
sure
that
they
are
working
with
the
latest
version,
the
SharePoint
framework,
as
you
can
see,
there
are
quite
a
few
samples
that
are
in
here.
It's
really
up
to
these
are
pure
community
things.
A
So
this
is
it's
not
guaranteed
that
they
are
going
to
work
right
out
of
the
box,
can't
say
so.
The
best
thing
you
get
you
that
you
can
do
is
best
thing
you
can
do
is
just
is
to
check
out
each
one
and
you
made
it
mean
to
go
through
into
making
up
make
an
update
to
it
so
like
over
here.
If
I
look
at
this
react,
MS
al
bot
and
I
come
in
to
the
actual
project.
A
This
one
is
using
the
SharePoint
framework,
1.5
dot
1.
So
that's
you
know,
that's
very
old
that
is
I,
believe
early
2017
like
February,
oh
no
2018,
February
or
March
ballpark
somewhere
right
in
that
time,
so
your
mileage
may
vary
you're
right,
so
you
say
you've
you
found
some
you've
tried
some,
not
sure.
If
they're
supposed
to
be
working
this
something
I'm
doing
or
it's
outdated,
I
would
put
money
on
it.
It's
probably
just
outdated.
You
just
have
to
see
there.
A
Are
there
different
ways
you
can
go
through
it
and
to
try
and
update
these
the
office.
365
CLI
has
a
command
that
you
can
use
to
make
your
life
easier
to
update
them.
Hey.
You
want
a
good
community
project,
good
community
contribution
for
PMP.
Go
somebody
come
in
and
start
going
through
these
projects
and
start
updating
them.
If
there
was
a
button
to
upgrade
all
the
projects,
we
would
do
it
a
second,
but
you
know
it's
all
like
this
stuff
is
all
community.
A
A
Couple
things
and
follow
up
here
regarding
debugging
in
the
local
languages
by
Christiaan.
Let's
take
a
look
at
that
issue.
Really
quick!
Just
share
that
with
everybody
else,
so
you
can
see
what
we're
looking
at
here.
Nope!
That's,
not
right!
That
issue
cannot
use
debug
locale
when
in
write
manifest.
A
A
Patrick
create
a
button
to
update
all
the
projects.
Yes,
I
need
a
mean.
We
need
the
Big
Easy
button,
SPF
X
easy
upgrade
I'll
put
that
on
their
roadmap,
cool
all
right.
Other
questions
that
are
posted
here
so
I
think
we're
gonna
go
ahead
and
wrap
it
up.
Please
don't
forget:
we've
got
another
call
on
July
18th,
twenty
eight
twenty
nineteen,
twenty
eighteen
I'm
going
back
in
time.
We
got
another
call
on
July,
18th
2019.
A
Please
check
the
SharePoint
docs
for
the
invite
link
for
that.
If
you
come
over
here
again
to
the
SharePoint
Docs
go
to
community
over
here
on
the
summer
camp
calls
that
will
be.
The
second
call
you
see
right
here
if
you've
got
an
idea
for
a
demo.
Let
me
have
it
send
something
to
me:
I'd
love.
We
can.
We
can
cut
it
down
a
little
bit
if
you
want
to
have
a
discussion
on
something
please
jump
in
and
do
that
as
well.
A
I,
don't
want
to
repeat
the
same
stuff
we
did
at
the
beginning
of
the
call.
I
will
but
I
want
to
repeat
the
same
stuff.
We
did
at
the
beginning
of
the
call.
There's
a
lot
of
stuff
that
I'd
love
to
I
love
the
demo
as
well
I'm
happy
to
do
too,
but
let's
see
what
everybody
else
is
interested
in
doing
best
way
to
do
that,
get
in
touch
with
us
get
in
touch
with
me.
A
I'm
on
Twitter,
just
at
Andrew
call
send
me
a
message
and
or
send
me
an
email
Andrew
at
Boitano,
CIO
and
I'm
happy
to
go
through
and
help
arrange
and
doing
a
demo
or
to
try
and
try
and
cap
it
around
two
demos
and
then
so
we
have
time
for
Q&A
and
stuff.
So
for
those
of
you
who
are
in
the
United
States
happy
fourth
of
July
this
weekend
stay
safe
and
for
everybody
else
in
the
world.