►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 22nd of November. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
Demos:
- Kemal Sinanagic – PnPjs Site Designs and Site Scripts
- Anoop Tatti (Content and Code) - Convert to PDF and Copy Classic Link SPFx extensions
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group
bi-weekly
sync:
it
is
November
22nd
Thanksgiving
here
in
the
States
and
it's
a
normal
day,
not
in
the
States,
so
welcome
everybody
and
glad
you
all
can
make
it
so.
We've
got
Oh.
Turkey
attack
gobble
gobble,
gobble
gobble
I.
A
Was
gonna
do
sound
effects,
but
I
thought
that
might
be
too
much
so
as
we
get
started
on
the
call,
we
always
like
to
discuss
what
the
call
is
about
for
folks
that
might
be
new
to
the
call
or
new
to
the
recordings.
This
is
part
of
the
larger
SharePoint
patterns
and
practices
program
where
we
have
broken
out.
These
special
interest
group
calls
so
that
we
can
have
a
little
bit
deeper
focus
on
some
certain
topic
areas.
This
one.
A
It's
focused
around
client
side,
development
things
which
will
go
down
that
list
here
in
a
second
and
then
we
have
a
second
call
ever
on
the
other
week.
So
this
calls
every
other
week.
There
was
another
call
on
the
weeks
this
call
doesn't
fall
on.
Hopefully
that
makes
sense
where
we
in
that
one
excuse
me
dive
into
a
little
bit
of
PowerShell
and
see
some
development
and
manage
code
development,
so
different,
more
of
the
hesitates,
call
it
classic
SharePoint
development,
but
not
client-side
development
on
the
other
call.
A
So
this
call
is
really
focused
around
updates
on
SharePoint
framework
and
associated
development
patterns.
The
PMP
jeaious
libraries
office,
365
CLI,
the
SPF
X,
reusable
controls,
as
well
as
the
SPF
X
yeoman
generator,
which
might
still
be
new
to
some
of
the
folks
on
the
call
and
I
would
encourage
you
to
check
out
if
you
haven't
our
last
call
from
November
8,
where
Stephan,
who
started
the
yeoman
generator
project,
actually
did
a
great
demo
and
explanation
here
on.
A
This
call
so
go
back
and
check
that
out
a
really
cool
thing,
what
that
is
as
an
extension
of
the
sharepoint
framework,
yeoman
generator
so
you're,
getting
all
the
same
back-end
stuff,
all
the
same
sharepoint
framework
functionality,
but
you
have
a
few
more
choices
now,
when
you're
setting
up
your
project,
things
like
using
angular
elements,
adding
the
PM
pjs
libraries
in
by
default.
Things
like
that,
so
a
very
cool
tool,
really
nice
extension
of
what
sharepoint
framework
gives
you
out-of-the-box
so
do
check
that
out.
A
Client-Side
related
stuff-
if
you
will
so
two
links
down
there
at
the
bottom,
SP
PNP
community
will
take
you
to
the
Microsoft
tech
community,
specifically
the
SharePoint
section
of
the
tech
community.
There
that's
a
great
place
to
ask
general
questions
around
SharePoint
development,
whether
it's
client-side
or
not
fantastic
place
for
things
like.
How
would
you
architect,
how
would
you
design
you
know
I
can't
get
this
to
work.
A
What
feature
would
you
use
to
do
this
or
that
does
it
really
don't
pertain
to
any
specific
library
or
aren't
really
a
bug
in
anything
or
more
just
kind
of
a
question
on
how
to
do
something?
Tech
community
is
a
great
place
for
those
kind
of
questions
and
then
the
second
link
there,
AKMs
SP
dev
Doc's,
will
take
you
to
the
SharePoint
developer
documentation,
so
that
will
include
the
documentation
for
SharePoint
framework.
A
So
if
you're
new
to
SharePoint
framework
that'll
give
you
all
of
the
getting
started
guides
the
nice
little
tutorials
to
walk
through
I
know,
that's
how
I
got
started
and
that's
where
I
still
go
and
I
have
to
do
a
web
part
or
something
and
forget
exactly
a
step
in
the
process,
definitely
check
those
out
but
as
well.
The
documentation
is
there
for
managed
code
solutions,
see
some
solutions.
All
of
that
sort
of
stuff
will
be
there
all
our
developer.
Documentation
is
all
moving
to
that
location.
A
If
you
see
gaps,
please
let
us
know
please
report
those.
We
will
do
our
best.
Unfortunately
right
this
second
documentation
is
losing
out
to
some
other
priorities,
as
it
often
does.
But
still
let
us
know
if
you
see
a
gap
and
that
puts
it
on
the
backlog
make
sure
we
won't
forget.
It's
been
reported
we'll
check
that
out,
but
do
give
us
a
bit
of
time
on
that
as
we
are
working
as
we've
talked
about
before
on
our
plan
to
catch
up
on
sort
of
the
overall
SharePoint
framework
issues
list.
A
A
So
a
tactic,
a
capability,
a
technique,
it's
the
word
I'm
looking
for
a
technique
to
make
that
work
so
definitely
check
that
out
and
then
should
have
a
little
bit
of
time
here
for
Q&A
at
the
end.
So
moving
right
along
before
we
get
started,
do
always
like
to
discuss
for
folks
looking
to
get
more
involved
with
the
patterns
and
practices
stuff.
The
first
two
boxes,
their
demo,
a
SharePoint
framework
solution,
demo
any
of
the
at
P
and
P
stuff.
So
that
could
be
the
CLI,
the
PJs,
the
yeoman
generator.
A
The
reusable
controls,
any
of
that
stuff,
would
love
to
see
demos
inside
or
outside
of
SharePoint
framework
and
really,
as
I've
said
and
y'all
are
probably
tired
of
hearing
me
say
it,
but
I
think
the
demos
are
really
one
of
the
more
valuable
parts
of
these
calls
because
I
know
I
always
learned
something
new.
We
get
a
chance
to
see
great
new
stuff
that
all
of
you
out
there
in
the
community
is
working
on,
but
as
well
for
those
of
you
out
in
the
community.
A
It
gets
you
a
little
bit
of
visibility
into
some
of
the
cool
work
that
you're
doing,
which
I
think
is
always
rewarding.
At
least
it
is
for
me,
when
I
get
to
kind
of
show
off
some
of
the
stuff
I've
done,
because
I
know
often
we
we
sort
of
work
on
our
little.
You
know
bubbles
and
we're
doing
our
are
things
we
don't
really.
You
know,
get
to
show
off
the
cool
stuff
we're
doing
to
folks
that
might
appreciate
it
as
much
as
we
do
so.
These
calls
great
opportunity
to
do
that.
A
If
you'd
like
to
demo,
please
reach
out
to
myself
or
visa,
reaching
out
on
Twitter,
is
a
great
way
to
get
in
touch
with
us.
Do
you
reach
out
to
us
we'd
love
to
get
you
signed
up
to
demo
on
a
call
just
a
note?
We
might
not
be
able
to
get
you
on,
for
example,
immediately.
The
next
call
on
the
schedule,
but
we
will
get
you
scheduled.
Please
do
reach
out
love-love-love
to
see
the
demos
from
everybody
and
really
appreciate
everybody
taking
the
time
to
put
those
together
and
present
the
other
two
boxes
there.
A
So
you
can
always
contribute
on
github
across
all
of
our
projects,
so
any
of
the
stuff.
We
appreciate
your
issues,
you
might
report,
we
don't
appreciate
having
issues,
but
we
appreciate
you
telling
us
about
them,
so
we
can
get
them
fixed
and
then
as
well.
We
always
love
to
have
those
pull
requests
from
the
community,
we're
starting
to
see
a
whole
lot
more
activity.
The
last
I'd
say
two
months
has
been
really
fantastic:
we're
seeing
a
bunch
of
new
folks
show
up
and
contribute
to
the
various
things
so
across
the
suite
of
components.
A
So
love
to
see
that
really
appreciate
those
contributions
and
thank
you
to
everybody
that
has
contributed
to
all
of
the
work
we're
doing.
It
really
benefits
all
of
us
in
the
community
and
helps
us
in
our
SharePoint
development
journey
and
then,
finally,
you
can
always
provide
feedback
so
to
feedback,
not
necessarily
an
issue
but
feedback
just
general
how
things
are
going.
What
do
you
think
about
these
calls?
What
do
you
think
about
the
samples,
the
demos,
those
sorts
of
things?
A
What
kind
of
things
would
you
like
to
see
more
of
or
less
of
really
always
appreciate
that
feedback,
that
feedback
really
drives
what
we
do
and
again
I
do
like
to
say:
if
you
don't
see
immediate
change,
when
you
give
us
a
piece
of
feedback,
it's
not
that
we've
ignored
it.
It's
that
sometimes
change
takes
a
little
bit
of
time,
so
trust
that
we've
gotten
your
feedback
received.
It
we've
discussed
it
as
a
team
and
we'll
definitely
work
to
change
things
as
much
as
we
can.
A
One
example
of
that
is,
we've
been
asking
folks
if
we're
having
too
many
calls.
We
had
a
survey
about
that,
not
sure
if
the
survey
is
mentioned
in
this
deck,
but
we
talked
about
it
on
the
monthly
call.
We've
already
got
a
bunch
of
great
responses
on
that
so
feedback.
There,
we've
read
through
that.
We'll
continue
to
read
through
that
and
process
that,
but
the
general
general
consensus
seems
to
be
around
no.
A
We
do
not
have
too
many
calls
so
great,
but
really
appreciate
that,
and
that
feedback
really
helps
us
drive
the
value
of
what
we
do
in
P
and
P
for
all
of
you
out
there
in
the
community,
and
so
with
that
I
will
hand
things
over
to
Oh
No
one
more
slide.
So
this
is
what
I
was
just
talking
about:
I
jumped
the
gun.
Are
we
having
too
many
calls?
So
we
have
had
this
discussion
starting
last
week.
This
idea
of
are
we
having
too
many
calls?
A
We've
got
the
bi-weekly
calls
and
we
have
a
monthly
call
as
well
then,
as
a
lot
of
the
videos
and
other
recordings
we
put
out
directly
to
YouTube.
So
are
we
doing
too
many
things?
Are
we
having
too
many
calls
would
really
appreciate.
Folks,
if
you
have
the
time,
give
us
some
feedback
there
on
SPF
called
feedback.
Akms
SPF
call
feedback,
love
to
hear
from
folks
and
again
really
appreciate
everybody
who's
already.
A
B
Thank
you
and
on
the
call
survey
we
will
be
running
that,
probably
for
a
few
weeks
right
now.
It
seems
to
be
that
everybody's
saying
that
we
should
not
change
anything,
that
things
are
looking
insane
acute,
but
there
is
a
freeform
text,
input
box
there
as
well,
so
feel
free
to
give
us
any
other
feedback
we
dated
on
the
PNP
or
something
that's
missing
or
quality
or
or
whatever
it
should
be
done.
So
let
us
know
so
that
we
will
able
to
address
any
concerns,
while
you
might
have
now.
B
Thank
you
rob
for
your
input
on
that
one.
So,
on
the
SharePoint
framework,
a
small
update
on
the
engineering
side
before
we
go
back
on
the
open
source
projects
and
then
the
live
demos
from
a
noob
and
Kimmel.
We
did
a
tech
check
earlier.
Patrick
already
explained
what
is
the
docs
environment,
so
I'm
not
going
to
repeat
that
one
here,
all
the
issues
environment
we
just
Tuesday.
We
went
half
of
our
pending
issues
true,
and
we
will
continue
to
react
these
more
often
in
the
future.
B
To
be
honest,
next
week,
a
lot
of
the
teams
team
engineering
teams
will
be
in
the
European
SharePoint
conference
in
Copenhagen.
So
that
means
that
next
week
we
will
not
catch
at
least
pending
issues.
But
if
there's
any
critical
things,
we
have
a
support,
engineer
looking
in
the
DOS
and
they
were
being
engineering
as
needed.
So,
okay,
now
quickly,
update
on
this
I
didn't
actually
update
the
percentage
percentages
in
the
lower
section,
but
just
been
pointing
the
fact
that
the
growth
seems
to
be
continuing
being
insanely
good.
So
we
still
do
not
have
any
predictions.
B
Even
while
we
will
be
within
a
half
a
year,
because
we
can't
predict
the
growth
on
on
the
third
party
or
a
custom,
SP
affects
use
it
in
in
the
cloud.
That's
because
the
adoption
is
growing
so
fast
that
it's
it's
unheard
of,
and
this
is
by
far
the
fastest,
adapt
that
customization
model
in
office
365
and
we're
seeing
a
lot
of
interest
on
all
of
the
different
services.
B
So
Microsoft
teams,
people
were
super
excited
on
getting
SharePoint
framework
as
the
platform
for
Microsoft
team,
snaps
and
all
and
and
other
services
are
looking
into
doing
the
same,
because
clearly
community
is
embracing
SharePoint
framework
and
really
wants
to
use
that
that
industry
standard
way
of
customizing
SharePoint,
and
so
it
makes
perfect
sense.
So,
if
you're
still
wondering
on
hey,
should
I
do
SharePoint
add-ins
or
should
I
do
a
form
solution,
so
sandbox
solutions
and
don't
do
that,
concentrate
on
SharePoint
framework.
B
That
is
where
the
future
of
SharePoint
is
absolutely
a
open
framework
where
parts
working
of
classic
pages
and
publishing
bases
as
an
example
and
also
in
the
modern
experience
is
so
even
though
you
would
be
in
a
classic
offers.
Insights,
you
can
still
use
a
upon
framework,
a
good
thing
to
remember
now,
a
few
things.
What
has
happened
since
our
last
goal
related
on
SharePoint
framework.
So,
first
of
all,
it
was
like
two
hours
after
our
previous
and
bi-weekly
upon
framework
all
we
actually
relate
SharePoint
framework
1.7.
B
So
now
it's
two
weeks
away
from
from
that
release
moment.
Basically,
the
main
things
here
are
the
general
availability
for
thank
you
for
need
more
sea
level
and
general
availability
for
dynamic
data,
which
is
basically
sharing
compa
data
between
them
components
and
also
SharePoint
2019
support
in
a
yeoman
generator
and
then
a
lot
of
preview
capabilities.
So
preview
basically
means
that
they
do
work
in
a
target
release
talents,
but
they
do
not.
We
do
not
support
them
yet
in
the
production,
because
it
might
be
that
we're
changing
the
function.
B
Now
that
is
still
based
on
your
input
and
although
everybody's
asking
then
okay,
so
when
will
do
teams
tap
bg8
and
when
will
do
the
domain
eyes
right,
webparts,
b88
and
technically.
To
be
honest,
we
don't
know
why
don't
we
know
well,
because
it's
dependent
on
what
kind
of
feedback
you're
telling
us
based
on
the
issue
list
with
us
in
the
SPF
dog.
So
if
you
find
these
things
useful
and
awesome
and
there's
no
issues,
everything
just
magically
worked
with
the
first
one
and
they
will
actually
go
much
faster
GA.
B
Then
then,
if
we're
running
into
issues
or
we
find
technical
challenges
behind
of
the
scenes,
that
impacts
our
timing.
But
that's
how
the
HR
service
development
works.
We
have
no
clue
when,
when
these
things
would
be
GA
to
lg8,
but
clearly
it
doesn't
happen
by
end
of
this
year,
because
now
we're
already
at
the
holiday
season
and
then
when
we
come
back
from
the
holidays
and
we
are
collecting
the
feedback
and
start
modifying
based
on
the
feedback
and
then
we'll
finalize
them
to
be
g8
at
some
point.
B
So
that
gives
you
some
sort
of
a
hints
potentially
where
we
will
land
on
those
and
GA
now
anyway,
related
on
that
one.
So
just
making
sure
that
everybody
is
aware
of
all
of
these
assets
and
resources
which
we
have
released.
We
resist
recently
we
release
and
release.
Quite
a
few
documents
related
on
the
new
cable
is.
B
There
is,
for
example,
are
really
nice
detailed,
step-by-step
guidance
on
how
to
built
she
Microsoft
aims
tabs
with
SharePoint
framework
framework,
the
serpent
frameworks,
yeoman
generator,
and
this
is
in
both
reading
and
also
in
video
format
and
basically
you'll
get
a
simplified.
The
web
part,
which
is
aware,
is
it
actually
a
web
part
or
is
it
Microsoft
themes
tab
in?
In
my
personal,
let's
say:
how
do
we
position?
B
This
is
that
you
use
the
SharePoint
framework,
the
built
one
solution
and
then
your
surface,
the
same
solution
in
both
Microsoft
themes
and
also
as
a
SharePoint
framework
web
part
kind
of
related
on
this
one
and
just
letting
you
know
as
well
and
so
the
we
just
released
this
one.
Was
it
actually
earlier
today
or
did
I
push
it
out
yesterday?
I
can't
remember
time
flies
so
fast,
but
the
leads
lob
example
which
we
actually.
This
is
the
original
sample,
which
we
first
demonstrated
in
SPC
2018,
North
America
in
May.
B
In
the
for
first
time,
showing
that
hey,
you
could
actually
surface
your
same
lob
line
of
business
application,
either
in
SharePoint
or
in
the
Mike's
of
teams.
This
solution
has
provided
has
been
provided
to
you
as
a
sample
now
so
source
code
and
everything
else
is
available
for
you
in
the
SPF
solution
repository.
So
you
go.
There's
lusts
and
master
plans
for
a
solutions.
Folder
contains
leads
elope,
a
solution.
B
Folder
you
pull
that
one
down
you
run
npm
install
and
then
you
can
actually
test
and
see
how
the
things
are
working
properly
in
your
environment
and
obviously
the
reason
why
we
want
you
to
get
access
on
this
one
is
that
potentially,
you
might
want
to
use
this
as
a
demo,
if
you're
an
MVP
or
a
percent
during
conferences
and
so
on.
So
you
can
easily
get
access
on
the
same
demos,
us
what
we've
been
using.
B
We
will
be
as
an
example
using
this
one
as
one
of
the
demos
for
ESP
SPC,
but
why
not
actually
give
you
access
on
these
things
as
well,
so
cool,
that's
now
available
for
everybody
as
well
now
and
it's
pretty
polished.
So
one
note
maybe
on
this
one,
so
it
is
missing
the
details:
how
to
set
up
the
asha
function
for
now,
because
I
run
out
of
time
on
writing
all
of
those
technical
details.
B
So,
but
there
is
a
demo
mode
in
this
wet
part,
and
by
default
is
in
these
in
the
demo
mode,
where
it's
not
actually
executing
the
asha
function,
functionality
it
is
just
generating
the
demo
data
inside
of
it.
So
it's
basically,
I
hard-coded
inside
of
the
report,
but
it
demonstrates
the
story,
so
you
can
actually
use
this
one
really
easily
for
your
demos
as
well.
B
Certain
findings
which
we've
been
running
into
nothing
critical
though,
but
we're
still
debating,
will
the
1.71
happen
or
will
we
actually
push
1.8
as
the
next
one
at
1.8
will
be
coming
out,
then
I
would
say
next
quarter
and
next
year,
so
I
would
say
late,
potentially
late.
First
quarter
next
year
from
a
timing
perspective
and
then
at
that
point
some
of
the
capabilities
might
be
might
be
available
in
GA.
B
Some
might
be
delayed
until
the
next
release,
we'll
see
where
we
are
at
that
point,
but
really
the
priorities
and
big
themes
for
SharePoint
a
platform
right
now
from
this
moment
forward.
It's
getting
obvious
that
the
dev
preview
capabilities
out
and
then
I,
say
organization.
We
are
prioritizing
API
and
performance
optimization,
and
this
is
a
big
theme
for
us
as
well,
because
the
service,
the
use
it
is
growing
so
fast
and
there
has
been
some
performers
chance
this
year
in
there.
So
we're
really
concentrating
on
that
one.
B
B
There
was
an
assumption
that
it
could
have
been
actually
slightly
more
easier
than
the
last
finding.
So
that's
slightly
delaying
that,
but
we
were
still
looking
into
making
that
a
scenario
happen.
It
will
not
have
a
licensing
story,
but
we
will
give
you
a
capability
of
pushing
your
shape
and
framework
solution
to
the
SharePoint
store
one
way
or
another,
and
then
it's
up
to
you.
How
do
you
implement
the
licensing
or
those
web
parts
and
we'll
give
you
guidance
on
that?
But
we're
not
gonna
actually
take
any
cuts
on
on
those
solutions.
B
That's
that's
pretty
much
the
direction
where
we
are
heading
and
to
be
fair
subject
to
change,
so
there
might
be
some
last-minute
changes
and
done
and
then
we're
exploring
options
on
using
SharePoint
framework
with
other
services,
and
that
would
already
mean
that
it's
will
no
longer
be
a
SharePoint
framework.
It
will
be
renamed
to
be.
Let's
say
officer.
Is
this
2-5
framework,
or
am
I
soft
racist
if
I
framework
now.
B
A
Great
thanks
so
quick
updates
across
the
pnp
libraries,
so
for
the
PJs
client-side
components
we
did
just
release
on
November
16th
one
to
six
and
the
reason
for
that
kind
of
surprise
release
was
some
folks
are
working
on
some
stuff
for
the
European
SharePoint
conference
and
needed
a
couple
of
things
added.
So
it
seemed
like
a
good
opportunity
to
slip
out
a
release
for
folks
and
get
some
of
the
great
stuff
and
again,
while
most
of
this
came
from
folks
in
the
community,
which
is
fantastic.
So
thank
you
to
everybody
there.
A
So
some
new
stuff
in
the
term
store
getting
terms
by
ID
list.
I'm.
Sorry
item
now
has
a
parent
list
property.
You
can
now
sets
easily
set
item
metadata
fields
and
multi
fields.
There's
a
couple
of
helper
methods
for
that.
You
can
set
the
view
XML
some
search
improvements,
the
ability
to
create
modern
communication
sites
added
some
update
and
delete
methods
to
user.
A
That
was
actually
in
graph
in
the
graph
library
added
some
documentation,
and
then
this
is
something
we've
gotten
feedback
on
in
the
past,
so
try
to
give
some
better
error,
messaging
or
HTTP
errors
that
are
coming
out
of
the
PM
pjs
request
pipelines.
So
that
should
now
have
much
more
detail
in
the
actual
error
response
you
get
back
in
the
message
of
that
error,
object
itself,
so
great
stuff.
Thank
you
to
everybody
in
the
community.
Again
most
of
these
updates
were
from
folks
in
the
community.
So
really
appreciate
that
appreciate
everybody's
hard
work.
A
There,
too
links
down
there
at
the
bottom
or
one
link
down
there.
The
bong
excuse
me,
the
PNP,
github
io
PJs
takes
you
to
the
PNP
Jay
s,
library,
documentation
and
that's
a
great
place
to
get
started.
Please
let
us
know
I
know
there's
gaps
there.
Please
let
us
know
if
you
see
a
gap
or
some
missing
documentation,
we'll
do
our
best
to
get
that
updated.
We
of
course,
also
accept
full
requests
for
documentation.
So
if
you
have
a
few
moments
and
want
to
update
some
Doc's,
always
appreciate
that
as
well
p.m.
A
PJs,
a
hashtag
there
on
Twitter,
you
can
follow
me
at
mediocre,
bowler
on
Twitter
I,
pretty
much
just
post
updates
around
P
and
PJs,
and
so
you
know
not
a
lot
of
spam.
If
you
want
to
follow
me
on
that
stuff.
So
again,
thanks
to
everybody
in
the
community
contributing
to
P
&
PJs,
it's
really
phenomenal.
A
So
that's
going
to
be
for
version
1.10,
managing
web
hooks
list,
content
types,
uploading,
files
across
platforms,
PNP,
starter
kit,
setup
script
and
then
more
commands,
of
course,
always
looking
for
your
feedback
and
comments
on
what
can
help
there
or
as
always,
you
can
contribute
to
the
CLI.
Cli
is
actually
a
great
place
to
get
started
if
you
haven't
contributed
contributed
before
because
each
command
is
really
atomic.
So
you
can
work
just
sort
of
on
that
command
without
having
to
sort
of
go
across
the
entire
library
and
check
things
out.
A
So
a
really
great
way
to
get
involved
and
we've
seen
a
lot
of
great
contributions
from
the
community
in
the
CLI
as
well.
Always
you
can
install
the
latest
versions
using
the
install
you
install
that
globally,
with
the
dash
G
flag
and
then
hashtag
office,
365
CLI
on
Twitter,
there's
a
git
er
channel
there,
and
then
there
are
Doc's
as
well
on
the
AKMs
35
CLI,
so
really
check
that
out.
A
If
you
haven't
used
that
and
are
unable
to
use,
the
PowerShell
gives
you
a
great
option
for
cross-platform,
using
the
command
line
to
manipulate
your
SharePoint
farm
and
take
care
of
a
lot
of
common
asks
so
on
the
reusable
controls.
So
these
are
SPF
x4,
usable
controls
based
on
react.
So
if
you
haven't
checked
these
out,
please
do
there's
two
sets
of
controls.
The
first
controls
are
property
controls.
Those
are
currently
at
version,
1.12.
Those
are
for
the
property
pane.
A
So
when
your
web
part
goes
into
edit
mode,
you've
got
that
property
pain
and
those
property
controls
are
a
bunch
of
very
helpful
picker
controls,
so
user
Pickers
list,
Pickers,
color,
Pickers,
taxonomy,
Pickers,
there's
a
bunch
of
them
and
then
the
react,
content
controls
or
a
version
110
and
those
are
more
for
the
body
of
your
web
part
or
as
well
your
application
customizer.
But
those
really
help.
You
quickly
write
your
web
parts
without
having
to
create
a
lot
of
these
controls
yourself.
Save
you
a
lot
of
time
and
then
as
well.
A
They're
also
styled
with
the
office
UI
fabric
so
that
you
are
you're
able
to
blend
in
and
have
that
nice
out-of-the-box
look
with
your
webparts,
so
really
fantastic
controls.
Here.
Elio
has
been
doing
a
lot
of
that
work
again
with
a
lot
of
great
contributions
from
the
community,
so
love
to
see
that
and
if
you
could
save
some
time,
it's
always
worthwhile
to
check
those
out
and
save
some
time.
The
most
used
controls
are
the
place
order,
control
the
webpart
title,
control,
the
people,
picker
control
and
then
as
well.
A
We've
got
some
new
stuff
in
there.
The
list
item,
picker,
the
property,
pane
property,
pane
property,
editor
control
and
the
property
pane
web
part.
Information
control
are
some
recent
additions
or
updates
in
the
library
to
links
down
at
the
bottom
to
the
documentation
for
the
react,
controls
and
the
property
controls.
So
you
can
check
those
out
and
then,
like
I
said,
if
you
haven't
used,
the
control
is
a
really
great
way
to
jumpstart
your
SharePoint
framework
development
and
get
a
lot
of
fantastic
functionality
right
out
of
the
box
and
then
the
community
yeoman
generator.
A
So
looking
at
the
SP
FX
generator
again,
this
is
something
I've
talked
about
a
couple
times
on
the
call
check
this
out.
If
you
have
a
new
version,
1.5
is
out
so
it's
upgraded,
the
SharePoint
to
1.7
so
you're,
actually
creating
a
SharePoint
1.7
project
update
test
definitions,
updated
the
on-premises
support
for
2019,
as
well
as
some
additional
tests,
and
then
it's
the
domain,
isolated
option
added,
that's
out
of
the
1.7
capabilities
and
then
package
update
checker
has
been
added
as
well,
so
installing
the
latest
version
from
NPM.
You
can
always
do
that
again.
A
This
is
a
global
install
using
the
GE
flag.
You
can
get
more
information
down
there
at
the
link,
generator
SPF
X-
and
if
you
haven't
checked
this
out,
please
do
and
then
up
and
of
course
this
is
also
accepting
contributions.
So
if
you
want
to
do
pull
requests
or
have
issues,
of
course,
please
do
report
those
so
great
work.
Everybody
Stephan
Stephan
is
leading
the
effort
there
and
again
with
lots
of
great
contributions
from
folks
out
there
in
the
community.
A
C
Internet
got
a
I,
got
a
parsing
in
it.
Yeah
I'll,
just
wait,
maybe
or
I
can
already
do
my
introduction.
So
so
hello,
everyone,
my
name,
is
Kamal
and
I'm.
A
SharePoint
/
office,
365
consultant
take
a
technical
consultant
from
Belgium
and
I
work
for
20
great
I've,
been
using
the
paint
Bay
libraries
since
I've
started
working,
which
was
around
2015
and
specifically
the
pimpy
core
back
then,
which
was
very
useful
for
provisioning
stuff.
C
The
templating
engine
is
awesome,
so
this
is
also
why
I've
had
some
interests
with
side,
scripts
and
size
designs,
which
are
basically
a
new
way
to
provision
our
assets
on
modern
sites.
I
assume
everyone
is
familiar
with
them,
but
I'll
just
explain
the
basics,
your
site
designs
and
you
have
side
scripts.
C
So
some
people
confuse
it
too,
but
basically
it's
very
simple.
Your
site
decides
you
can
see
them
as
your
template
and
the
side
scripts
are
is
basically
your
JSON
schema,
which
holds
your
provisioning
data.
You
can
think
of
it.
If
you
think
about
baby
court
templating
there
that
that
would
be
your
XML
file,
so
yeah.
C
C
Let
us
run
for
a
second
and
then
we'll
come
the
first
step
which
will
create
our
site
scripts
to
start
off
with.
So
obviously,
we
need
a
side
script
which
will
later
add
to
a
site
design,
which
is
a
schema
we
can
generate,
which
is
out
of
the
scope
for
this
discussion.
There
are
tools
and
I'll
show
you
later
how
you
can
use
these
tools
to
easily
create
such
schema.
So
basically,
what
we're
doing
here
is
creating
a.
C
C
Let
that
run-
and
we
check
out
this
object
when
it
contains
we'll
see
it
has
an
ID,
and
our
title
is
in
here,
so
that
that's
a
good
thing.
Let's
continue.
The
next
step
is
we'll
create
a
site
design
using
this
site
script
as
one
one
of
one
of
the
IDS
we
just
created
as
a
side
script
inside
of
it.
He
provisioned
this
and
we'll
make
sure
we
provision
this
on
a
team
site,
so
that
we
pass
on
here
is
currently
as
far
as
I
know
only
limited
to
these
two
options.
C
So
once
once
we've
created
our
site
design,
you
can
see
all
the
parameters.
We
can
see
that
this
is
not
a
default
site
design.
We
can
see
here
that
I've
misspelled
the
title
which
will
correct
in
a
second
so
yeah
you
have.
You
have
all
this
nicely
typed
object,
which
you
can
use
with
your
intelligence,
for
example,
yeah
check
it
out.
So
let's
correct
our
title:
first
being
vgs,.
C
So
if
we
now
look
at
it
we'll
see
our
title
is
updated,
so
it's
just
an
example
to
show
you
how
the
update
function
works.
Next,
another
function
we
can
use
is
you
can
limit
your
site
designs
to
only
be
visible
or
viewable
to
a
certain
group
or
users,
and
we
have
functions
for
this
as
well.
So
it's
pretty
easy
to
use.
You
can
pass
a
group
or
an
array
of
groups
or
users
to
limit
your
amount
of
user
that
can
view
the
site
design
when
creating
them.
So
let's
do
that.
C
And
we'll
see
in
our
rights
object,
which
contains
our
permissions,
we
can
see
that
the
administrator
is
the
only
one
that
currently
can
feel
to
to
create
these
sight
designs
and
we'll
make
sure
we
remove
that.
So,
if
you
want
to
remove
all
the
rights,
the
easiest
thing
to
do
this
is
to
basically
fetch
all
the
rights
which
I've
just
done
and
then
map
all
the
user
principles
to
an
array
and
and
pass
that
again
in
a
function
to
revoke
these
his
rights.
Let's
do
that.
C
We
should
see
that
our
rights
objects
should
have
a
language
serial,
which
means
we
don't
have
any
explicit
rights
on
our
side
designs,
all
right.
So
that's
quite
technical
and
boring.
Let's
try
to
apply
our
our
site,
design
on
only
if
any
existing
team
site,
so
I
have
one
here,
I
created
if
I
go
to
the
site.
Contents,
we'll
see
that
we
don't
have
a
pimp,
a
J's
library.
If
you
remember,
we
had
our
site
script,
which
is
this,
which
is
basically
just
very
simple,
so
we
create
the
list
and
if
we
run
this.
C
And
then
we
refresh
our
site,
we
should
see
a
PPG's
list,
so
this
is
just
a
way
to
make
it
possible
easily
using
the
pimp,
a
J's
library.
If
we
continue
the
next
step
will
do-
and
this
is
an
also
tool.
I
will
show
you
right
now
we'll
try
to
update
our
side
script
and
the
thing
is
we'll
use
of
yeah
a
little
more
complex
definition
or
schema
and
I
did
not
come
up
with
this.
C
I
just
use
this
very
out
inside
which
I'll
just
show
you
very
quickly
and
it
is
designed
or
written
by
mokopuna
maki.
If
I
pronounced
it
correctly.
Excuse
me
if
I'm,
not
so,
basically
what
I
just
did
I
went
to
samples
and
I
picked
one
of
these,
and
this
is
the
one
I
chose
it's
a
very
awesome
tool.
You
can,
you
can
just
do
it
everything
to
a
graphical
user
interface.
So
if
you
change
something
here,
it
will
reflect
on
your
schema.
C
It's
basically
just
a
JSON
string,
so
pops
up
for
the
it
is
still
I
love
it.
So,
let's
update
our
site
script
with
this
more
advanced
script
and
we
should
note
when
I
do
this.
It
does
not
mean
that
our
that
our
site
will
be
updated,
so
the
visioning
will
not
happen.
We
didn't
trigger
anything.
We
just
updated
the
site
script,
which
is
linked
to
our
site
design.
We
have
make
tents,
so
we
need
to
provision
our
site
design
again.
So
let's
do
that.
C
C
This,
which
I'll
just
show
you
right
now.
If
you
go
to
the
documents
library
we'll
see
that
we
have
these
extra
columns
like
project
owner
delivery
date,
so
we're
sure
we
provide
the
correct
site
design,
how
that's
about
it
for
applying
your
site
designs
and
then
in
your
side,
scripts
and
managing
them.
There
are
some
interesting
things,
for
example,
if
you
load
all
your
site
scripts,
and
basically
we
only
have
one
right
now
you
can
see
our
schema
is
not
loaded.
So
it's
a
no
and
there
I'm
not
sure
why
this
is.
C
But
it's
just
the
way
the
API
is
designed.
So
to
make
sure
you
get
your
finishin,
we
need
to
use
this
function,
which
will
basically
take
the
ID
as
an
input
of
the
script
side,
script
and
load
the
content.
So
if
we
do
this,
we'll
see
that
our
metadata
has
been
filled
up
and
that
our
content
or
schema
is
available.
So
this
is
just
a
side
note
for
people
who
might
be
wondering
why
why
the
content
is
not
loading
or
the
schema,
and
this
is
also
documented
on
the
official
documentation
site
by
Microsoft.
C
C
C
Deed
that
our
provisioning
will
start
so
usually
with
it
with
the
default
team
site
template.
You
wouldn't
get
this,
so
we're
now
sure
we've
got
everything
set
and
that
it
works.
So
the
nice
thing
about
this
is
that
you
can
actually
see
that
the
things
that
have
been
updated
and
that's
about
it
if
we
call
our
site
designs
one
last
time
we'll
see
we
have
this
nice
site
design
with
a
specific
ID.
We
can
see
it's
the
default
one.
C
C
So
I
have
one
right
here,
though,
it's
it's
still
a
work
in
progress,
but
this
was
my
initial
idea
and
unfortunately,
I
was
hoping.
The
kind
of
forget
it
finished
for
for
this
presentation,
but
I
didn't
have
enough
time.
So
it's
basically
just
fetches
all
the
side
designs
and
you
have
your
site
scripts
here
and
yeah
there's
not
much
functionality.
You
can
edit
that
if
we
name
just
two,
it
should
refresh
and
update,
but
that's
about
it.
You
can
click
on
this
and
receive
the
D
of
the
site,
script.
C
C
A
D
Hello
everyone
morning
afternoon
evening,
my
name
is
a
noob
and
I'm
on
developer
content
and
code.
You
can
follow
me
on
Twitter
right
else
and
then
that's
my
my
LinkedIn.
If
you
want
as
well
today,
I
have
been
given
an
opportunity
by
Versailles
and
the
PMP
team
to
present
to
PNP
to
SPF
xx,
extensions
yeah.
That's.
D
D
Behind
developing
this
extension,
sometimes
you
would
need
the
classic
link
say
in
a
Content,
ID
forever
part
run
image
or
maybe
or
even
in
display
templates.
When
you
want
to
display
an
image
say
you,
you
have
a
list
where
you
have
to
animation.
You
want
to
display
that
using
display
template,
then
you
would
need
the
classic
thing
to
be
present
in
that
in
that
list.
So
we
have.
This
was
developed
basically
considering
all
the
classic
things
in
in
consideration.
You
just
do
a
quick
demo
of
this
one
and
then
I'll
show
you
the
code.
D
So,
as
you
can
see,
we
have
a
library
here
and
then
course
some
items
here.
So
if
I
just
select
this
this
item,
which
is
an
image
and
then
I
can
see
this
extension
come
over
here,
click
on
that
and
then
all
it
does,
it
says,
link
has
been
copied
and
you
can
press
control
V
to
use
that.
So,
if
I
just
quickly
open
up
notepad
and
then
paste
that
you
can
see
if
we've
caught
our
acrostic
link,
which
means
we
can,
we
can
use
this
any
way
we
want.
D
So
you
can
either
display
present
as
a
toast
for
the
sweet
alert
again
because
the
command
is
pretty
straightforward.
All
you
do
is
just
you
know,
pass
the
title
and
the
text
that
you
want
to
display
and
the
type
whether
it's
a
success
or,
and
things
like
that
and
if
you
are
using
toaster,
you
know
I
think
there
was
a
demo
of
closer
by
Chris
Kent
in
one
of
the
PNP
calls.
D
So
if
you
say
want
to
edit
the
properties
of
the
extension,
you
can
come
come
to
the
standpoint
extensions
list
which
is
in
the
air
catalog
site,
and
then
you
can
basically
edit
the
property
of
the
copy
classic
link
and
then,
at
the
moment,
I've
said
show
toast
alone.
But
if
I
set
that
to
yes,
then
you
know
instead
of
this
sweet
alert,
you
will
see
see
the
toaster
right.
D
D
If
you
want
to
do
some
complex
tasks
after
getting
the
stream,
then
you
can
probably
do
those
in
in
the
a
function,
but
this
whatever
I
have
done
in
this
extension,
can
be
done
of
client
as
well.
So
as
in
on
the
on
the
client
side,
no
need
to
do
a
quick
demo
of
this
one.
Let
me
kick
off
the
SEO
function.
First,.
D
Open
the
library
I've
caught
a
couple
of
documents
here.
One
is
a
word
document
and
an
Excel
document,
nice
names,
isn't
it
those
two
documents
and
click
on
convert
to
PDF
and
then
convert
PDF,
so
press
convert?
And
then
you
know,
since
I
requested.
Here's
your
function
once
what
your
function
runs:
converts
documents
to
PDF
and
upload
those
PDF
documents
back
to
this
library
and
when
I,
okay,
that
just
the
screen
is
refreshed.
You
can
see
whole
document
and
an
Excel
document,
video
formats,
just
click
on
that
word
document
and
then
yeah.
D
So,
with
respect
to
the
code
of
this
one
again,
on
the
extension
side,
it's
quite
straightforward.
All
we
are
doing
here
is
for
for
all
the
selected
items.
We
are
getting
the
names
of
the
items
that
are
selected
and
then
pushing
it
into
an
array,
and
then,
after
that,
we
pass
it
to
a
method
called
start
conversion.
That
method
essentially
constructs
the
as
your
function.
Url.
D
We
take
URL
and
then,
if
I
go
on
TS
your
function
itself,
if
we
just
drop
this
so
once
we
are
in
the
as
your
function
yeah,
we
get
all
the
details
from
the
extension
and
then
we
loop
through
all
the
items
and
then
for
for
each
item.
As
I
said,
it
needs
a
sharing,
ID
or
an
encoded
URL
to
compute
that
this
formula,
basically
we
get
the
base64
string
and
then
use
this.
You
exclamatory
and
then
some
some
other
bit
of
code,
which
includes
replacing
and
expect
that
this
this
was.
D
This
was
posted
as
an
answer
by
Michael
Swenson
and
follow
him
on
in
one
of
the
blocks
so
yeah
and
specially
to
that
as
well.
And
then,
once
we
have
that
encoded
URL,
we
need
to
pass
it
to
the
client
so
before
so
we
need
to
get
the
graph
plan.
Now.
There
are
various
ways
with
which
we
can
get
craft
line
over
here.
I
am
just
using
a
no
application,
ID
and
an
application
secret
to
took
ethics
of
client.
D
D
D
Those
those
options
include
the
format
as
PDF.
Now
there
are
a
lot
of
formats
available
to
that.
In
this
case
we
are
using
PDF,
so
we
will
get
the
PDF
stream
from
the
craft
land
and
then,
after
that,
you
can
use
again
the
craft
and
to
upload
the
document
library,
sorry
to
upload
the
documents
back
to
SharePoint,
but
I'm
using
you
know,
PNP
here,
there's
one
extension
method
called
as
root
folder
upload
file
and
then,
with
one
line
you
can
can
just
upload
the
document.
D
A
Thank
you
very
much.
That
demo
also
looks
great
because
I
still
couldn't
see
it
on
my
screen,
not
sure
what's
going
on
there,
but
thank
you
very
much
very
cool
demo,
fantastic
stuff
and
I
think
you
got
a
few
questions
there
in
the
ion
window.
If
you
have
a
chance
to
get
those
answered,
they
should
be
back
on
the
slides.
A
Theoretically,
I
see
them,
but
I'm
sharing
them.
So
I,
don't
know
if
things
are
working
or
not,
maybe
somebody
could
confirm.
Devi
can
see
them
great
awesome,
so
not
really
much
time
for
Q&A
I.
Think
we've
had
a
great
discussion,
as
always
over
there
in
IM
windows.
So
thanks
everybody
for
that.
Our
next
meeting
will
be
december
6th
for
the
SPF
x,
geneious
Sig
call
December,
6
can't
believe
we're
already
into
December.