►
From YouTube: SPFx JavaScript SIG 7th of December 2017
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
This
is
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly,
sync,
its
December
7th
2017.
This
is
Patrick
Rogers,
I'm
back
I'm,
very
excited
to
be
back
and
talking
with
all
of
you.
I
had
a
wonderful
opportunity
to
be
off
on
family
leave
for
an
extended
period,
which
is
a
fantastic
thing.
A
Microsoft,
let
me
do
it,
let's
everybody
do
not
just
me,
but
so
very
excited
to
be
back
very
excited
to
be
re-engaging
with
the
community
and
look
forward
to
this
call
and
updating
folks
on
what
we've
been
up
to
so
for
folks
that
might
be
new
to
the
call
or
watching
the
recordings
for
the
first
time.
This
is
the
sharepoint
patterns
and
practices
call.
So
it's
part
of
a
larger
program
and
the
special
interest
groups
were
formed
to
give
a
chance
for
audiences
who
are
interested
in
more
specialized
areas,
in
this
case
client-side
development.
A
We
have
another
sig
that
covers
the
c
s--
on
powershell
development
and
really
like
to
give
those
folks
an
opportunity
to
get
a
little
bit
deeper
involved
in
those
areas
of
interests
that
we
just
can't
dive
into
on.
The
monthly
community
calls
because
it's
just
too
broad
of
a
topic,
so
these
specialized
interest
groups,
their
special
interest
groups,
were
formed
and
on
this
one
we
talked
a
lot
about
the
sharepoint
framework
latest
releases
news,
new
tips
and
tricks,
as
well
as
demos,
around
sharepoint
framework
and
then
as
well.
We
talked
about
this
javascript
core
component.
A
We've
been
working
on
for
over
a
year
now,
which
is
really
exciting.
To
think
about
that.
This
is
gone
on
that
long
and
been
as
successful
as
it
has
been,
and
that's
dude
again
to
all
of
you
in
the
community
so
to
links
down
there
at
the
bottom,
AKA
MSSP,
P&P
community,
we'll
take
you
out
to
the
Microsoft
tech
community
area
for
SharePoint.
That's
a
great
place
if
you
have
general
sharepoint
development
questions,
not
just
around
client-side
development
but
around
all
kinds
of
sharepoint
development
or
even
sharepoint
administration.
B
But
the
FairPoint
Patrick
before
you
go
back
on
their
roll.
We
should
actually
have
a
specific
link
on
the
AKMs
link
for
the
spdm
Docs
issue
list,
because
we
want
to
get
those
issues
tracked
in
the
issue
list
rather
than
random
comments
in
there,
for
example
in
our
articles
and
but
that's
a
different
topic.
So
let's
update
this
light
for
the
next
one.
So.
A
Scratch
what
I
said
that
takes
you
to
the
official
SharePoint
documentation,
link
there
so
moving
right
along
into
our
agenda.
So
what
do
we
have
today?
We've
got
the
Jas
core
component
got
some
updates
to
talk
to
you
all
about
around
our
at
PMP
scope:
work
as
well
as
some
updates
for
SPP
and
PJs
SharePoint
framework
latest
news,
and
then
we've
got
some
demos
around
the
SharePoint
p.m.
PJs.
We've
added
the
ALM
API
support
to
the
last
release
and
then
as
well.
A
The
at
PNP
library
I
want
to
talk
through
what
that's
gonna
mean
and
what
our
thoughts
are
and
then
sort
of
you
know
solicit
feedback
from
everybody
about
those
directions.
Because
again
it's
a
very
it's
all
very
community
driven
so
I
want
to
ensure
that
we're
getting
the
feedback
from
folks
and
folks
are
able
to
have
their
voices
heard.
Then
we've
got
two
really
cool
demos:
Russell's
got
a
react.
Security
grid,
SharePoint
framework
web
part
and
Chris
has
an
SVG
image
web
part,
which
shows
off
a
couple
of
the
controls.
A
Client-Side
controls
so
very
cool
demos
from
those
folks,
and
then
we
should
have
a
little
bit
of
time
at
the
end
for
a
QA
but
we'll
see
in
terms
of
the
demo
time,
I
always
like
to
talk
about
the
opportunities
to
participate.
So
if
you're
new
to
the
calls
or
new
to
looking
for
a
way
to
participate,
really
invite
everyone
to
get
involved
in
the
way
they
would
most
like
so
demo
in
a
SharePoint
framework
solution.
So
that
could
be
a
web
part.
That
could
be
an
extension
that
could
be
something
else.
A
Sharepoint
framework
related
on
this
call.
So
obviously
we've
opened
this
up
to
the
community
and
look
forward
to
getting
folks
to
demo
on
this
call
contributing
on
github.
So
that's
going
to
any
of
the
repos
reporting
an
issue
providing
a
PR
to
fix
an
issue
providing
feedback
on
features.
You'd
like
to
see
things
like
that,
really
invite
folks
to
contribute,
get
involved
on
github
demo
and
SPP
and
PJs
project.
A
So
there's
a
lot
of
folks
have
done
stuff
with
SPP
and
PJs
that
may
or
may
not
be
in
SharePoint
framework,
so
either
way
invite
you
to
demo
something
related
to
that
library
and
then
finally
providing
feedback,
whether
it's
through
the
github
channel,
as
I
mentioned
earlier,
whether
it's
coming
to
these
calls
and
providing
feedback
or
whether
on
the
forums,
is
providing
feedback.
But
really
we
want
your
feedback.
We
take
your
feedback
to
heart.
We
can't
always
immediately
act
on
every
piece
of
feedback,
but
we
really
do
take
them
to
heart.
A
Read
them
internalize
them
and
look
to
see
how
we
can
shape
the
roadmap
moving
forward
based
on
the
feedback
from
all
of
you
out
there
in
the
community,
so
keep
that
great
feedback
coming
so
real,
quick
p.m.
PJs
core
component
got
a
nice
update
here
for
everybody
right
when
I
got
back,
we
released
SPP
and
PJs
3:02
that
had
some
updates
on
issues
and
feedback
from
the
community.
So
I
went
through
the
issues
list
knocked
out
a
bunch
of
that
stuff
and
then
as
well.
A
Whoops
sorry
go
back
a
slide
and
got
a
couple
of
new
features
in
there.
The
main
one
there
is
the
ALM
API,
so
we
got
those
added
I'm
gonna
show
those
a
little
bit
on.
The
call
here
in
a
second
and
I
did
want
to
talk
a
little
bit
about
the
work
continues
on
the
at
P
and
P,
and
so
I
wanted
to
sort
of
talk
about
what
this
means
and
sort
of
the
roadmap
going
forward.
Understanding.
A
We
don't
have
definite
times
at
this
point,
but
wanted
to
talk
to
you
guys
and
start
to
get
this
out
there.
So
the
idea
of
moving
to
this
at
P
and
P
scope
really
is
is
not
a
move
away
at
all
from
patterns
of
practices
or
SharePoint
or
any
of
the
work
we've
done
before.
It's
simply
a
way
to
create
a
container
for
the
Pattinson
practices
work
for
those
folks.
A
Something
or
more
likely,
you've
seen
like
at
Microsoft
slash
something
if
you're
doing
a
lot
of
SharePoint
framework
work
and
that
scope
allows
us
a
little
bit
more
freedom
to
distribute
our
packages
because
we
as
a
community
driven
effort,
can't
really
release
stuff
as
at
Microsoft,
and
because
we're
looking
at
doing
stuff
that
isn't
necessarily
always
SharePoint,
it
didn't
seem
right
to
really
be
releasing
stuff
under
at
SharePoint.
So
we
looked
at.
How
can
we
have
a
scope?
What
kind
of
you
know
container?
A
Can
we
place
our
work
in
and
we
were
lucky
enough
to
work
with
the
prior
owner
of
the
PNP
organization
that
wasn't
actually
in
use
by
them.
So
we
got
that
transferred
over
to
us,
which
is
very
exciting,
and
then
we
actually
got
the
scope
on
NPM
transferred
over
to
us
as
well.
So
we
were
able
to
create
this
container
within
which
we
can
distribute
the
work
we
all
do
together
as
a
community.
A
A
Yet
that's
you
know
we're
working
on
the
communications,
we're
working
on
the
releases
and
I'm
gonna
talk
a
little
bit
more
about
that
in
the
demo,
but
it's
very
much
building
on
the
success
of
SP,
P
and
pjs
the
growth
in
the
community
and
then
looking
ahead
at
how
we
can
grow
and
better
align
to
sort
of
the
the
community
kind
of
standards
out
there
and
what
some
of
the
other
larger
projects
are
doing.
We
very
much
looked
at
angular
what
the
that
team
has
done
as
sort
of
a
template
for
our
work.
A
I'll
talk
about
that
a
little
bit
in
the
demo.
The
aim
is
to
have
an
initial
release
by
the
end
of
this
calendar
year.
We
are
very
close
to
that.
The
coding
is
in
quotes
done
because
we
all
know
coding
is
never
truly
done,
but
V
and
we've
lost
the
presentation
there.
We
go
I
think
it's
back
for
me.
Hopefully,
it's
back
for
everybody,
but
so
working
on
the
docks
and
I'll
talk
through
that
again
on
the
demo.
A
Lots
of
docks
to
write
one
of
our
goals
is
to
have
more
documentation
for
this
release
than
we
did
for
the
prior
release.
Part
of
that
documentation
is
going
to
be
a
transition
guide
so
moving
from
SPP
and
PJs
to
the
new
libraries
and
looking
for
feedback
about
that
process,
because
we
wanna
make
sure
it's
an
easy
transition
do
want
to
ensure
that
folks
do
know.
The
SPP
mths
is
not
going
to
go
away.
We're
gonna
continue,
maintaining
it
for
six
months
from
the
release
of
the
new
libraries
and
with
that
transition
guide.
A
Hopefully,
six
months
is
enough
time
for
folks
to
get
their
projects
updated,
but
even
after
that,
six
months,
SPP
and
PJs
isn't
going
to
go
away.
We
will
continue
to
support
or
I'm
sorry
I
continue
to
accept
pull
requests
from
the
community
issues
from
the
community
and
things
like
that.
It
just
will
not
as
much
be
the
focus
of
the
core
team,
but
the
library
itself
will
live
on
in
github,
we're
not
going
to
delete
it.
The
versions
of
course,
will
remain
on
NPM,
etc.
A
So
we
we
aren't
going
to
break
anyone's
existing
stuff,
so
to
speak.
So
we'll
talk
about
that
a
little
bit
and
then
I
did
want
to
identify.
Andrew
koltakov
has
done
a
great
job
being
very
active,
a
lot
of
you
if
you've
submitted
issues
or
been
on
git
er
around
the
SPP
and
PJs
you've
probably
heard
from
him
and
then
he's
been
doing
a
great
job,
especially
while
I
was
out
of
answering
a
lot
of
questions,
and
you
know
really
just
being
involved
and
helping
out
submitting
pull,
requests
and
kind
of.
A
As
a
recognition
of
that
work
and
seeing
the
great
stuff
he's
done,
he's
gonna
be
taking
on
a
little
bit
larger
role
here
with
the
SPP
and
she
yeah
pardon
me
SPP
pjs
library
as
well
as
then,
the
the
at
P
and
P
library
is
once
we
get
those
moving,
so
he'll
be
helping
with
PRS
he'll,
be
merging
those
helping
with
issues,
and
things
like
that.
But
I
did
want
to
identify
and
thank
him
for
the
great
work
he's
done.
A
A
You
go
on
leave
for
a
while.
You
forget
how
to
use
Skype
so
bear
with
me
for
a
second
all
right,
so
I
wanted
to
talk
about
the
LM
API.
So
a
lot
of
you
I
know
this
was
talked
about
in
calls
around
this
being
added
to
the
sea,
psalm
core
components,
so
we've
now
added
that
support
to
the
SPP
and
pjs.
So
the
main
way
to
do
that
is
each
web.
A
The
web
object
now
has
a
get
app
catalog
method,
and
one
of
the
things
I'm
sure
you
guys
have
read
or
talked
about
in
the
past
is
the
app
catalog
exists
both
for
each
web
and
then
this
special
tenant
app
catalog,
which
is
really
only
differentiated
by
the
web.
You
open
that
app
catalog
on
so
get
app.
Catalog
method
called
in
this
manner,
will
get
the
catalog
for
whatever
this
current
web
is
so
fairly
straightforward.
A
You
can
also
then
chain
off.
It
hope
folks
are
fairly
familiar
with
the
api
at
this
point,
so
you
can
get
the
app
catalog
and
the
app
catalog
itself
is
a
queryable
collections.
You
can
do
selects
top
skip
things
like
that
and
that
will
give
you
all
the
apps
in
the
caddy
available
apps
in
the
catalog.
A
We've
provided
a
little
bit
of
flexibility,
so
you
can
get
any
catalog
by
passing
a
URL
in,
and
this
will
open
up
the
app
catalog
in
my
case
for
my
tenant,
app
catalog,
which
is
usually
usually
sites,
slash
app
catalog
for
your
tenant
and
that'll
get
but
I
work
for
any
site.
So
you
can
see
that
here
and
you
can
open
up.
This
is
just
another
site,
so
I
can
get
the
app
catalog
for
that
site
off
of
an
existing
web
and
then,
finally,
just
wanted
to
show
you
guys
you
can
create
a
web.
A
So
if
you
already
have
a
web
in
existence,
you
can
then
create
a
new
app
catalog
off
of
that
web.
You
could
also
pass
a
URL
directly
to
app
catalog
and
once
you
have
a
catalog,
you
can
do
things
like
get
the
app
by
ID
I'm
not
going
to
go
through
all
the
methods,
but
I
did
want
to
show
you
we
do
have
the
ALM.
Api
methods
are
documented
here
in
the
wiki,
so
you
can
go
to
the
developer
guide
and
look
at
the
ALM
API,
and
this
will
talk
about
again.
A
The
idea
of
the
tenant
app
catalog
and
the
web
app
catalog
how
to
get
the
app
catalog.
So
talking
about
what
I
just
talked
about
and
then
the
operations
you
can
perform
so
listing
the
apps,
adding
an
app
getting
an
app
and
then
those
app
actions
of
deploy
retract,
install,
upgrade,
remove,
remember
some
of
those
specifically
retract
deploy
and
remove
will
only
work
on
a
tenant
app
catalog
web.
A
A
Well,
if
I'm
just
want
to
do
graph
stuff,
why
do
I
need
all
the
SharePoint
stuff
and
then
vice
versa?
If
I
just
want
to
do
SharePoint
stuff,
why
do
I
need
the
weight
of
all
the
graph
stuff
to
also
be
in
the
library?
So
to
that
end,
this
is
our
new
repo,
and
so
you
can
actually
see
it
here:
github.com,
/p
and
P,
P
and
P.
A
A
Please,
because
I
still
have
a
lot
of
moving
pieces
and
it'll
just
be
easier
for
the
time
being,
to
be
able
to
kind
of
work
in
isolation
a
little
bit,
but
do
try
it
out
and
do
report
issues
definitely
want
to
hear
from
that.
But
so
we
broke
everything
up
into
a
bunch
of
different
packages.
So,
for
example,
logging
became
its
own
package
and
this
package
you
could
install
in
any
application.
It
has
logging
happens
to
have
no
other
dependencies.
A
So
if
you
really
like
the
way
we
did
our
logging,
you
could
install
that
in
any
application,
you're
using
and
use
that
logging
same
for
Commons.
So
if
you
like
some
of
our
shared
utilities,
you
can
install
just
the
common
package
and
then
for
the
rest
right
and
then
one
thing
we've
done
to
try
and
help
ease
the
transition.
Is
we've
created
a
package
called
P
and
PJs,
which
is
really
a
rollup
and
collection
of
all
the
packages
into
something
that
matches
closely
the
SP,
P
and
PJs
package,
so
we'll
be
rolling
that
out.
A
So
in
terms
of
the
package
structure,
each
of
these
is
identical
and
that's
on
purpose
to
make
it
sort
of
easy
to
manage,
but
also
easy
to
process
through
a
common
build
chain.
But
if
you
look
at
this,
so
we've
got
a
source
folder,
which
surprisingly
has
source
files
in
it:
a
test
folder
which
has
tests
in
it
and
then
we've
got
a
Doc's
folder.
So
this
is
a
new
kind
of
idea,
we're
introducing
that
we're
gonna
have
Doc's
that
live
next
to
the
code.
So
this
comes
from
a
piece
of
feedback.
A
I've
heard
a
lot
which
is
I
didn't
know
there
was
documentation,
I
couldn't
find
documentation
and
looking
for
a
way.
So
maybe
the
wiki
isn't
clear
enough,
isn't
easy
enough
for
folks
to
find
they
don't
see
that
right
away.
So
we've
put
the
docs
here
right
next
to
the
code
and
what
that
means
is
hopefully
one
it's
easier
to
find
and
two.
A
It's
easier
to
keep
up
to
date
because,
as
I'm
doing
a
code,
change
I
can
do
a
doc
change
right
next
to
it,
and
I
can
push
all
that
in
the
same
cool
request
and
so
that'll
become
part
of
our
contribution
guides.
If
you
are
doing
a
contribution,
please
update
or
add
to
the
docs
to
reflect
whatever
that
contribution
is,
and
that
will
benefit
the
idea
being.
That
will
benefit
all
of
us
moving
forward.
Some
have
a
better
documentation
coverage
of
the
entire
set
of
packages
and
so
the
docs.
So
we
have
a
gulp
Doc's.
A
As
you
can
see,
this
is
probably
the
prettiest
website
you're
going
to
see
today
it's
at
least
the
most
readable,
but
this
is
just
a
start
and
so
for
each
thing
we'll
have
common,
for
example,
has
its
files
again,
it's
very
pretty
and
we'll
talk
about
all
the
things
and
still
have
this
out
there
as
a
site,
so
looking
for
folks
to
help
out
with
this
and
branding
I'm
talking
to
a
couple
of
people.
But
if
anybody
out
there
has
some
some
real
design,
expertise
or
desire2learn
design
expertise.
A
This
would
be
a
great
opportunity
to
help
us
brand
this
site.
So
right
now
it's
just
very
simple:
it's
the
the
MD
file
is
translated
directly
to
HTML,
but
we'll
be
looking
to
add
to
that
get
obviously
some
formatting
some
colors
and
fonts,
and
things
around
to
make
this
really
pretty,
but
that
would
get
pushed
out
with
every
release
as
well
to
hopefully
help
with
our
documentation
coverage.
A
Another
thing
we've
done
jumping
back
here,
no
sorry
jumping
back
here
is
so
in
our
distal
durf
or
each
package.
We've
got
a
lot
of
different
files
now
and
you
might
say
Patrick.
Why
do
you
have
all
these
files
great
question?
Really?
This
is
to
support
as
many
formats
as
we
can
so
we've
got
and
I'm
looking
at
the
common
package,
but
this
would
be
the
same
across
all
of
them.
A
A
A
Excuse
me
and
then
we've
got
minified
versions
of
that
and
then
finally,
for
each
thing,
there's
gonna
be
this
giant
file
name,
so
common
es5
UMD
bundle
which
is
going
to
be
a
UMD
module.
That's
a
bundle
of
all
of
the
things
that
this
common
thing
depends
on.
So
in
Commons
case
it
depends
on
logging.
So
this
bundle
is
going
to
have
the
common
code,
as
well
as
the
logging
code,
all
bundled
together
and
that's
to
provide
folks
an
easy
way
if
you're
looking
to
you
know,
I
just
want
to
use
the
common
stuff.
A
I
want
to
use
in
the
browser
and
I
want
to
have
one
file.
Here
you
go
and
that's
gonna
be
the
same
for
the
SP
library,
the
graph
library,
etc.
There
will
still
be
one
file
you
can
grab.
That
is
a
bundle
of
all
the
functionality
you
need
just
to
make
things
work,
so
you
don't
have
to
deploy
six
eight
twelve
different
files
in
parallel,
we're
not
up
to
12
yet,
but
one
day
it
could
be
right.
A
A
So
if
we
look
at
our
package.json,
that's
going
to
go
out
with
every
package.
The
other
thing
we
tried
to
update
is
this
idea
that
there's
different
bundlers
out
there
that
might
be
more
advanced
than
sort
of
the
basic
stuff.
So
we
took
the
guidance
that
the
roll-up
folks
have
put
out
and
we
looked
at
tree
shaking
and
stuff
when
we
first
started
writing
this
and
it
just
wasn't
mature
yet,
and
so
now
it's
been
I,
don't
know
eight
months
nine
months
a
year,
so
it's
a
little
bit
more
mature.
More
folks
are
doing
it.
A
There's
better
guidance,
so
main
is
still
going
to
point
to
that
UMD
module.
So
that's
gonna
work
across
all
your
types
of
deployment,
so
your
different
browsers,
as
well
as
your
different
node
versions,
but
then
we've
added
this
module
and
this
es2015
I'm,
sorry
I,
said
2016.
So,
yes,
2015
module
version.
A
That
makes
it
very
easy
to
know
that
you've
got
all
the
libraries
in
alignment.
There's
not
going
to
be
any
confusion
about
beta
six
works
with
beta
three
or
anything
like
that.
They're
gonna
be
released
as
a
unit.
Every
time
as
we
go
out
just
wanted
to
mention
that
and
then
finally,
a
couple
of
things
I
wanted
to
show
folks.
A
A
You
know
for
folks
who
did
f5
debugging
in
Visual
Studio
code
still
able
to
do
that,
but
one
of
the
things
we
added
is
this
serve
folder
with
a
file
in
here.
So
I
can
actually
now
run
my
gulp
serve
and
it
will
serve
a
file.
That
is
this
code.
So
I
can-
and
this
is
all
watched
so
I
can
easily
before
you
kind
of,
had
to
put
stuff
into
a
script
that
are
web
part
and
bounce
back
and
forth
and
do
different
things.
It
was
a
little
bit
annoying.
A
So
this
is
hopefully
a
lot
easier
or
I
can
write
my
code
and
test
things
directly
in
the
browser
using
the
gulp
serve
by
just
adding
a
script
tag
to
a
page
and
because
of
time,
I'm
not
going
to
show
too
much
of
this.
But
the
last
thing
I
wanted
to
mention
around
the
serve.
Is
you
can
still
do
this
tag?
P
dash
dash
P
for
package
and
I
could
still
serve
it's
not
going
to
do
anything
right
because
you
have
to
say,
go.
A
A
So
inside
of
node,
you
could
supply
a
tenant,
an
app
ID
and
an
app
secret
which
I've
got
off
in
a
different
file
and
you'll
be
able
to
now
query
against
the
graph
from
node
using
this
Adel
fetch
client,
and
so
that's
done
using
setup.
So
I
think
a
lot
of
folks
that
are
familiar
with
this,
but
you
just
set
your
fetch
client
factory
to
return
a
new
Adel
fetch
client
and
you
can
query
the
graph
directly
from
node,
which
I
think
is
very
exciting.
Development
opens
up.
A
Some
new
scenarios
allows
us
to
write
tests
in
node
the
way
we
did
for
SharePoint-
and
you
know
so
that'll-
be
something
we're
developing
moving
forward,
and
this
is
just
for
node
at
this
point,
and
this
actually
relies
on
the
Adel
node
library
put
out
by
the
graph
team
under
the
hood.
So
that'll
stay
up
to
date
as
well.
A
Other
thing
I
want
to
mention
I'm,
adding
like
process
exit
to
a
lot
of
these
samples
and
debugging
stuff
that
just
makes
it
a
little
cleaner
to
exit
after
you
debug
out
of
some
things
and
then
one
of
the
thing
I
wanted
to
show
folks
because
I
think
it's
something
we
another
thing
we
talked
about
a
long
time
ago
and
we
couldn't
actually
do
it
because
of
limitations
in
typescript.
But
a
lot
of
you
might
remember,
there's
like
get
and
get
as
post
and
post
as
so.
A
And
I
think
we
are
ready
to
pass
this
over
to
visa
for
a
sharepoint
framework
update.
But
the
last
thing,
I
want
to
say
is:
thank
you.
Everybody
well
I'm
very
happy
to
be
back
just
published
a
beta,
so
do
pull
these
down,
give
them
a
try.
Give
us
the
feedback,
really
look
forward
to
hearing
from
folks
and
what
they
think
Daisy.
B
B
But
it
doesn't
mean
that
you
need
to
understand
exactly
what
Patrick
is
doing
right
now
and
to
be
honest,
the
the
neat
thing
about
the
MPTs
core
is
that
you
can
take
advantage
of
that
one
just
by
using
the
API.
You
don't
really
need
to
understand
the
ins
and
outs
of
the
library,
it's
just
a
capsule
item
to
complexity,
right,
Patrick
and.
B
Notes
and
a
few
news
related
on
SharePoint
framework,
because
we
want
to
actually
give
some
time
for
Chris
and
Russell
on
their
demos
as
well,
so
I
won't
be
taking
too
much
time
on
this
one,
but
a
few
things.
The
site
collection,
app
catalog,
and
this
is
actually
first
time
ever.
We
are
announcing
anything
on
the
special
interest
group
call,
and
this
has
not
even
gone
live
on
the
on
the
Twitter
and
there's
certain
reasons
why
this
happened,
which
is
a
long
internal
story,
but
the
site
collection.
B
Our
catalog
is
actually
available
for
you
to
take
advantage
today.
So
what
this
means-
and
we
can
actually
quickly
explain
that
on
following
slide-
is
that
if
you
are
a
tenant
administrator,
you
are
able
to
activate
the
site
collection
app
catalog
already
today,
using
certain
on
that
in
power
shots.
If
you
go
to
the
HTTPS
or
HTTP
a
kms
s,
PDF,
site,
collab
cap
right
now
that
they
came
as
addresses
pointing
to
a
support
article,
which
is
explaining
what
is
the
PowerShell
to
be
executed?
We're
adding
additional
contacts.
B
Contents
on
this
one,
so
they
came
as
address-
will
be
updated
to
just
of
myself
that
come
relatively
soon
from
full
transparency
perspective.
There
was
an
interesting
discussion
internally
that
that
people-
some
people,
didn't
quite
understand
that
the
demand
on
this
capability,
so
they
didn't,
really
see
this
as
a
massive
announcement,
at
least
for
me
and
based
on
that,
their
stuff.
What
we
talked
about
in
ignite.
B
Yes,
I
completely
agree
on
Leo's
comment
on
that
this
one.
Now,
what
does
it
actually
mean
in
practice?
We
contests
slides
true
few
times
in
the
past,
but
just
to
reiterate
to
add
the
message.
It
means
that
to
be
clean,
normally
you
have
a
tenant
level,
app
catalog
in
office
365
level.
So
if
you
put
something
there
all
of
those
solutions
available
and
visible
across
all
of
them,
sorry
excuse
me
all
of
the
site
collections
and
sites
now
using
the
site
collection
scale.
B
Back
catalog,
which
is
still
controlled
by
the
tenant
admin
you
can
enable
a
site
collection,
specific
app
catalog,
which
means
that
your
solution,
SPF
X
solution
or
an
adding,
is
only
available
within
that
side
collection.
So
it's
a
scoped
a
way
of
deploying
the
customization
to
be
available
from
a
functionality
perspective.
This
is
actually
super
easy.
It's
a
one
powershell
command
to
enable
that,
in
a
one
side,
collection
or
a
second
site
collection
command
to
disable
that
from
the
side
collection,
we
do
have
some
limitation
known
limitation,
which
we're
working
at
this
point.
B
So
there's
no
powershell
commandlets
to
get
lists
of
site
collections
where
this
feature
is
the
label.
So
you
need
to
kind
of
a
what
you
need
to
either
wait
awhile
to
get
that
feature
they
or
you
need
to
track.
Where
there's
like
questions
got
that
catalog,
he
has
been
enabled
a
small
camp,
but
that
will
be
addressed
in
the
future
as
well,
but
really
points
of
this
one
or
why
is
it
so
important?
B
It
absolutely
provides
flexibility
for
enterprises
on
the
deployment
options,
so
you're
able
to,
for
example,
target
some
of
your
shipment
framework
with
parts
only
to
be
available
in
your
corporate
intranet,
which
is
typically
a
publishing
classic
publishing
site,
because
SPF
X
works
in
a
classic
populist
in
science
as
well,
but
not
to
be
available,
for
example,
in
a
cooperation.
So
it's
understand
that
that
is
absolutely
a
massive
deal.
B
It
also
provides
decentralized
management
of
ad
instance
open
framework
packages,
so
as
a
tenon
administrator
I
can
delegate
that
hey
within
this
intro
global
internet
site
collection,
let's,
let's
leave
those
guys
to
be
responsible
of
their
own
thing
and
they
can
actually
enable
stuff
as
they
wish,
and
they
can
easily
do
that
and
also
scope
deployments.
So
the
visibility
of
a
functionality
on
in
a
foreign
particular
site
collection.
B
Now
one
thing
to
remember
on
the
decentralized
to
hem
and
management,
and
these
centralized
that
mean
SPF
X,
especially
it
is
still
full
trusted
to
JavaScript
running
in
the
browser's
context.
So
whenever
you
actually
give
the
responsibility
for
somebody
else
to
host
and
run
a
SharePoint
framer
solutions
in
a
site,
collection
level,
you
actually
delegate
the
responsibility
of
validating
in
quotes
to
code
as
well,
so
with
great
power
comes
great
oil,
crate
responsibilities
as
well.
B
So
please
do
remember
the
impact
from
a
carbon
ons
perspective
around
this
one,
but
it
is
no
doubt
a
great
capability
and
absolutely
important
for
certain
Enterprise
scenarios
quickly.
It's
just
a
we.
We
iterate
where
we
are
from
a
ship
on
development,
roadmaps
perspective
and
the
title
is
just
shipped
I.
B
Don't
know
why
well
ignite
week
or
after
we
shipped
quite
a
lot
of
functionalities
and
the
latest
one
will
being
the
site
specific
app
catalog,
which
is
now
allowing
the
scope
deployment
it
is
available
today
cross
cross
globally,
so
we're
able
to
use
and
enable
that
in
the
cycle
in
your
site
collections
now
we're
coming
soon
is
the
asset
included
in
deployment
packages.
This
is
something
which
requires
say
a
client-side
packages
updates,
so
human
template
packages
being
updated,
and
this
is
coming
super
super
super
soon
and
I.
B
Think
last
time
I
said
it's
coming
in
a
matter
of
days
rather
than
weeks
or
months,
and
now
we
can
probably
say
it:
it's
coming
in
a
matter
of
hours
rather
than
days
or
weeks.
Oh,
it's
coming
quite
soon,
you'll
see
an
update
communications,
obviously
in
social
media
and
Twitter
and
Facebook,
and
wherever,
when
the
latest
packaging
is
available
and
that's
the
site
has
it.
Packaging
is
a
massive
deal
because
it
will
reduce
still
or
it
will
simply
find
the
deployment
of
your
packages
to
the
SharePoint
for
a
shipment
online.
B
So
you
don't
have
to
worry
about
CD
and
hosting,
because
we
take
care
of
the
hosting
for
you
and
that's
a
super
cool
thing.
As
part
of
that
release
will
update,
we've
been
updating,
also
the
videos
and
tutorials
or
mentation.
So
you
can
actually
follow
up
on
the
changes
on
that
one.
Whenever
stuff
is
getting
up,
will
the
guidance
question
from
Joe?
Will
the
these
containers
the
instructions
to
update
existing
solutions?
B
No,
it
actually
doesn't
that's
a
fair
point.
Maybe
we
should
work
on
there
on
the
guidance
on
that.
One
good
point.
Thank
you
for
that.
It
is
basically
an
existing
it's
it's
a
super
simple
thing
from
a
developer
perspective,
it's
a
one
attribute
in
a
package
solution
Jason.
How
do
you
control
is
the
assets
getting
a
package
or
not
and
by
default,
if
I
remember,
the
value
is
true,
so
stuff
is
getting
packets
but
fair
point.
B
We
we
should
double
check
in
the
impact
of
this
one
and
potentially
document
that
for
you
as
well
now,
the
other
stuff
which
is
coming
are
still
PI
end
of
this
year.
Our
site,
designs
with
extensibility
point,
is
coming
by
end
of
this
year,
so
within
the
matter
of
week
or
two,
because
we
need
to
get
it
shipped
by
end
of
this
year,
because
we
promised
to
do
so
and
also
the
my
own,
more
Microsoft
craft
support
s
plan
to
go
out
later
this
year
as
well.
B
So
really
good
news,
and
if
you
have
some
time
on
the
Christmas
holidays,
to
check
these
things
out,
it's
a
great
opportunity
to
test
previous
stuff
up
sites
and
hop
API
is
group
if
I
API,
if
they
are
coming
in
the
next
quarter,
somebody
last
time
when
I.
Actually,
this
somebody
work
then
immediately
asking
okay.
So
what
happens
in
the
queue?
B
Sorry
for
running
slightly
loath
on
time,
I'm
gonna,
plane
Patrick
on
this
time
on
that
one,
but
I
think
the
next
thing
is
too
much
Russell
and
Chris
to
do
a
quick
demos
on
their
stuff.
That's.
B
B
C
Yes,
so
when
we
allow
users
to
share
files
in
a
SharePoint
site,
the
sharing
can
get
out
of
control
and
it's
often
quite
done
to
determine
actually
who
has
permissions
so
to
what
documents
and
folders
in
a
site.
So
I
created
a
component
I
call
a
security
grid
and
what
it
does
it
aims
to
give
you
a
user
at
a
glance
view
as
to
who
has
permission
to
us.
So
when
you,
this
is
a
sample
of
the
grid
when
I
load
it
up.
C
It's
showing
me
a
list
of
the
users
across
the
top
of
the
page.
The
list
of
all
the
lists
and
libraries
across
the
left
edge
and
in
the
middle
it'll
show
you
who
has
the
selected
permission
and
I
can
select
different
permissions
to
view
by
using
this
tool
bar
up
top
currently
I'm,
showing
people
with
view
permissions
I
can
instead
say
I
want
to
see
who
has
edit
list
permissions
and
you'll
see
that
the
grid
changed
to
reflect
that
to
show
who
had
those
permissions
I
can
also,
if
I
want
to
select
specific
users.
C
I
can
come
in
and
say:
hey
just
show
me
these
couple
of
users
on
the
grid
and
it'll
it'll
show
those
users
likewise
I
can
select,
which
lists
I
want
a
view
just
to
narrow
down
if
I,
if
I'm,
only
looking
for
specific
information
and
then
for
each
listing
library,
I
can
go
ahead
and
expand
a
library
to
see
the
folders
within
it
and
as
I
do
this.
If
calculating,
who
has
the
selected
permissions
to
each
of
these
items
right
down
to
the
document
level?
C
So
here
we
can
see
that
Abe
has
edit
permission
on
this
document
doc,
but
George
has
nothing
if
I
switch
this
to
view
list
items
I
want
to
see
who
can
view
this
you'll
see
that
they
both
have
the
view.
That's
so
that's,
basically
how
it
works.
I've
also
got
some
configuration
settings
in
here.
If
we
wanted
to.
If
an
admin
wanted
to
pre
configure
this
for
a
site,
owner
I've
got
some
tools.
That
would
let
them
do
that.
C
So
if
I
wanted
to
pre
configure
this
and
give
it
to
a
user,
so
they
didn't
know
about
custom
permission
levels,
I
could
say:
I
want
to
I
want
to
create,
have
the
default
permission
type,
the
Edit
list
items
permissions
for
instance,
and
then
uncheck
the
box.
That
says
let
the
user
select
the
permission
and
that
will
hide
the
ability
for
him
to
select
his
own
permissions
got
the
ability
to
show
the
name
or
the
email
on
the
top
that
corresponds
to
this.
It's
just
toggles
between
show
on
the
user's
name
and
email.
C
I
can
also
show
security
groups
rather
than
users,
if
I
like.
So
this
is
showing
the
security
granted
to
the
Active
Directory
groups
within
this
site.
I
can
let
the
users
select
users,
so
that
will
hide
the
user
selection
box
so
that
the
whoever
is
using.
This
cannot
change
the
users
and
then
the
title
column
with
this
thing
is
actually
resizable
here.
C
If
you
get
too
deep
in
the
folder
structure,
you
can
just
drag
and
drop
to
resize
it
and
then
on
the
second
page
of
the
configuration
if
I
want
to
I
can
select
if
I
want
to
show
hidden
lists
and
system
lists
and
again
whether
I
want
to
let
the
user
change
the
list
of
selected
lists.
This
will
hide
the
the
control
in
the
ribbon
and
then
finally,
I
can,
if
I
want
to
have
just
specific
lists
shown
on
the
I,
can
select
them
here
and
either
include
or
exclude
those
lists.
C
C
C
C
C
The
lists,
so
he
in
one
shot
I
get
everything
from
from
SharePoint,
so
that
I
can
continue
to
render
the
grid
and
then
he'll
go
back.
That
gets
returned
back
to
the
security
service
and
he
goes
ahead
and
renders
a
details
list.
This
is
all
using
fabric
components
and
the
columns
in
that
details
list
include
a
column
for
each
user.
C
And
when
I'm
going
this
is
this
is
actually
renders
a
cell
for
that
for
that
user
and
I
call
back
into
the
security
service.
This
method
to
say:
does
the
user
have
the
permission
and
he
checks
all
the
security
bits
that
we
got
back
from
SharePoint
to
determine
if
the
user
does
in
fact
have
permissions,
and
then
it
renders
the
the
circle
filled
or
not
filled
depending
on
if
the
user
has
permissions,
so
that's
a
high-level
overview
of
the
the
application.
A
couple
of
things
I
want
to
do
going
forward.
C
C
I
could
make
it
so
that
you
know
it
show
read
if
the
guy
could
read
it
and
show
Brina
if
he
could
write
to
it,
I
need
to
put
in
something
to
to
account
for
access
requests
that
are
outstanding
or
think
if
a
there's,
an
outstanding
access
request
to
give
someone
access
to
a
Lister
library
that
this
should
reflect
it.
It
doesn't
currently
because
the
person
person
hasn't
accepted
the
request,
so
I
hope
to
learn,
work
on
that
and
also
anonymous
access
links.
C
C
When
I
add
a
group
to
SharePoint
the
object,
that's
created
in
the
in
the
the
users
list
for
an
Active
Directory
group
as
the
security
I
this
this
SID
in
the
login
name
and
I'm,
trying
to
figure
out
how
to
get
that
SID.
The
members
of
that
group
from
the
graph
and
I'm
having
trouble
figuring
that
out.
It
works
fine
for
for
modern
groups,
because
the
login
name
that's
stored
in
user
information
list.
That
is
the
actual
gooood
of
the
object
in
Azure
ad.
C
B
Cool
Thank
You
Russell
for
that
one
really
really
really
create
web
part
and
Luis
is
providing
your
potential
solutions
for
the
discussion
as
well,
and
although
save
somebody
can
help
with
that,
that
would
be
proven
now.
I
think
we
need
to
flip
on
Chris
because
we're
running
low
on
time
again
like
I
always
do
there
would
be
so
much
to
do
so
much
to
talk
about
together,
but
Chris.
Thank
you
Russell
for
this
one
and
Chris.
Can
you
hear
us
I
can
hear
you?
Can
you
hear
me
yeah
that.
D
Right
so
my
name
is
Chris
Kent
there's
my
Twitter
there's
my
blog
feel
free
to
reach
out
for
anything.
Alright,
so
I
want
to
show
off
a
web
part,
it's
really
just
demoing
how
to
use
these
reusable
property
pain
controls.
So
if
you
guys
haven't
seen
this
yet
there's
an
open
source
library
up
and
we
get
it's
got
a
bunch
of
stuff.
So
out
of
the
box,
Sherman
firmer
gives
you
a
ton
of
different
property
paint
controls.
D
So
these
are
the
different
types
of
controls
and
click
that
pencil
the
show
up
over
there
there's
a
bunch
in
there.
The
cool
thing
is
it's
really
easy
to
add
your
own.
So
if
you've
got
some
ideas
for
a
cool
way
to
do
that,
this
thing
is
totally
open.
Add
them
in
there
is
a
really
nice
ones,
like
the
list
picker
or
a
term
picker
that
really
wrap
up
a
lot
of
that
complexity.
For
you,
the
two
I'm
gonna
focus
on
showing
you
today
are
the
spin
button
and
the
color
picker.
D
Now
these
are
just
wrappers
around
the
UI
fabric
react
components
of
the
same
name.
However,
you
don't
need
to
use
react
in
your
project
at
all
and
in
fact,
what
part
I'm
going
to
show
you
is
a
no
framework
web
part,
and
so,
let's
take
a
look
at
what
it
looks
like
okay,
so
here
we've
got
a
workbench
and
if
I
go
and
I
add
my
exciting
SVG
hero
web
part,
we
see
I
get
this
beautiful,
PNP
superhero,
I'm,
gonna
click
this
edit
button,
that's
where
we
start
to
see
these
properties
show
up.
D
So
here
we've
got
the
spin
button
property
paint
control.
Where
I
can
look
at
these
nice
little
spin
buttons
here
and
I
could
hit
up
or
down
right
because
he's
doing
that
on
the
step.
So
it's
going
up
and
down
by
five
the
nice
thing
is
I
can
go
all
the
way
down.
I've
set
a
minimum
value
of
25
I
can't
go
below
that
very
similarly,
I've
got
a
maximum
value
up
here.
So
I
can't
go
down
that
different
than
like
us.
D
They
have
text
control,
so
a
text
control
always
returns
a
string
right
so
you're
responsible
for
doing
you
know
a
lot
of
stuff
there
when
you're
trying
to
do
a
number
so
right
now
the
recommendation
is
generally
use
a
slider
right,
but
when
you
need
to
be
a
little
more
specific
than
that,
that's
where
you're
gonna
use
something
like
this.
It's
guaranteed
to
always
come
back
as
a
number.
D
You
know
if
someone
typed
in
you
know
a
string
here,
you
know
it's
gonna,
just
default
with
a
minimum
value,
same
thing,
so
much
types,
some
kind
of
crazy
value
right.
It's
gonna
go
over
the
maximum.
Meanwhile
they
could
still
type
in,
like
I've
allowed
two
decimal
places,
which
is
configurable
all
right.
You
could
type
that
in
here,
okay,
so
all
of
that
just
kind
of
works
together.
This
is
an
SVG
image,
which
is
why
this
is
working
the
way
it
is
so
that's
kind
of
a
spin
button
control.
D
Well,
the
other
thing
I
didn't
mention
here
is
the
suffix.
So
you
can
add
this.
Obviously,
that's
not
returned
back
at
the
value
you
just
get
back
to
the
number,
but
this
is
a
really
nice
indicator
to
users
exactly
what
they're
setting
alright
so
down
here
we've
got
the
color
picker
control,
which
you
see
I've
got
a
ton
of
them
here.
If
I
want
to
come
in
here
and
I
want
to
say,
you
know
what
let's
make
this
guy
a
little
prettier
right,
let's
go
to
yellow
cave
still
for
a
nice
red
shirt.
D
Let's
adjust
that
diaper!
You
know,
let's
make
that,
let's
make
that
a
green
here.
Nice
thing
is,
you
could
set
these
by
dragging
the
user
around,
but
you
can
also
grab
the
Danville
values
you
can
set
those.
So
if
I
wanted
to,
you
know,
set
the
pants
so
build
a
more
of
a
traditional
Robin
type
of
look.
I
can
hit
that
and
you
can
see
all
that
gets
updated
kind
of
on
the
fly.
So
that's
what
the
color
picker
control
does
a
couple
things
to
know
what
the
color
picker
is.
D
You
can
say
I
turn
off
this
alpha
slider
now
you
can
also
make
it
so
it
just
shows
full
like
this,
but
obviously
I'm
showing
so
many
of
these
I,
like
the
inline
style,
the
best
okay.
So
let's
take
a
look
at
a
couple
things
with
that.
So
if
we
go
back
to
these
slides
here,
here's
how
you
use
those
property
paint
controls.
So
you
just
going
to
add
them
to
your
project.
You're
gonna
run
this
NPM
install
command.
All
this
is
available
and
a
really
nice
getting
started
guide.
That's
up
available
on
the
site.
D
The
URL
is
down
there.
You're
just
gonna
run
that
it's
gonna,
add
it
into
your
project
and
then
you're
gonna.
Do
this
one
little
step
where
you
know
your
config,
that
jason
and
then
underneath
the
localized
resources,
node,
you're
gonna,
add
this
property
control,
strings,
okay
and
then
you're
gonna
use
the
controls.
It's
very
exciting.
So
I'll
show
you
what
that
looks
like
these
two.
D
A
couple
notes
on
this
PNP
man,
so
I,
took
the
original
here
had
a
couple
problems
with
it
here,
mostly
that
was
a
raster
image
which
made
it
difficult
for
me
to
scale
this
thing
when
the
shooters
on
slides
and
that's
where
this
has
come
from,
if
you
guys
want
to
use
that
it's
totally
open,
there's
both
the
original,
which
is
also
now
an
SVG,
but
then
there's
this
new
one,
which
is
just
slightly
change
those
proportions
a
little
bit.
You
guys
feel
free
to
have
at
it.
It
works
nice
and
PowerPoint.
D
Alright.
So
again,
this
is
my
little
web
part
very
simple.
In
the
config
dot
JSON
after
I
run
that
npm
install
I've
just
copied
in
this
property
control
strings.
You
can
cut
and
paste
that
directly
from
the
website,
just
put
it
on
there.
That's
just
going
to
make
sure
that
the
localized
strings
inside
the
properties
and
controls
are
synced
up
and
then
an
actual
web
part.
D
You
can
see
here's
where
I've
got
the
standard
kind
of
property
pane,
so
that
could
be
using,
but
down
here
very
similarly,
I'm
just
importing
the
ones
I
need
directly
from
there
and
if
you
go
to
the
guy
that'll
show
you
the
exact
thing
you
can
cut
and
paste
for
each
of
these.
So
here's
what
I've
got
my
color
picker
and
color
picker
style,
assistant,
enum
and
then
my
spin
button
right
here
you
can
see
where
I've
declared
my
properties
interface.
D
You
can
see
I'm
expecting
the
CSS
compatible
string
back
from
the
color
picker,
so
those
are
just
string
values
that
I'm
going
to
use
directly
and
then
I
can
be
guaranteed.
That
spin
button
is
always
going
to
return
me.
A
number
so
got
that
here
in
height
and
the
way
I'm
translating
that's
that
SVG
images
I'm
directly
rendering
the
SVG
image
right
here,
which
is
just
something
created
in
Inkscape
and
then,
if
you
open
up
an
SVG
image
and
save
visual
studio
code,
you're
gonna
get
this
text
view.
D
You
can
cut
paste
that
right
in
here
and
you
see
I'm
just
inserting
the
properties
directly
in
it.
So
there's
the
height
just
roll
down
by
the
way,
as
you
see
I'm
starting
for
the
scanned
in
right
for
the
hands
on
all
that,
so
it
should
be
pretty
straightforward.
You
can
check
all
this
out.
This
webpart
is
available
as
part
of
the
web
port
web
parts
samples.
D
If
you
wanted
to
say
hide
that
alpha
slider
right,
it's
right
here
and
you're,
just
gonna,
say
true
and
that's
gonna
get
rid
of
that
and
that's
stuff,
pretty
much
it
so
there
again.
These
are
just
two
of
the
controls
in
there
there's
a
ton
in
there.
Please
feel
free
to
add
to
this.
It's
really
powerful
library
make
your
web
parts
quite
a
bit
better.
Okay!
It's
all!
We
got.
A
Awesome
very
cool,
very
demo,
they're
both
you
guys,
Russell
and
Chris.
Thank
you
very
much
really
great
to
see
the
stuff
the
community
does
and
like
I
mentioned
earlier.
If
you
have
done
some
work
around
SharePoint
framework
or
the
client-side
libraries
or
just
client-side
development
on
SharePoint
in
general
and
you'd
like
to
demo
that
on
this
call,
you
just
have
to
get
in
touch
with
either
myself
or
vaisya,
and
we're
happy
to
help
set
that
up.
A
So
if
you've
done
a
new
demo
into
the
SharePoint
framework,
webparts,
that's
a
great
source
for
these
kind
of
things.
So
just
let
us
know
if
you're
interested
in
doing
a
demo
would
love
to
have
you
on
the
call.
So
that
looks
like
our
time
for
this
week
we
don't
have
much
time
for
Q&A,
but
our
next
meeting
is
gonna,
be
December,
21st
I
know
this
is
a
holiday
period
for
a
lot
of
folks.
I
will
be
working
so
I.
A
This
meeting
will
happen
but
understand
if
folks
can't
make
it
will
have
the
recording,
of
course
like.
Like
always,
and
then
our
next
general
meeting
is
the
14th
of
December.
So
that
would
be
next
Thursday
says
as
you're
familiar
with
I
think
by
now
these
are
every
other
week.
So
look
forward
to
seeing
you
at
those
meetings
and
remember,
learn,
reuse
and
share,
and
that's
the
is
that
our
new
pnp
motto
did
I
leave
and
we
changed
mottos.
Well,.