►
From YouTube: SPFx JavaScript SIG 21st of December 2017
Description
Recording of the SIG call from 21st of December 2017. Latest news on SharePoint Framework and on the SharePoint JavaScript community efforts.
'More details on covered content from https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Patterns-amp-Practices-JavaScript-Special-Interest/m-p/140921#M4081
A
Hello
and
welcome
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
sync
is
December,
21st,
2017,
I,
hope
everybody
is
in
the
holiday
spirit,
whatever
holidays,
one
might
celebrate.
I
know
we're
all
getting
ready
to
for
a
little
bit
of
time
off,
which
is
always
wonderful.
We
could
spend
with
friends
and
family,
but
first
we're
gonna
do
our
sink.
A
The
first
is
to
the
Microsoft
tech
community,
SP
P,
&,
P
community
will
take
you
to
the
Microsoft
tech,
community,
sort
of
the
the
SharePoint
I
guess
area
or
channel
or
whatever
we
call
it
there
for
SharePoint
development.
It's
a
great
resource.
If
you
have
general
questions
things
like
that,
that
aren't
necessarily
an
issue
for
one
library
or
another.
That's
a
great
place
to
get
those
kind
of
questions
answered,
and
the
second
link
is
a
link
to
the
official
documentation
for
SharePoint
development.
A
So
do
check
that
out
we're
working
to
update
that
as
often
as
we
can
as
well.
So
moving
right
ahead.
Our
agenda
for
today
we're
gonna
do
a
quick
update
on
the
JavaScript
core
component
and
then
I've
got
a
couple
of
demos
around
that
that
we'll
talk
about
later
or
do
after.
We
do
a
SharePoint
framework
update
from
visa.
A
But
we
like
to
remind
folks
of
the
different
ways
you
can
get
involved
in
both
this
call
and
the
larger
patterns
and
practices
program.
The
first
one
is
demo
a
SharePoint
framework
solution.
So
usually
we
don't
this
week,
but
typically
we
have
a
lot
of
community
demos
on
these
calls
and
if
you
would
like
to
be
or
do
one
of
those
demos
just
get
in
touch
with
us,
we'll
get
you
on
the
schedule
and
you
can
do
your
demo
on
the
call.
A
Typically,
those
are
gonna
come
from
webparts
or
extensions
that
have
been
submitted
to
the
gallery
on
github,
but
that's
not
necessarily
a
requirement,
but
that
does
also
get
you
a
little
bit
additional
visibility
into
the
the
work
you're
doing
the
cool
demo.
You've
created
you
can
contribute
on
github,
so
contribute
on.
Github
involves
pull
request,
submitting
code,
it
involves
submitting
issues
when
you
find
issues
in
the
JavaScript
core
libraries
or
any
of
the
libraries
helping
on
issue.
A
A
A
So
we'll
step
into
an
update
on
the
the
JavaScript
core
component
released
earlier
this
week
on
the
18th
on
time
for
once
released,
SP
P,
PJs
3:03.
It
was
a
smaller
update,
but
I
had
a
couple
cool
new
additions
in
there,
as
well
as
a
couple
bug
fixes.
But
we
now
have
support
for
regional
settings
off
of
the
web
object.
And
then
you
can
now
get
list
item
versions
previously,
maybe
7
5,
green.
A
Yeah
I,
don't
usually
say
my
password
here
on
the
calls,
but
so
so
previously
we
only
supported
document
versions,
and
so
we've
added
support
for
the
list.
Item
versions
and
just
a
heads
up
the
rest.
Api
for
list
item
versions
is
much
more
limited
than
the
document
api.
For
example,
you
can't
go
get
previous
versions
and
things
like
that.
The
way
you
can
for
documents,
but
you
can
look
them
up
now-
look
up
the
version,
so
we've
added
the
support
we
could.
A
Their
work
continues
on
the
at
PNP
scoped
libraries
I
had
I
wanted
to
get
the
release
out
before
the
end
of
this
calendar
year.
The
code
is
basically
ready
at
this
point,
but
I'm
still
working
on
documentation.
So
it
looks
like
early
2018
for
getting
those
libraries
out
there
and
I'm
gonna
demo
today
on
how
to
update
a
solution
from
SPP
and
PJs
to
these
new
libraries
and
I
just
want
to
point
out
again
that
they
are
available
as
beta
versions
right
now.
A
So
if
you
grab
those
and
I'll
show
that
again
in
the
demo,
but
if
you
want
to
grab
those
off
the
beta
Channel,
you
can
begin
working
with
them
or
trying
them
out
over
the
holiday
break.
If
you
have
some
time
and
then
finally,
the
issues
list
I
just
wanted
to
mention,
we
do
have
a
few
discussions
going
on
there
about
one
about
large
batch
processing
and
then
a
second
around
support
for
a
new
API
that
we're
getting
some
good
feedback
on.
So
we
might
add
support
for
that.
A
A
A
So
real,
quick
I
wanted
to
show
folks
how
to
update
a
solution
from
SPP
and
pjs
library
to
use
the
new
at
PNP
scoped
work.
So
what
you
see
here
this
is
a
hello
world
web
part
of
created
in
SharePoint
framework
and
alls
I've
done
is
run
the
yeoman
generator
I've
created
the
boilerplate
hello
world
web
part
with
no
JavaScript
framework.
So
this
is
no
frameworks,
no
any
confusion.
A
It's
just
the
straight-up
JavaScript
hello,
world
web
part
and
then
I've
I've
added,
SPP
and
PJs
to
the
library
and
I've
imported
some
things
we're
going
to
so
the
pnp
root
object,
which
I
think
most
folks
may
have
been
familiar
with
if
you've
used
the
library
and
then
we've
also
imported
some
individual
items
so,
for
example,
the
web
class,
the
util
class
and
then
logger
the
log
level
and
the
function
listener
logging
listener.
So
I
want
to
kind
of
step
through
where
we
added
that.
A
So
first
we're
setting
the
active
log
level
to
verbose
and
then
we're
subscribing
a
new
function
listener
to,
and
this
logger
is
the
SPP
and
pjs
logger.
So
we're
subscribing
a
function
listener
that
is
then
logging
to
the
SharePoint
framework
log.
So
this
is
not
something
you're
required
to
do,
but
I
wanted
to
sort
of
demonstrate.
A
You
know
hooking
up
this
logger
to
the
SharePoint
framework
logging.
So
all
the
logging
will
kind
of
go
through
one
channel
and
end
up
in
the
same
place
which
by
default,
would
be
the
console
in
the
browser.
But
you
could
write
your
own
SharePoint
framework
loggers
and
things
like
that,
but
we
won't
get
into
that,
but
we
have
subscribed
a
logger
to
the
SPP
and
pas
work
here,
I've
added
the
on
a
knit
code.
A
So
every
time
you
work
with
SPP
in
PJs
within
SharePoint
framework,
you
need
to
pass
in
the
context
of
that
web
part
or
that
extension
and
the
reason
for
that
has
to
do
with
how
SharePoint
framework
its
SharePoint
framework
itself
works.
In
that
the
only
valid
context
is
the
one
contained
in
essentially
the
closure
of
that
web
part.
There
is
no
sort
of
global
context.
A
So
it's
important
to
always
add
this
on
an
it
block
and
you
can
see
that
that's
on
the
wiki,
if
you
need
to
grab
that
and
then
in
the
render
method,
we've
written
again.
This
is
obviously
a
very
complicated
web
part,
but
we
show
a
simple
loading
message
and
then
we're
showing
a
couple
different
techniques
here,
because
I
wanted
to
show
updating
some
different
things
so
we're
taking
our
web
instance
and
we're
actually
setting
from
the
context
directly
the
absolute
URL
of
the
web.
A
We
want
to
use,
and
so,
if
you
do
this,
you
don't
actually
have
to
do
the
honor
network,
but
I
wanted
to
show
doing
this.
And
so
we
get
a
web
and
we're
selecting
its
title
and
then
we're
using
to
get
as
method,
which
is
a
part
of
SPP
and
pjs.
That
allows
us
to
type
our
return
and
we're
saying
we're.
A
Gonna
get
back
an
object
that
has
a
title:
that's
gonna,
be
a
string
property
and
then
we're
calling
then
or
saying
then,
and
that's
getting
the
promise
and
we're
saying
on
that
web
we're
just
going
to
update
our
Dom
element.
So
if
you've
done
SharePoint
framework
work,
this
is
our
webparts
dom
element
and
we're
gonna
say
it's.
Inner
HTML
is
just
going
to
be
an
h1
tag
that
says
the
web
title
is
the
title
of
the
web.
A
We
just
got
and
then
we're
going
to
make
a
second
request
here
using
the
P&P
object
that
we
imported
from
SVP
and
pjs
to
do
our
full
method
chain,
so
we're
gonna,
say:
p,
+,
p,
SP
web
lists
select
the
title
of
each
of
the
lists
and
again
we're
gonna
do
a
get
as,
but
you
can
see
here.
Our
object
is
to
be
a
title.
A
That's
a
string,
but
now,
as
is
an
array
of
things
coming
back
and
so
we're
gonna,
do
then,
and
we're
gonna
append
to
that
inner
HTML
element
just
in
HR
and
then
the
lists
there
in
this
web.
And
so,
if
I
am
very
lucky,
let
me
actually
refresh
the
page.
So
we
get
our
web
part
and
hello
world,
and
so
we
can
see
it
at
work.
We
get
the
web
title
and
then
we
see
it
has
these
lists,
and
I'm
doing
this
in
my
tenants
workbench
so
I'm.
A
So
I'll
move
that
off
to
the
side,
and
now
we
want
to
update
this
to
be
or
to
use
rather
the
new
at
PNP
scoped
libraries,
so
our
first
step
to
go
to
the
command
line
and
I'm
gonna
hit
control-c
to
get
out
of
the
server
and
then
the
first
thing
we
want
to
do.
Let
me
pull
up
my
notes
so
not
to
type
all
this
is
we're.
A
It
gives
us
a
lot
more
flexibility
in
the
work
we
do,
but
it
gives
you
all
much
more
flexibility
in
what
you
import
as
well,
and
let
me
give
me
two
seconds
because
I
forgot
to
show
you
one
other
part
of
my
demo
that
is
going
to
make
this
a
little
clearer.
And
so,
if
we
look
here,
this
is
the
actual
file
that
gets
generated
of
the
disk
when
we
do
the
build
or
serve
and
it's
452
K
and
that's
including
it's
built
I'm,
not
doing
any
external.
A
So
that's
building
the
SPP
and
pjs
into
this
file
and
we're
at
452
k,
so
just
kind
of
keep
that
number
in
the
back
of
your
head.
So
splitting
up
these
things
allows
you
to
import
less
stuff
that
you
don't
need,
and
the
second
thing
is
I'm
importing
the
from
the
beta
channel
for
all
of
these
things,
because
we
haven't
done
a
real
release
for
this
stuff.
A
B
A
A
So
we've
installed
our
four
libraries,
which
you
can
all
see,
are
a
beta
dot
seven.
So
one
of
the
new
things
with
the
libraries
is
because
there's
a
bunch
of
libraries
instead
of
one
versions,
could
get
very
confusing.
So
one
thing
we're
gonna
do:
is
every
library
is
going
to
be
released
every
time
whether
it
has
an
update
or
not?
And
that
means
every
time
you
want
to
ensure
you've
got
the
latest
versions
or
that
everything
matches
you
just
have
to
make
sure
everything's
on
the
same
version.
A
So
in
this
case
it's
beta
dot
seven
once
we
do
a
release,
it'll
be
1.0
and
then
they'll
all
go
to
1,
0,
1,
etc.
So
everything
will
move
in
lockstep
and
that
will
hopefully
reduce
a
lot
of
the
confusion
that
could
happen
with
different
libraries
and
do
these
versions
work
together
and
that
sort
of
thing
so
then
I
want
to
come
in
and
we
need
to
start
updating
our
web
part
now
to
use
the
new
at
PNP
scoped
libraries
instead
of
the
SPP
and
PJs.
So
we
actually
don't
have
that
much
work
to
do.
A
But
we
have
a
few
small
changes
to
make
the
first
one.
Of
course
we
need
to
update
our
imports
to
import
from
the
new
libraries,
so
I'm
going
to
do
an
import,
and
the
first
thing
we
want
to
import
is
the
logger
the
function
listener
and
the
log
level
and
we're
gonna
now
import
those
from
that
PNP
logging
and
then
we've
got
a
little
duplicate
error
there.
So
I'm
just
going
to
comment
those
out,
and
now
we
need
to
import
our
util,
so
I'm
going
to
import
whoops.
A
A
So
another
thing
we've
tried
it
I'm
going
to
comment
all
of
those
imports
out
now.
So
another
thing
we've
tried
to
do
is
ensure
and
I
forgot,
a
comma
is
ensure
or
to
make
things
easier.
So
this
SP
library
has
the
main
export
is
SP.
The
graph
libraries
main
export
is
graph,
and
so
that's
hopefully
going
to
help
again
with
the
transition
of
moving
to
these
things
and
helping
you
know
mentally
what
maps
to
what.
A
But
so
this
SP
replaces
that
P
and
P
variable,
and
actually
is
just
the
if
you
remember
P
and
P
OS
P
dot
the
rest
of
the
chain
just
take
away
the
P
and
P
part.
So
I
want
to
come
down
and
let's
update
our
actual
code
now
well,
you
can
see
right
away.
The
logging
stuff
needs
no
updates.
There's
been
no
changes
in
the
logging
framework
for
the
pond,
the
P
and
P
side.
So
we
changed
our
imports.
It
now
works
as
before.
A
So
if
you've
put
logging
throughout
your
code
change
your
imports
at
the
top
of
the
file
logging
is
gonna
continue
to
work
exactly
as
it
did
no
changes
there.
Great
our
next
change.
We
see
a
little
red
squiggle.
Is
this
PNP
setup
the
only
change
there
is
change,
P
and
P
to
s
P
and
we're
gonna
do
SP
setup
and
we
do
it
exactly
the
same.
We
pass
it.
A
The
SPF
context
and
the
format
of
this
object
has
not
changed
from
the
300
version
of
SP,
P
and
PJs,
so
it
has
changed
from
the
to
o,
but
from
the
3
o
version.
No
changes
there.
So
that'll
simplify,
hopefully
again
the
migration
by
changing
the
P
and
P
to
s
P
R
SP
setup
will
be
complete,
we'll
come
down
here
to
the
render
method.
We
have
a
couple.
Other
changes,
no
changes
to
the
web.
Our
web
object
still
works.
A
So
if
you're
using
the
web
object
directly
and
passing
in
URLs,
that's
still
gonna
work,
just
fine,
you
still
select
off
the
web.
It
can
chain
off
the
web
exactly
as
before.
Well,
one
thing
that
has
change
is
instead
of
get
as
you
now
just
need
to
do,
get
and
that's
because
the
typescript
language
was
updated.
So
we
can
actually
do
default
types
in
generic
arguments,
so
we
could
make
that
any
by
default
and
you
can
specify
what
you
want
it
to
be
so
get
as
goes
away.
You
just
need
to
use.
Get
now
accept.
A
The
functionality
is
exactly
the
same,
so
I'm
going
to
do
the
same
thing
down
here
or
change,
get
as
just
to
get,
and
the
last
thing
here
is
I'm
just
going
to
delete
P
and
P,
and
then
everything
else
will
work
the
same,
so
I
can
do
SP
web
lists
select.
Get
and
then
I
get
my
lists
and
that's
all
our
updates
and
everything
you've
come
to
expect
to
be.
There
is
on
the
SP
variable
or
object
now,
so
you
can
say
SP
web
lists
etc.
Get
my
title.
A
All
of
that
still
works
exactly
the
same.
We've
just
changed
the
starting
point
of
where
you're
gonna
chain
from,
and
so
that's
it.
That's
all
our
updates
and
we're
now
using
the
new
libraries.
So
I
want
to
sort
of
show
that
work
by
saying
gulp
serve
again
and
there's
our
web
part
working
exactly
as
before,
and
I'll
assume.
A
You
can
trust
me
that
it's
this
it's
the
new
web
part
with
the
new
code,
so
I'll
riad
it
to
the
page
and
there
it
is
so
everything's,
working
as
it
did
before,
and
we've
updated
our
code
to
use
the
new
at
PNP
scoped
libraries.
So
not
a
lot
of
changes,
not
a
lot
of
complicated
changes.
Hopefully
folks
will
have
a
very
easy
time
with
that
again
we're
working
to
smooth
that
out.
So
any
feedback
on
that
process
will
be
much
appreciated.
A
There
will
be
a
video
recorded
and
posted
as
well,
which
is
pretty
much
what
I
just
showed
you
but
sort
of
isolated.
Out
of
this
call
to
show
that
update
and
I
think
we've
covered
here,
the
most
common
scenarios
of
chaining
off
of
P
and
P,
using
logging
importing
things
like
util
and
then
the
setup
on
an
it.
A
We
are
updating,
just
did
a
big
update
on
Docs
yesterday,
so
you
can
see
this
is
the
github.com
slash,
P
and
P
slash
PNP,
that's
the
Rotonda
c
department
of
redundancy,
but
this
is
updated.
Readme
talks
about
documentation
and
then
links
to
different
packages
that
are
part
of
this
repo
and
we've
got
documentation
for
each
of
those
packages.
Again
this
is
pretty
bare-bones,
but
we're
working
on
improving
it.
As
we
go,
and
then
we
also
have
two
github
pages
site
is
up
and
live
in
the
sense
that
it
exists.
A
Gonna
continue
supporting
SPP
and
PJs
for
six
months
with
once
we
release
the
at
PNP
libraries.
After
that
six
months,
the
core
team
will
no
longer
be
sort
of
actively
supporting
it.
Our
focus
will
move
entirely
to
these
libraries,
but
we
will
always
be
accepting
pool
requests
and
things
like
that
from
the
community.
If
folks
want
to
work
on
or
improve
or
fix
a
bug,
something
like
that
in
SPP
and
PJs,
it
won't
go
away.
It
will
remain
there
and
github.
It's
not
going
to
be
unpublished
from
NPM
or
anything
drastic
like
that.
A
So,
if
you're
using
it
in
your
projects,
now
there's
no
immediate
absolute
need
to
move.
You
know
on
a
certain
schedule,
just
know
that,
after
six
months,
our
core
team
focus
will
move
entirely
to
these
new
libraries.
So
you've
got
plenty
of
time
to
Train
plenty
of
time
to
help
us
help
you
transition
in
terms
of
Venus
the
feedback
and
so
definitely
look
for
and
invite
that
feedback
from
everybody.
So
I'm
gonna
jump
back
now
to
the
presentation
and
go
back
to
they
know.
A
A
B
B
beside
we're
looking
into
having
all
of
the
cross-linking
and
everything
else
for
us
all
of
the
sites
and
URLs,
so
that
people
are
not
getting
confused
because
obviously
we
will
keep
on
doing
and
the
core
team
will
keep
on
doing,
for
example,
PNP
PowerShell
in
the
future
as
there,
even
though
Patrick
you
in
the
context
of
p.m.
PHAs
core,
you
said,
the
core
team
will
never
not
do
anything
else
than
this
library,
so
obviously
the
larger
PMP
according
will,
but
the
core
team
of
the
PHAs
core.
It's
a
different
thing.
B
A
This
again,
just
because
Matthews
asked
to
do
this
again
so
right
now,
we've
got
the
SPP
PJs
library
is
the
JavaScript
client-side
library
that
the
patterns
and
practices
program
is
put
out
and
we've
been
supporting
that
for
over
a
year.
But
we
want
to
move
now
to
these
new
libraries,
these
at
P
and
P
scoped
libraries,
which
will
contain
all
of
the
same
functionality.
Just
slightly.
A
Oh,
my
god,
I
have
a
disclaimer
of
some
sort
right,
but
but
so
the
idea
is
that
six
months
gives
folks
plenty
of
time
to
migrate
existing
projects
or
move
new
projects
to
the
new
libraries.
The
new
libraries
aren't
out
yet
they're
out
in
beta
folks
can
absolutely
please
try
them
out
and
let
us
hear
some
feedback
but
we'll
get
those
out
and
the
idea
being
folks
would
migrate
their
projects
to
the
new
at
P
and
P
libraries
and
again
we're
looking
to
get
that
transition
as
smooth
as
possible
and.
B
B
Exactly
so,
let's
move
into
the
shipment
frame
website
and
choose
some
latest
news
on
this.
One
I
won't
not
have
a
demo
at
this
time
and
because
we
were
actually
expecting
enough
to
have
this
many
people
in
there
in
the
coal,
but
it's
good
to
see
the
interest,
even
though
it
is
a
holiday
season,
but
we
should
have
a
plenty
of
time
for
Q&A
if
we
have
any,
but
some
news
and
some
things
to
actually
cover.
B
Let's
see
if
I
can
get
my
clicker
to
convert
properly
there
we
go
so
since
the
two
weeks
ago,
special
interest
group.
We
we
have
two
special
interest
group
for
SharePoint
frameworks
this
snap,
so
we
have
released
now
the
SharePoint
framework
from
one
point
four,
so
that
came
out
actually
I
would
say
one
hour
after
the
previous
special
interest
group
call
and
in
the
previous
special
interest
group
call
I,
think
we
demonstrated
acid
packaging
already
so
I'm
up
can
actually
do
that
in
here
have
a
webcast
available
for
that
one.
B
We
do
have
other
videos
available
on
how
this
actually
works
and
the
do
toriel's
have
been
updated
to
match
the
asset
packaging.
Well,
the
white
part
tutorials,
and
what
this
one
meant
and
just
to
clarify
on
this
one.
So
if
you
are
built
in
a
SharePoint
framework
solutions
using
this
weapon
framework,
1.4
or
newer
pretty
soon,
there
will
be
a
key
on
the
newer
version.
It's
from
this
moment
forward.
You
do
not
need
to
anymore
worry
about
hosting
the
JavaScript
files,
if
you
don't
want
to
so
by
default.
B
Whenever
you
package,
your
SP
pkt
file,
the
Chaves
kit
files
and
manifest
files-
and
everything
else
is
inside
of
this
BBK
to
file
and
if
your
tenant
has
an
office,
365
CDN
enabled
we
will
automatic
the
served
serve
all
of
the
JavaScript
files
from
the
office
365
CDN.
If
your
tenant
doesn't
have
of
the
365
CDN
enable
we
will
automatically
serve
the
JavaScript
files
from
the
tenant,
app
catalog
site
collection.
B
But
the
key
point
here
is
that
the
step
which,
in
the
past
you
were
forced
to
do,
which
is
boot
to
your
JavaScript
files
on
a
CDN
update
the
URLs
properly
and
everything
else
that's
no
longer
needed
unless
you
explicitly
want
to
do
them
and
that's
a
really
really
important
and
a
great
great
improvement.
So
this
is
super
super
super
functionality.
From
that
perspective,
now
again
mention
quite
a
few
times
reiterating
the
message
as
well.
B
If
you
choose
to
or
if
you
wish,
and
you
wanna
house
this
stuff,
for
example
in
our
show,
CDN
or
in
let's
say,
Amazon
CDN
I,
don't
know
if
they
haven't
said
in
I,
haven't
checked,
you
can
still
do
that.
You
just
flip
the
setting
in
the
packaging
in
the
package.json.
A
package
solution
package
package
solution
chase,
inform
enough
to
actually
include
assets
inside
us
and
package.
What's
good
about
this.
B
One
also
is
the
fact
that,
since
the
javascript
files
are
inside
of
this
PPK
2
package,
I
can
actually
create
and
create
the
SP
PDF
file
the
solution
file
and
I
can
send
it
to
Patrick
or
Sebastian
or
whoever
and
say,
hey,
have
a
look
and
they
can
just
add
it
in
their
chant
and
voila.
It
will
work
because
the
I
don't
need
a
worry
about
where,
where
and
the
chose
get
files
are
being
how
or
and
I
don't
need
to
worry
about
getting
them
hosted.
B
They
are
hosted
automatically
when
this
baby
acacia
files
are
getting
the
front.
So
in
some
sense,
yes
Sebastian
here
and
her
famous.
So
in
some
sense
you
might
kind
of
start
thinking
that
this
is
well
in
in
quotes.
The
idea
is
almost
similar,
our
sample
solution,
but
we
probably
shouldn't
confuse
people
by
using
the
sample
solution.
Gem.
But
basically
you
are
encapsulating
your
customizations
inside
of
the
SPP
acacia
file
and
you're
able
to
deploy
that
to
your
channel
and
that's
super
super
cool.
B
We
did
have
a
small
challenge
with
the
asset
hosting
plus
the
site
collection
at
catalog,
but
that
bug
should
have
been
already
resolved.
So
if
you
are
looking
into
our
using
the
site
collection,
app
catalog
option
that
now
supports
the
assets
packaging
as
well,
if
or
it's
beginning
rolled
out
as
we
speak
in
production
now,.
B
Key
points
quickly
on
the
asset
packaging
kind
of
I
mentioned
this
one
already.
Why
is
this
important?
So
no
there's
no
additional
unsettling
location
needed,
so
everything
is
inside
of
the
buckets
organization
in
control
of
the
solution
isn't-
and
this
is
basically
meaning
that
if
you're
pairing
this
replicated
one
or
a
solution
from
the
third
party,
you
as
the
tenant
owner,
because
the
assets
are
getting
automatically
hosted
from
your
tenant,
you
actually
control
when
the
assets
are
getting
updated.
B
So
the
RSVP
caging
fast,
are
not
referencing
a
rendering
JavaScript
file
from
Internet's
from
somewhere
in
the
URL.
You
actually
have
it
inside
of
your
talent
and
that's
really
cool,
because
then
you
control
when
the
file
suckering,
updated,
really
important
thing,
and
then
you
can
easily
use
the
same
package
to
test
the
stuff
in
the
death
in
the
user,
acceptance
tenant
or
to
user
acceptance
and
environment
depending
on
your
setup
and
then
in
the
production.
B
B
So
right
now
what
has
happened
is
the
site-specific
app
catalog
is
not
animating
as
far
out
as
it
included
in
deployment
packages
is
out
last
time
two
weeks
ago,
that
wasn't
quite
yet
out
site
designs
with
an
extensibility
point
and
the
dogs
are
out
for
that
one
and
it's
gradually
getting
enabled
in
the
first
release.
So
we
unfortunately
found
out
a
small
deployment
challenge
on
that
one.
B
So
it
seems
to
be
that
we
need
to
still
wait
a
few
more
days
and
we
get
to
decide
designs
and
extend
with
the
next
instability
point
to
truly
work
across
globally
in
the
previous
status,
but
that's
getting
handled
within
a
days
now
the
really
kind
of
an
exciting
capability.
What
people
have
been
waiting
for
a
long
long
long
time
is
more
Microsoft
craft
support.
B
Originally,
we
did
actually
promise
to
release
this
by
end
of
this
year
and
we
failed
and
I
do
apologize
on
that,
because
it
will
be
actually
getting
available
on
the
first
or
second
week
of
January.
Well,
that's
the
current
ETA,
but
what
it
actually
means
is
that
you
can
define
as
a
tenant
administrator
what
are
the
permissions
and
scopes
which
are
available
for
the
craft
or
for
external
APRs.
B
So
that
is
a
super
super
cool
capability
and
I
do
have
a
slide
coming
up
on
after
this
one
which,
what
I'm
trying
to
explain
quickly.
What
does
it
all
about?
So
this
is
the
I
quickly.
True,
that's
like
15
minutes.
Before
the
call
first
time
they
were
trying
to
explain
how
how
things
are
actually
working,
but
let's
get
back
on
that
one
in
a
second
and
these
two
other
big
things
are
hub
sites
and
hub
api's
and
a
Cooper
fly.
B
Ap
is
today
we
actually
release
the
new
version
of
season
and
powershell
commandlets
for
sharepoint
in
general,
SharePoint,
Online
and
general,
and
those
actually
contains
some
new
capabilities
for
Krupa
Phi
and
a
four
hub
sites.
They
do
not,
however,
yet
from
birth,
because
the
capabilities
have
not
been
enabled,
but
whenever,
within
the
early
January
within
the
in
January
time
frame,
you
will
see
announcements
whenever
the
hub
sites
and
Krupa
fireEye's
will
move
into
previous
status,
and
then
those
api's
will
be
enabled
as
well.
B
Our
deployment
mechanisms
work
in
a
way
that
we,
how
would
I
put
it?
This
is
almost
like
old-school
way.
Let's
not
actually
even
do
that
comparison,
because
people
might
freak
out
it
works
in
a
way
that
we
push
out
stuff
on
SharePoint,
Online
and
evasions
on
a
SharePoint
Online,
and
then,
when
we
actually
decide,
we
enable
the
functionality.
So
we
enable
the
flight
in
our
internal
terminology.
So
the
fact
that
the
API
exists
it
doesn't
mean
that
it
actually
works.
B
That's
it's
not
quite
yet
ready
to
do
a
live
demo,
but
what
I
wanted
to
do
is
quickly
explain
what
are
we
talking
and
what
does
it
actually
mean
so,
starting
from
early
January?
The
first
week
of
second
week
is
the
ETA
right
now
you
can
actually
configure
additional
permissions
for
the
craft
client
and
what
it
means
is
that
the
tenant
admin
now
my
animations
is
completely
I
took
a
wrong
version.
Patrick.
B
It
is
requesting
the
access
token
automatically
from
Azure
ad
directory.
It
is
getting
the
access
token
that
bearer
token
will
contain
the
additional
permissions
and
scopes,
and
when
it's
calling
that
external
API,
for
example,
we
can
actually
make
the
things
work
properly,
because
it's
calling
using
the
right
scopes
and
right
permissions.
B
B
We've
been
having
and
I
didn't
want
to
show
you
a
doc
which
is
slightly
too
early
environment,
but
this
will
be
super
super
super
great
stuff,
because
this
work
this
for
me
at
least
calling
securely
the
fifth
party
custom,
Web
API,
is
the
holy
crao
of
sharepoint
online
development.
It's
been,
it's
been
the
thing.
What
people
been
asking
from
a
day,
one
in
sharepoint
online?
B
How
do
I
securely
call
in
an
authenticated
manner,
including
authorization,
a
third-party
web
api,
with
a
social
inertia
to
unplug
all
of
the
options
and
possibilities,
what
we
have
in
Asscher
and
voila?
It's
coming
and
that's
absolutely
mind-blowing
and
absolutely
brilliant
good
victim
attic
of
Puppets.
Yes,
my
software
client
is
an
app
defined
in
Azure
ad.
Sorry,
yes,
so
for
Bill
hires,
the
Microsoft
craft
craft
client
is
a
new
object
actually
in
the
SharePoint
framework
and
usher
ad.
Http
client
is
a
new
object
as
well.
B
The
Microsoft
craft
behind
is
just
a
wrapper
in
on
top
of
the
types
of
craft,
JavaScript
library,
and
you
can
easily
use
that
it
will
hide
the
complexity
of
calling
access
and
getting
access
token.
It
will
take
care
of
all
that,
for
you,
the
optional
application
in
Azure
ad
is
called
SharePoint.
Online
client
you,
if
you
are
the
administrator
of
the
azure
ad,
you
can
actually
see
that
there
and
then
that's
the
one
where
we
provide
the
permissions
technically
technically.
B
Also,
if
you
as
a
developer
or
if
you're
an
ISV
developer
and
your
solution
requires,
for
example,
certain
scopes
whenever
you
install
the
solution
to
the
app
catalog,
you
can
configure
that
solution
to
indicate
that
hey.
Do
we
have
additional
permission
requirements
so
this,
but
this
solution
actually
requires.
For
example,
what
would
it
be?
B
People
contacts
read
permission
for
for
the
users
and-
and
you
can
actually
in
this
solution
package
JSON
file-
you
can
define
that
there's
additional
permissions
needed
and
there
is,
you
know,
scopes
for
the
craft
and
when
that
happens,
when
somebody
is
installing
the
solution
to
the
app
catalog,
the
inadvertent
is
going
to
be
notified.
That
hey.
This
solution
requires
scopes,
which
I'm
up
to
default
scope.
Additional
scopes
of.
Please
go
through
the
approval
process.
B
We
do
have
an
approval
functionalities
for
these
additional
scopes
in
the
central
admin
UI
or
using
a
PowerShell,
so
they're
sadist
approval
process
for
getting
the
scopes
what
the
solutions
are
requesting.
But
ultimately,
what
happens
is
that
you
are
adding
conditions
that
sharepoint
online
client
object,
which
is
an
azure
ad
and
depending
on
those
permissions,
depending
on
the
skills
that
has
been
configured
for
that
one.
Then
you
have
access
in
the
Microsoft
craft
client
or
in
our
ADHD
Bitcoin.
So
it's
super
cool
super
cool
stuff
quickly.
B
Looking
into
the
questions,
somebody
carry
a
surface
book
to
you,
that's
pretty
cool.
So
so
there
is
a
single
for
all
SPF
X
solution
that
used
to
craft.
That
is
correct
and
that's
a
good
point
from
Philip
as
well,
so
you
might
have
multiple
solutions
which
have
slightly
different
scopes
requirements,
for
example,
for
crafts,
and
you
you
as
a
developer,
you
can
configure
those
scope
requirements
in
this
V
pkg
file.
There
is,
however,
only
one
object
so
we're
not.
Ultimately
we
are
not
dynamically
provisioning
at
your
ad
application
objects
to
the
other
ad
per
solution.
B
There's
only
one
object
in
the
art
rarity
and
super
important
thing
to
realize,
and
that
means
that
if
there's
two
applications
which
are
requesting
different
scopes,
you
will
enable
both
of
those
scopes
to
that
one
single
object,
and
that
means
that
it
might
be
that
there's
another
application
which
isn't
asking
any
permissions
in
the
SB
pkt
file
or
in
a
package.json
file.
But
when
it's
actually
calling
the
craft
API,
it
will
have
the
same
access
tokens
as
well,
and
that's
why
this
is
a
tenant
administrative
operation
and
in
our
documentation.
B
We
will
absolutely
go
through
in
detail.
What
does
it
actually
mean?
What
are
the
implications
whenever
you,
for
example,
uninstaller
solution
from
that
catalog?
It
does
not
remove
any
of
these
permissions
or
any
of
the
scope.
So
this
is
using
Ada
and
still
because
they
does
only
let's
say
officially
released
version
of
the
JavaScript
libraries
to
talk
against
a
sure
ad
MSI
I'll.
I
don't
think
it's
well.
It
has
not
yet
been
released
to
a
final
version
or
it's
wasn't
at
least
released
when
the
decision
on
the
tech
for
this
one
was
actually
done
now.
B
Obviously,
in
the
future,
when
things
are
evolving,
we
will
absolutely
keep
on
evolving
this
implementation
as
well
I'm,
definitely
going
to
need
the
special
video.
Yes,
we
will
have
an
extended
tutorials
we're
looking
into
having
a
tutorial
on
the
basic
flow,
so
how
to
actually
configure
a
right
away,
part
which
is
action
requesting
additional
scopes
of
the
craft
and
then
what's
the
approval
process.
B
For
that,
the
second
video
tutorial
hands,
plus
video
will
be
around
how
to
create
a
third-party
web
api,
the
third-party
web
api
and
configure
that
to
be
accessible
and
call
a
polar
from
the
shipment
framework
web
part.
But
if
we
cover
both
of
those
as
a
tutorial
and
then
we
have
additional
documentation
which,
what's
true
old,
terminologies
and
everything
else,
I
think
we
should
be
in
a
relatively
good
shape.
With
the
code
of
samples,
videos
and
written
the.
B
Simple
with
just
in
time,
thank
you
say
for
me
having
okay
sounds
good,
but
that's
pretty
much
on
the
craft
on
third
party
API
access
support.
If
you
are
interested,
this
intern
process
did
not
really
change
that
much
since
the
Ignite
demo,
so
in
ignite,
Paulo
Parc
actually
demonstrated
this
functionality
in
it
was
Paolo's
and
look
up
on
dinelli's
session
I.
Look
upon
the
realization
where
Paulo
was
doing
actual
demos
where
they
demonstrated
the
functionality
of
calling
a
third-party
web
api
using
this
method
from
a
SharePoint
framework
resolution
huge.
B
That's
it
for
that
one
with
my
clicker,
my
clickers
over
there,
but
that's
it
for
the
SharePoint
frame
website
so
like
mentioned
I
could
not
unfold
them
with
a
point
demonstrate
that
yet,
on
the
next
time
on
the
4th
of
January
I
will
promise
that
we
will
have
a
live
demo
record.
Less
is
the
relationship
on
nut-shaped
most
likely
it's
not
shipped,
because
obviously
people
are
on
vacation
right
now.
Authority
of
people
in
Redmond
are
on
vacation,
but
we'll
see
in
early
January
this
probe
a
shipped
within
the
4th
of
January.
Is
it
4th?
B
Is
it
I
think
it's
both
1st
January?
Isn't
it
Patrick
the
next
special
in
skroob
call
5fx?
Yes,
it
is,
and
I
will
actually
do
a
live
demo
on
the
craft
functionality.
So
we
can
have
a
discussion.
I
can
walk
through
the
process.
I
could
walk
through
the
details,
inside
of
it
as
well
and,
unlike
said,
and
there
will
be
tutorials,
there
will
be
examples.
B
B
Any
news
from
when
managed
metadata
will
be
added
to
the
spbm
via
REST
API.
So
Christiana
has
a
good
question,
so
this
is
the
most
requested
capability
on
the
user
voice.
And
yes,
this
is
actually
highly
requested
capability,
so
technically
it
to
be
able
to
add
that
to
the
VM
PHAs
core,
it
requires
that
there's
a
native
REST
API
to
be
able
to
call
or
if
they're
radically
the
SPP
MBTA
is
good,
call
just
use
the
season
API,
but
that
would
not
be
that
optimal,
because
that
would
be
hacking.
B
We
in
the
ship
on
engineering
which
I
do
represent
as
well.
We
are
looking
into
having
investments
on
the
advance
documentation,
scenarios
for
it
and
the
ECM
scenarios
more
and
more
starting
from
the
second
half
well,
the
first
half
of
next
calendar
year,
starting
from
January
now
will
to
taxonomy
API
is
be
the
first
phase
of
that
ezm
story,
I,
don't
know,
but
it's
coming
relatively
soon.
We
absolutely
understand
that
there's
a
massive
demand
for
that.
There's
also
discussions
on
maybe
the
taxonomy
service
that
they
raised
above
sharepoint.
B
So
it
should
not
be
just
a
ship
one
specific
taxonomy
service.
Maybe
it
should
be
office,
365,
5
or
white,
and
a
taxonomy
service,
and
if
that's
the
case,
then
there
will
be
even
further
delays
on
actually
getting
the
REST
API
is
because
getting
the
taxonomy
service
raised
from
a
shipment
level
to
the
office
365
level
we
or
actually
be
a
big
thing.
It
will
be
I
would
be
highly
beneficial,
no
doubt,
but
it
would
actually
delay
on
getting
the
right
implementation
up.
So
technically,
on
the
JavaScript
p.m.
B
A
So
I've
looked
at
that
and
I've
looked
at
wrapping
the
JSON
stuff
and
it's
something
I'm
a
little
bit
more
open
to
now
that
we
could
have
a
separate
package
that
not
everybody
would
have
to
worry
about,
like
you
could
have
an
app
P
and
P
slash
metadata
or
whatever
we
come
up
with
a
good
name
for
it.
The
the
issue
is
it's
not
pretty
one
and
it
doesn't
so.
We
have
kind
of
that
fluent
API
that
we've
used
throughout
the
libraries
and
it
doesn't
flow
well
in
that.
A
B
A
B
B
So
the
reusable
taxonomy
picker
for
SharePoint
framework
with
parts
is
actually
using
and
exposing
taxonomy
services
to
the
season
AVM
and
in
engineering
with
thought
about
this,
and
basically
we
said:
well,
that's
not
a
way
to
make
that
happen
by
using
the
system
of
rapper
our
faking,
the
BSC
ISM,
and
calling
that
the
end
point
using
a
JavaScript
API.
So
we
do
have
this
implementation
already
in
the
taxonomy
picker.
So
we
could
actually
use
that
one
to
simplify
well,
the
throw
some
conquer
adverb
at
least
reduce
the
work
needed
for
PHAs
core.
B
A
To
jump
up,
pager
is
question
ETA
on
that
release.
Sometime
early
in
the
new
year.
Honestly,
at
this
point,
it's
dependent
on
getting
me
getting
all
the
documentation.
I
can
get
done
done,
but
the
code
because
I'm
a
developer,
so
the
codes
basically
done
and
I'm
just
behind
on
documentation.
So
if
you
want
to
grab
the
beta
versions
off
the
beta
Channel
for
those
libraries,
they're
essentially
code
complete
at
this
point,
so
I
wouldn't
say-
maybe
dropping
them
in
production.
A
B
Coming
back
on
the
previous
questions,
I
think
you
jumped
quite
a
lot
for
there
was
a
question
from
Rodriquez
Sno
Moncada,
an
error
when
trying
to
use
a
new
asset
packaging
capability,
which
is
invalid
shipment
app
package
arab-arab
park.
Url
is
not
valid
for
rules
defined
in
the
open
pockets
convention
specification
now,
Rodriguez
I
haven't
seen
that,
but
what
I
would
actually
recommend
is
to
get
the
repo
steps
to
our
issue
list,
and
this
is
something
for
everybody
in
this
call.
B
So
if,
when
you've
run
into
issues
in
the
SharePoint
framework
and
I
should
have
had
a
slide
on
this
one,
but
that
one
for
the
future
has
been
a
secret
cause,
but
if
we
run
into
an
issue,
you
have
a
question:
you
run
in
the
random
exceptions
in
SPF
X.
Please
go
to
the
issue
list.
Spf
dogs
issue
list.
This
list
is
getting
replicated
to
our
visitor
story
online.
Our
engineers
are
reading
this
and
we
do
have
a
triage
twice
or
three
times
in
a
week.
We
look
into
this
list.
B
We
assign
the
tasks
to
our
engineers
to
investigate
if
there's
problems.
So
this
is
your
shortcut
to
actually
report
and
get
input
from
engineering
by
providing
Danida
to
every
pro
there.
Now
there
will
be-
and
there
has
there's
always
delays
on
getting
things
done
on
build
pls
comment,
depending
on
an
issue.
Typically,
we
should
have
had
labeling,
at
least
for
your
issue,
so
which
indicates
that
it
has
been
touched
so
to
come
around
can
really
if
you're
pasting
the
issue
there.
B
Let's
have
a
look
on
what
it
is
and
I'll
come
back
onto
the
on
duration.
But
every
single
item
in
this
issue
list
is
getting
triage.
Now
we
do
not
have
a
massive
amount
of
engineering
engineering
resources,
which
means
that
we
need
to
balance
the
work.
What
we
do
on
this
issue
list
investigation
with
the
new
functionalities
which
are
apply
into
shape,
so
there
is
always
a
delay,
but
he
is
a
way
of
getting
some
level
of
support,
plus
the
fact
that
community
helps
community
in
this
issue
list
as
well.
B
So
there's
a
lot
of
a
lot
of
answers
and
a
lot
of
resource
are
getting
close
because
other
people
in
the
community
are
helping
and
saying
hey,
good
question,
and
this
is
how
you
actually
make
it
happen.
But
so
please
please
please,
please.
If
you
run
into
critical
issues,
please
use
the
Asia
list.
We
need
to
know
so
we
can
actually
fix
it
fix
the
issues
quickly.
Coming
back
on
the
I
think
that
was
Rodriquez
question,
making
sure
that
we
don't
actually
miss
anything.
That
was
the
metadata
that's
before
tariqas
management
already.
B
Did
it
end
of
the
day
people
are
doing
its
Jason.
Oh
my
point
themselves
now
yeah,
that's
not
that
pretty
exactly
that's
run
the
MMS
management,
other
stuff,
editing
experience
for
SPF,
exfilled
customizers,
that's
so
david
is
asking
around
that
editing
experience
if
you're
building
a
field
customizer
for
shipment
framework
extension-
that
is
only
for
the
reader
on
the
experience,
know
the
editing
experience
is
not
there.
Yet
we
just
changed
the
editing
experience
in
a
modern
list.
B
If
you
have
noticed
that
you
are
no
longer
redirected
to
a
separate
page,
the
editing
experience
is
inside
of
the
list
or
library.
So
you
will
be
actually
in
the
same
context.
Now
that
we
have
done
that
change,
we
are
able
to
start
looking
into
how
to
expose
the
editing
experience
for
filled
customers
as
well.
The
owner
of
the
field
costs
well
owner
of
the
modern
lists
and
libraries
is
aware
of
the
request.
B
Note
8x
support,
and
so
that's
a
good
thing
to
discuss
as
well.
Right
now,
as
pay
effects,
only
supports
note,
6
point
X.
So
if
you're
using
a
node,
8,
X
or
9
X,
you
might
run
into
unexpected,
sits
issues.
The
night
node
8
support
is
something
which
has
been
started
to
being
done
in
engineering
quite
a
few
times,
and
then
people
run
into
issues
and
then,
when
a
ship,
and
then
we
need
to
pride
us
to
shipping
before
adding
the
nodes
8
support,
because
something
were
forced
to
get
ship.
B
B
Good
I
think
that
was
all
questions
which
were
pending
at
least
from
the
past,
unless
I
missed
something
Patrick
did
I
miss
something,
no
I,
think
that's
it.
Okay
and
thanks.
Oh
there's,
a
Philip
answer,
a
question:
I
can
actually
guess
yeah
I.
Remember
this
your
number,
even
so
we
are
looking
into
this
one
as
well.
This
has
been
raised
as
the
internal
priority
pretty
recently,
and
the
status
is
equal
tract,
meaning
that
it
has
been
acknowledged
internally.
B
The
1042
issue
is
seems
to
be
related
and
two
different
things
like
actually,
while
they
comment
at
the
end
in
the
issue
as
well,
so
we
aren't
using,
for
example,
waldek
as
someone
of
the
resource
and
one
of
the
persons
who
are
helping
on
reducing
the
load
for
engineering,
and
he
is
doing
some
level
of
an
investigation
as
well.
So
this
seems
to
be
do
two
different
things.
There
seems
to
be
an
issue
actually
in
our
sample,
which
isn't
super
optimal
and
there
seems
to
be
a
small
issue
in
there.
B
Specifics
related
on
the
handling
as
well.
Right
now,
like
said
for
this
week
and
next
week
and
there's
nobody
in
Richmond
who
can
actually
fix
this
and
we're
not
shipping
anything
because
we're
in
a
freeze
period
and
because
we
don't
want
to
actually
ship
something
two
days
before
Christmas,
because
nobody
wants
to
be
sitting
on
there
on
the
on
Christmas
Eve.
If
somebody's
gonna
call
you
and
ask
you
a
question,
because
here
one
time
I
went
down,
you
don't
want
to
be
that
guy
and
so
we're
not
actually
touching
sharepoint
online
right
now.
B
B
A
Well,
I
just
want
to
say
thank
you
to
everybody
for
a
great
year.
It's
been
a
blast
for
me
and
I
hope.
Everybody
else
has
enjoyed
the
journey
and
look
forward
to
great
things
in
2018
hope
everybody
gets
some
time
off
and
get
to
relax
and
enjoy
not
working
for
a
period
of
time,
but
I
want
to
say
thank
you
for
myself
and
everybody
else
on
the
core
team
for
all
of
you
that
participate
in
these
calls
and
on
the
rest
of
the
work
we
do.
It
really
means
a
lot
to
us.