►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 26th of April. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
A
So
as
always,
we
start
with
a
little
introduction
to
what
this
call
is
all
about.
We
are
part
of
the
larger
SharePoint
patterns
and
practices
program
and
the
reason
we
started.
These
special
interest
group
calls
of
which
this
is
one
and
there's
also
one
for
PowerShell
and
seasaw
managed
code
development
and
we're
on
alternating
Thursdays.
But
we
started
these
because
we
just
had
too
much
material
to
cover
across
too
many
different
areas
to
do
it
all
and
save
the
one
monthly
call
we
used
to
be
doing
so.
A
We
split
out
and
broke
it
out
into
these
calls.
So
we
can
focus
in
this
call
a
little
bit
more
on
an
open
discussion
around
a
SharePoint
framework
and
client-side
development
patterns,
especially
those
related
to
SharePoint,
not
even
necessarily
SharePoint
framework,
but
just
the
ways.
Folks,
approach,
SharePoint
development
on
the
client
side
and
as
well.
We
talked
about
the
PJs
libraries
as
well
as
the
office
CLI
I
should
update
this
slide,
the
office
365
CLI
and
the
reusable
controls
the
react,
controls
for
SharePoint
framework
as
well.
A
So
really
more
of
a
specialized
deep
dive
into
those
topics,
and
then,
of
course,
we
emphasize
the
community
demos
I
think
that's
again,
the
most
valuable
part
of
these
calls
to
links
down
there
at
the
bottom.
Sp
P,
&,
P
community,
will
take
you
to
the
Microsoft
tech
community.
That's
a
great
place
to
get
general
questions
answered
if
it's
not
necessarily
an
issue
specific
to
a
certain
library,
whether
that's
SharePoint
framework,
whether
that's
PJs
or
something
else,
and
maybe
wouldn't
be
appropriate
as
much
as
an
issue
to
that
library.
How
do
I
design?
A
How
would
you
architect
things
like
that
are
great
for
the
Microsoft
tech
community
and
the
second
leg
there
SP
dev
Doc's
takes
you
to
the
SharePoint
developer,
documentation
and
that
is
the
all
up.
Sharepoint
developer
documentation,
so
it's
covering
everything
having
to
do
with
SharePoint
development,
so
whether
you're
new
to
SharePoint
framework
want
to
try
that
out.
For
the
first
time,
you
can
see
that
whether
you
need
to
look
things
up
on
manage
code
development
or
the
add-ins
sorry
provider
hosted
ad
is
been
so
long
since
I've
done
those.
A
My
brain
couldn't
remember
them,
but
all
of
that
documentation
is
there
on
that
site
and
available.
So
do
please
check
it
out.
I'm.
Looking
at
the
comments
and
I'm
distracted
by
the
fact,
we've
all
just
learned,
alt
keys,
sir
agenda
for
today,
engineering
update
from
SharePoint
framework
we've
got
p.m.
A
So
the
QA
open
discussion,
then
at
the
end,
if
we
have
time
and
we'll
see
so
before
we
get
into
the
rest
of
the
agenda,
I
want
to
do
talk
quickly
about
opportunities
to
participate
in
the
larger
patterns
and
practices
program.
And
then
specifically,
this
call.
We
really
encourage
you
and
invite
you
to
come
demo,
both
your
SPF
X
solutions
and
your
PJs
solutions,
or
just
your
SharePoint
related
client-side
development
solutions.
So
those
are
those
are
the
kind
of
things
we
want
to
see
on.
This
call
we've
seen
amazing
demos
over
the
last
year's.
A
Like
it's
been
years
now,
we've
been
doing
this
call
and
really
encourage
you.
So
if
you've
done
some
great
work,
please
reach
out
a
great
question.
How
do
you
reach
out
to
us
you
can
reach
out
to
us
on
Twitter?
You
can
reach
out
to
us
via
the
issues
list,
if
you
find
no
other
way
to
do
that,
but
hitting
us
up
on
Twitter
is
a
great
way
so
either
of
ASA
or
myself
is
that's
a
really
easy
way.
Patrick
scales,
better
I,
don't
know
that.
That's
true
other
ways
to
participate.
A
You
can
contribute
on
github.
So
if
you've,
if
you
found
an
issue
in
any
of
the
PJs
or
the
SPF
X
libraries,
please
report
those
contribute
pool
requests.
We
always
welcome
pool
requests.
We
always
welcome
suggestions
for
enhancing
the
libraries
and
really
do
appreciate
all
that
feedback
from
everyone.
In
the
community
and
then
that
final
box,
there
just
provide
feedback
so
feedback
on
everything,
we're
doing
so.
Feedback
on
these
calls
feedback
on
the
other
work
we're
doing
on
SharePoint
framework
on
things
like
that
and
really
do
appreciate
that
and
take
that
to
heart.
B
B
You
can
yes,
no,
why
did
we
jump
to
the
start?
I?
Don't
understand,
actually
jump
to
their
ride.
Slide.
Sorry,
for
that
there
we
go
so
a
few
things
from
a
trip
on
the
engineering
side
relay
they
don't
show
up
on
the
framework.
You
can
hear
me
right,
Patrick,
it's
up
for
checking,
okay,
so
we've
done
some
work
on
the
documentation
side
and
we
keep
on
evolving
this
one
pretty
soon
we'll
release
a
set
of
scenario-based
documentation
here,
which
is
really
targeted
for
you
to
find
out
as
an
example,
hey
I'm
heading
to
SharePoint
Online.
B
What
is
my
options
to
do
scheduled
tasks
as
versus
server-side
climate
jobs
are
not
available
or
how
would
I
do
ezm
capabilities
in
SharePoint
Online,
so
more
kind
of
a
sign
based
solution
guide
answers
coming
up
pretty
soon.
It
will
be
more
and
more
more
in
more
guidance
related
on
the
modern
customizations
in
here
as
well,
and
we've
done
some
free
work
on
the
on
the
slides
of
structure.
B
B
The
issues
in
here,
one
of
the
classic
ongoing
super
long,
lasting
issues
related
on
events
is
now
is
Phillip
is
on
the
call
I'm
not
checking
the
comments
it
is
finally
now
resolved
and
it
should
be
available
to
fix,
should
be
available
worldwide
related
onto
even
thing
and
SharePoint
framework
extensions.
If
you're
really
into
that
one.
We
apparently
still
have
a
small
challenge
related
on
search
experiences,
and
the
problem
is
that
the
search
experience
is
and
the
search
doesn't.
B
Actually
it
doesn't
have
really
a
more
an
experience
which
would
play
well
with
our
extension,
so
we're
still
working
on
that
one
try
to
get
that
100%
at
bullet
proof,
but
the
classic
problem
with
moving
to
application
pages
or
layout
spaces
and
then
moving
back
on
the
on
the
modern
basis.
And
then
you
would
lose
your
extension.
That
has
been
now
finally
fixed
in
SharePoint
Online.
Now.
B
One
reminder
at
one
of
a
kind
of
advertisements,
so
shipment
conference
is
coming
up
within
a
few
weeks.
I
think
we're
now
three
weeks
or
something
like
that
to
do
the
SharePoint
conference.
Since
your
open
conference,
there's
great
great
great
pre
workshops,
a
see
is
gonna
as
an
example.
Do
a
great
workshop
on
SharePoint
framework
kick-starting
and
getting
started
on
SharePoint
framework
development.
We
from
SharePoint
engineering.
B
What's
coming
up
on
trending
story,
we
go
through
on
the
latest
on
SharePoint
frameworks,
there's
some
pretty
cool
announcements
coming
up
on
that
one
as
well
as
really
really
what's
coming
and
announced
coming
pretty
soon
as
a
new
capabilities
available.
Now
this
is
the
precoded
Day
is
on
Sunday
20th
of
May.
There
is
some
competition
like
mentioned.
This
is
overlapping,
for
example,
with
a
C's
thing.
B
So
please
do
consider
which
one
we
are
going
to
go
and
then
the
actual
conference
is
from
Monday
to
wednesday,
quick
conference
to
get
the
latest
on
SharePoint
overall
right
after
this
one,
by
the
way,
if
you
are
from
Europe
there's
also
the
European
Cooperation
summit
in
Mainz
Mainz
basically
means
Frankfurt
and
that's
a
week
after
Las
Vegas.
So
if
you
don't
want
to
fly
to
Las
Vegas
and
your
based
on
Europe,
then
you
can
go
to
mines.
Me
I
will
be
there
then,
and
then
we'll
be
there.
B
Not
goggle
gun
home,
we'll
be
there
as
well,
and
there
could
be
a
lot
of
MVPs
and
European
cooperation
summit
sharing
the
latest.
What
we've
talked
about
in
Las
Vegas
as
well.
A
lot
of
decisions
in
Las
Vegas,
unfortunately,
are
not
recorded
this
time.
It's
super
pity
because
which
would
be
create
that
this
would
be
recorded,
that
you
would
be
able
to
see
them
afterwards,
but
we
will
absolutely
make
sure
that
we
will
release
webcast
and
training,
videos
and
updates,
and
all
of
that,
all
of
the
new
announcements
in
the
dev
platform
now
other
topics.
B
B
So
this
is
a
really
good
example
of
a
new
documentation
which
has
been
evolving
and
added
on
there
on
the
SharePoint
oxide,
it's
kind
of
cool
the
fact
that
you're
able
to
do
or
load
your
customization
development
development
stuff
on
top
of
the
production
pages,
so
we're
able
to
actually
test
and
see
how
your
web
parts
are
working
and
they're
all
girls,
that
there
is
still
the
workbench
and
everything
else
available
on
the
usage,
so
I've
again
hidden
the
numbers.
So
you
don't
know
what
is
actually
the
numbers
to
use.
B
It's
keep
on
crowing
quite
heavily.
It's
I,
don't
know
why.
But
apparently
Monday
is
the
peak
day
on
Monday
Tuesday,
so
where's
the
big
thing,
and
then
it
goes
slice
it
down
after
the
week
people
are
getting
tired,
I
don't
know,
Friday
is
Friday,
is
actually
a
vacation
day
in
certain
days
in
certain
countries
in
the
world.
So
from
that
perspective,
usage
going
down,
it's
also
understandable,
but
in
general
shape
and
framework
adoption
is
growing
extremely
fast.
Still
we're
looking
into
doubling
these
numbers
pretty
much
by
end
of
June
July.
B
So
it's
it's
growing
insane
offense
on
the
roadmap.
No
new
really
changes
in
here.
So
obviously
we
talked
about
the
site,
design
and
size
script
actions
in
general,
that's
related
on
SharePoint
framework,
but
already
in
view
of
the
previous
community
cause
the
Krupa
Phi
API
story
is
getting
more
and
more
ready.
I
think
this
will
be
actually
released
before
SBC,
if
I'm
not
mistaken.
So
please
check
the
tech
community
and
our
social
media
if
you're
interested
on
that
one,
the
Krupa,
Phi,
API,
documentation
and
also
PowerShell
documentation
is
actually
already
out.
B
So
you
are
able
to
go
and
check
it
out
and
what
will
be
available
for
you
whenever
the
Krupa
fire
functionality
will
be
coming
up,
live
to
your
actual
tenants,
and
then
we
have
super
cool
stuff
coming
up
on
the
SPC
for
some
of
the.
If
you're
coming
in
to
build,
some
of
the
new
announcements
will
be
actually
covered
in
build
as
well.
B
So
you
might
want
to
follow
up
on
the
social
media
on
the
build
announcements
related
on
SharePoint
there's
some
cool
stuff,
which
I
can't
unfortunately
make
in
the
scope,
but
super
cool
super
cool
stuff
coming
out
cool,
but
that's
really
much
quickly
on
my
site.
So
nothing
really
new
you
from
a
shape
of
engineering
side,
because
we're
gearing
up
for
built
and
care
enough
for
SBC
to
give
you
the
really
the
new
announcements
and
many
things
we're
working
on
a
new
version.
B
Obviously,
on
SharePoint
framework,
so
1.5
version
of
SharePoint
framework
is
coming
out
pretty
soon.
I
can't
again
give
you
an
exact
date.
Last
time
we
were
planning
to
get
to
one
point
four
point:
one
out:
it
was
delayed
than
two
weeks
and
do
certain
findings.
So
I
don't
want
to
promise
you
a
date
because
I
will.
It
might
be
that
we
can't
keep
today,
but
one
point:
five
is
coming
out
pretty
fast
and
the
documentation
will
then
explain.
What's
new
inside
of
it.
I
can't
leak
that
yet,
but
Patrick
take
it
away.
So.
A
A
quick
update
today
on
the
click
the
next
button
on
the
client-side
libraries
still
working
on
a
CD
nsj
support
I.
Finally,
our
issue
in
their
repo
has
gotten
some
comments,
and
so
people
assigned
to
review
it
so
I
think
we're
getting
a
little
closer
to
that
getting
pushed
through.
Really
at
this
point,
we
just
need
them
to
merge
it.
We're
still
doing
the
weekly
beta
releases
on
Fridays
and
the
major
releases
will
be
monthly.
That's
unchanged,
please
check
the
changelog
just
to
remind
folks.
A
That's
we'll
be
updating
that
every
time
we
merge
a
change
into
the
dev
branch
will
update
the
changelog
alongside
that,
so
you
can
see,
as
things
are
added
and
we're
working
on
bug,
fixes
and
issues
a
couple
issues
that
are
in
there
right
now
about
adding
support
for
comments
on
modern
pages
and
likes
on
modern
pages.
That's
something
we're
gonna!
A
Take
a
look
at
trying
to
get
into
the
next
version
for
what's
this
month
is
April
for
May,
so
we're
try
and
get
that
in
for
May
release,
but
just
started
looking
at
that
this
morning,
before
the
call
so
we'll
see
how
that
goes.
Do
want
to
remind
folks
SP
p.m.
PJs,
the
last
version
we
will
publish
of
that
is
in
July.
A
So
this
is
just
your
friendly
reminder
to
start
migrating
your
projects
when
possible
and
if
you're
starting
any
new
projects,
would
very
much
encourage
you
to
start
with
the
app
PNP
scoped
libraries,
all
the
same
functionality
and
more
is
there,
and
if
you
have
any
issues,
transitioning
or
migrating
your
projects
over
to
the
new
libraries.
Please
let
us
know
we
want
to
try
and
make
that
process
as
smooth
as
possible,
and
then
we
will,
you
know,
see
what
we
can
do
to
help
you
out
as
well.
Link
down.
A
There
is
to
the
documentation
so
P
and
P
github
io,
/p,
+
PJs
gets
you
all
the
documentation
for
the
new
scoped
libraries,
as
well
as
a
transition
guide
to
move
from
s
PP
and
PJs
to
the
new
libraries
following
the
hashtag
PP
j
s
on
twitter,
and
you
can
follow
me
at
mediocre
bowler
on
twitter
for
all
the
updates.
I
don't
tweet
a
lot,
so
you
won't
get
a
lot
of
spam
or
anything
for
me,
but
you
will
get
updates
about
when
we
publish
betas
or
new
versions
of
things
like
that.
A
So
that's
quick
update
for
the
P
and
P
client
libraries
stepping
now
to
the
office
365
CLI
before
I.
Do
this
again
I'll
see
if
Waldeck
is
on
the
call
I
don't
think
he
is
so
I
will
do
the
update
for
the
office
365
CLI.
Today
we
have
a
new
beta
out
1.2.0,
including
commands
to
get
information
about
modern
pages
and
their
contents,
their
web
parts
etc.
A
Currently
in
preview
authenticating
using
credentials
so
that
be
username,
password
kind
of
thing,
as
well
as
getting
information
about
hub
sites
and
syncing
the
hub
site
theme,
adding
and
removing
list
items
and
removing
files
and
remove
files.
I
think
that's
supposed
to
be
a
second
bullet
point
set
property
bag
values
so
that
stuff
is
in
process
there.
C
That
is
not
you
know,
current
version
so
say
you're
on
version,
1.3,
dot,
zero
and
you
want
to
move
to
the
latest
version
of
it,
we're
working
on
a
command
that
when
you
run
it
it
will
spit
a
report
out
and
say
here
are
the
things
that
you
have
to
do
here
are
the
things
that
you
should
go
look
at
here
are
the
things
that
were
removed
or
added,
etc.
That's
our
p1
and
then
down
the
road.
C
We
will
hopefully
be
able
to
automate
that
as
well,
so
that
you'll
be
able
to
run
it'll
spit
a
report
out,
but
it
will
turn
around
and
also
say:
oh
your
projects
now
updated.
We
just
updated
it
for
you.
We're
gonna
do
this
in
two
stages
that
we
want
to
make
sure
that
not
everybody
has
got
their
their
projects
in
a
source
in
a
source
and
repository
and
source
code
management
SCMS.
So
I
don't
want
to
do
something
that
runs
it
and
main.
C
Was
your
project
and
then
stuff
isn't
working
you're
like
what
was
it
used
to
be
so
we're
gonna?
Do
this
in
two
stages
and
spit
a
report
out
the
first
time
to
make
it
a
little
bit
easier
for
you,
so
Philip
cool
idea
submit
it
to
the
issues
list.
You'll
see
we
got
an
issue
up
there
on
our
repo
and
it's
something
that
we
definitely
want
to
do.
C
I
would
love
to
be
able
to
have
a
report
that
that
will
spit
out
an
issue
list
and
all
that
stuff
for
you
as
well,
but
that's
all
down
the
road
we're
trying
to
currently
working
on
the
the
way
that
we
figure
out
and
inspect
the
project
and
what
needs
to
change
first,
so
amazing
questions
about
that.
I
can
have
I'll
jump
in
and
watch
the
chat
query
as
well.
I
don't
want
to
take
up
too
much
of
Patrick's
time
here,
thanks
Patrick
yep.
A
Don't
know
what
to
call
that
appendage.
On
the
end,
there
will
get
you
the
the
sort
of
latest
published
beta
of
the
CLI
on
the
SPF
X,
reusable
components,
so
these
components
are
published
again
as
part
of
the
PNP
ecosystem
of
things
and
the
first
one
is
a
set
of
controls
that
you
can
use
in
your
SPF
x,
webparts,
and
what
they
do
is
help
you
with
sort
of
reusable
bottled-up,
UI
and
functionality.
So
you
don't
have
to
recreate
these
things.
Necessarily
yourself
for
your
projects.
A
The
first
one,
the
taxonomy
picker
control,
has
been
added
and
those
are
the
associate
issue
numbers
there
off
to
the
right.
There's
a
list
picker
control
now
added
and
some
general
fixes
in
bug
and
stuff
like
that,
have
also
been
incorporated
into
the
controls
and
that's
version,
1
3
0
and
then
for
the
property
controls
which
are
the
same
idea,
reusable
controls,
but
in
these,
in
this
case,
for
the
property
pain
when
you.
A
So
when
you
edit
your
SharePoint
framework,
webpart
you've
got
some
reusable
property
controls
you
can
put
into
that
property
pain
or
that
editor
pane.
Those
are
at
version:
1,
5,
1
and
you've
got
a
color
picker
now
optionally,
returning
color
objects
and
again
some
general
fixes
and
and
bug
fixes
there.
So
if
you
haven't
checked
out
these
controls,
they
are
a
fantastic
way
to
jumpstart
your
project.
A
They're
reusable,
obviously
drop
into
your
project,
NPM,
install
them
and
you're
all
set.
So
save
yourself
a
lot
of
time
and
a
lot
of
effort
there
very
nicely
laid
out,
and
they
will
really
help
you
out
getting
started
with
kind
of
some
of
these
common
sort
of
components
and
controls.
All
right,
so,
let's
jump
into
the
demos.
The
first
one
would
be
lease
lease
if
you're
ready,
hi
guys,
you
kill
me.
Yes,
sir,
you
want
to
go
ahead
and
start
presenting
yeah.
D
You
so
hi
guys,
my
name
is
Luis
and
I'm.
Gonna
show
you
more
about
the
application
station
that
I
don't
working
with
website,
but
before
I'd
like
to
do
a
very,
very
quick
demo.
Introductions
worry
about
the
websites,
so
you
can
see
here
that
I
created
a
marketing
outside
website,
as
you
probably
know,
is
something
that
Microsoft
has
released
some
some
weeks
ago.
So
now
we
have
the
ability
to
create
website
and
as
different
other
side
collections
into
into
the
half
side
in
order
to
create
the
half
side
and
you're
gonna
need
power.
D
D
As
you
can
see
here
with
the
news,
roll
up
roll
up
web
part
so
so
far,
there's
a
flight
instructor
regarding
the
half
side,
meaning
that
you
can
only
associate
the
site
with
a
specific
hot
site
and
you
can't
have
a
hot
site
inside
another
another
half
site.
So
for
now
is
yes,
the
flattest
structure
you
can
see
here
at
the
person
out-of-the-box
sites
web
part.
That
is
so
mean
the
different
sites
that
are
inside
this
marketing
half
site.
In
this
case,
I
have
four
sites
inside
and
but
I
thought
that
would
be
cool
too.
D
D
D
You
can
see
how,
in
the
feather,
there's
a
drop-down
with
the
same
four
sides
that
are
here
and
I
can
jump
directly
into
into
the
side,
as
you
can
see
clear
and
also
the
extension
is
ready
in
the
render
they
drop
down
when
you
are
in
a
subpoena
subside.
So,
for
instance,
this
is
a
I
know
hub
sype
site.
So
if
I
refresh
the
page,
even
with
the
witnessed
as
you're
running,
there's
nothing
there's
nothing
in
the
feather,
because
this
is
not.
D
This
is
not
a
half
site
so
how
we
can
get
this
information,
the
sub
sites
that
are
inside
instead
of
outside.
Well,
we
can
use
search
honestly
and
there's
a
nice
article
from
Michael's
Benison,
explaining
how
you
can
run
some
search
queries
in
order
to
guess
to
get
these.
The
sides
that
are
inside
inside
a
hot
site
but
thing
is
that
I
realized
that
there's
a
uninterested
and
undocumented
API,
and
that
is
given
us
some
information
about
the
sub-site,
so
I
was
just
curious.
Ally
and
I
gave
it
a
try
and
is
working
fine.
D
So
here
in
the
in
the
network
tab
you
can
see
that
their
circle,
two
sides
have
feed
ten-point.
So
you
are
said
in
the
you
can
say
the
department
ID.
This
is
the
grid
of
the
site,
that
is
the
half
side,
and
this
is
giving
us
the
same
information
they're
the
items
that
are
inside
a
half
site
also
including
the
half
site,
the
half
side
itself,
as
you
can
see
here,
marketing,
half
site
they're
different
different
sites
inside
the
half
side.
D
However,
note
that
this
API
is
not
inside
the
SharePoint
there's
some
other
way
of
mind
was
Europe
three
years
before
Manila
and
finish
that
to
call
this
API
you're
gonna
need
a
specific
little
token,
as
you
can
see
here
and
meaning
that
you
can
call
this
API
directly
using
the
SP
HTTP
client,
but
curiously
there's
another
API.
That
is
inside
certain
point.
You
can
see
here,
there's
SP
home
service
context
and
you
can
expand
token
and
that's
gonna,
give
us
a
specific
access.
D
Token
access
token
that
you're
gonna
be
able
to
use
to
get
the
information
from
the
other
from
the
other
API
and
also
there
are
a
couple
of
your
mind
here
that
you
can
use
to
compose
the
URL
of
the
of
the
other
API
to
get
the
hobby
information.
So
basically,
what
I'm
doing
is
just
calling
this
qu
API
is
from
the
from
the
extension.
So,
let's
jump
into
into
the
code,
so
I've
created
an
application
customizer
here.
D
So,
as
you
saw
in
the
only
need
we
are
calling
the
render
placeholder
and
what
we
are
doing
here
is
creating
a
specific
place
holder
using
a
placeholder
provider
that
is
provided
as
part
of
the
of
the
context
and
in
this
case
I'm
creating
the
a
placeholder
into
the
top.
It
just
means
the
header
of
the
other
side
and
then
once
the
placeholder
is
creative,
we
are
just
injecting
the
the
react
component
that
is
rendering
the
drop-down.
D
This
property
also
has
value
and
the
value
is
there
is
the
half-site,
the
idea
of
the
side?
That
is
the
half
side.
So,
in
order
to
know
if
this
is
a
half
site
or
not,
we
can
call
this
have
site
ID,
but
then
we
have
to
check
if
the
value
is
the
same
value
that
the
site
ID,
because
in
this
case
it
means
that
is
the
half
site
itself.
So
in
this
case,
is
the
FAFSA,
so
there's
another
function
to
get
the
token.
D
So,
as
I
showed
you
before,
using
these
SP
home
service
context
is
fun
token,
we
can
get
the
specific
access
token
to
come
to
the
hub
API
and
then
finally,
we
are
calling
the
sides
with
API
in
this
case
and
just
our
code
in
the
URL,
but
as
I
showed
you
before,
we
can
get
this
value
also
from
there
from
the
previous
API.
So
in
the
department
ID,
we
are
sending
the
site
ID
from
the
from
the
context.
D
So
this
is
going
to
give
us
all
the
on
the
sides
inside
a
half
site,
as
you
can
see,
we
have
to
set
the
specific
feathers.
The
dealer
token
in
the
in
the
authorization
header
and
also
this
API
needs
to
use
to
to
have
another
feather
con
SP,
homemade
API
context,
and
the
value
is
just
on
the
screen
with
the
portal
URL,
pointing
to
the
absolute
URL
of
the
other
side.
D
As
I
said
before,
nothing
is
documented
about
this
API,
so
I
just
find
found
out
all
this
information,
just
testing
and
I'm
trying,
but
with
just
these
two
feathers
is
enough
to
call
the
API.
So
we
are
calling
the
API
using
the
HTTP
client,
and
then
we
are
just
map
in
the
the
information
to
my
custom
interface,
with
a
different
properties
and
finally
I'm
just
removing
the
half
side
from
the
from
the
collection
service.
We
just
want
to
jump
into
into
our
site
at
the
insight
website,
but
not
notice
how
the
website
itself.
D
B
Which
is
absolutely
correct
so
now
there
is
a
reason
why
we
wanted
to
cover
this
as
the
demo.
So
there's
two
things.
Obviously
the
idea
is
crate
from
Luis
and
the
functionality
is
kind
of
cool
and
flip
between
the
sides
and
the
request
and
the
requirement
for
the
behavior
absolutely
makes
sense.
Now
the
API
which
is
used
here
is
non
documented.
It's
meanst
unsupported,
so
because
it
hasn't
been
documented
anywhere.
B
We
haven't
covered
it
that
in
the
documentation,
it
basically
is
unsupported
and
we
can
change
that
API
in
a
given
day
and
that's
really
the
key
reason
why
I
wanted
to
actually
have
this
demo
covered
here.
It's
a
cool
functionality
absolutely,
but
since
it's
using
an
undocumented
API-
and
you
should
be
considering
this
more
as
a
technical
demo
and
potentially
something
a
little
bit-
will
have
a
third
party
API
in
the
future.
B
If
we
can
show
the
demand
for
the
third
party
API-
and
that's
really
one
of
the
key
points
in
all
of
this
stuff
as
well,
and
so
that
there's
a
significant
amount
of
investments
currently
going
on
on
SharePoint
as
a
platform,
one
of
those
investments
are
actually
going
to
go
for
first
party
requirements
and
first
party
with
bots
and
so
a
lot
of
the
feature,
crew
and
free
to
PMS.
They
concentrate
on
having
a
cool
for
its,
for
example,
let's
say:
SharePoint
homepage
the
SharePoint
home
landing
page
or
some
of
that
of
the
rocket
pods.
B
They
don't
necessarily
even
remem
the
thing
about
the
requirement
of
the
development
experience
and
that's
something
where
we
need
you
to
people
in
the
audience
who
are
in
this
community
call,
or
also
watching
this
video
recording
later
and
to
submit
first
of
all,
first
of
all,
reporting
potentially
issues
on
the
caps
and
then,
if
it's
actually
in
an
enhancement
or
a
gap
in
our
API
surface,
then
creating
a
user
voice
entry
in
a
user
voice.
So
we
can
actually
show
the
demand,
for
example,
right
now
in
the
user
voice.
B
By
far
the
number
one
request
is
the
taxonomy
REST
API,
which
is
having
1226
quotes
unless
somebody
just
wrote
it
on
that
one
as
well,
so
having
that
Amanda
for
having
few
hundred
votes
on
a
PR
request,
for
example
hey.
We
need
to
have
all
of
this
stuff
which
Luis
demonstrated
in
here
exposed
in
a
supportive
API.
If
we
can
show
the
demand
as
a
community,
then
we
will
now
I
put
my
engineering
hat
on
now.
Then
we
in
SharePoint
engineering.
B
We
actually
know
that
there
will
be
people
using
this
API,
and
that
means
that
we
will
then
offer
document
that
supported.
Api
is
for
those
capabilities
super
important
now
the
taxonomy
one.
Let's
talk
about
that,
one,
for
example
in
the
Q&A
one.
Would
you
have
certain
solutions
on
that?
One,
the
next
webcast
and
we
have
certain
thinking
on
that
one-
there
will
be
eventually
a
taxonomy
REST,
API
I'm,
not
I,
can't
go
too
technically
technical
details
why
that
has
not
yet
happened,
but
now,
how
would
I
put
it
personally?
B
I
can
see
it
already
in
a
horizon,
so
it
is
coming
sooner
or
later
now.
Luis.
Thank
you
for
this
one
and
not
taking
anything
away
from
Louis's
or
some
demo
and
awesome
reverse
engineering
on
what
has
been
what
what
is
actually
possible
on
the
platform.
So
we
just
need
to
make
sure
that
we
as
a
community,
also
inform
the
engineering,
for
example.
B
People
like
me
and
share
from
the
engineering
on
the
demand
using
official
channels
so
sending
me,
for
example,
a
Twitter
tweet
or
an
email
saying
we
really
need
to
have
this
API,
that's
not
actually
productive.
That's
not
the
right
way
of
reporting
to
demanding
man
should
be
reported
using
the
user
voice.
So
we
can
actually
then
show
that
there's
300
other
people
who
are
asking
for
this
API
is
there's
clearly
a
demand
for
it.
B
Let's
actually
fix
that
cool,
let's
actually
move
on
to
a
fine
and
let's
absolutely
have
a
Q&A
Q&A
and
then,
as
the
busting
side
note,
if
you
send
an
email
with
starting
with
dear
vissa,
that
doesn't
mean
actually
have
I
pass.
Something
like
you,
sir
okay,
but
I
think
we
had
a
who
was
the
second
one
on
the
demo.
B
E
I'm,
a
SharePoint
developer
of
currently
working
at
McConnell
health
started
with
SharePoint
from
around
2007
version
bounced
around
the
globe
for
a
people
now
settled
in
Canada
nice
to
meet
you
all.
Thank
you
for
having
me
and
I
wanted
to
talk
about
the
extending
the
site
pages
librarian
with
more
fields.
Ways
and
the
main
challenge
with
what
we
have
now
is
content
type
is
sealed.
E
If
we
go
there
and
try
to
add
some
more
cones,
for
example,
and
so
what
we
can
just
go
ahead
and
use
the
MD,
PowerShell
or
or
any
other
way
to
to
programmatically,
add
them
there.
It's
just
that
they
will
not
be
able
to
see
him
in
the
user
interface
if
a
person
can
go
to
the
just
bejust
library
and
try
to
ovulate
that
from
ordinary
out-of-the-box
user
interface,
and
that's
where
some
additional
code
would
go
along
with.
E
So
let's
say
we
got
those
counts
somehow
into
into
our
site
pages.
In
my
case,
I
just
use
the
pinky
PowerShell
and
you
can
then
start
populating
them.
So
one
easy
way
without
any
kind
of
extensions
you
just
to
go
to
a
view
which
is
not
grouped
by
anything
so,
for
example,
all
pages
and
in
there
we
can
use
quick
edit
and
that
would
be
enough.
But
who
wants
that?
E
First,
the
demo
that
sorry,
the
site
pages
library
and
just
to
demonstrate
that
we
can
switch
to
all
pages
without
group
view
and
just
use
the
quick
edit
and
in
my
in
my
case
the
columns
are
not
actually
managed
in
at
the
data.
They
are
playing
lookups
single
value
lookups
to
other
fields
to
analysts
it
is,
it
can
be
multiple
value
lookups
as
well
my
code
in
support
tests,
and
so
that's
not
actually
the
main
point
here.
E
Let's
go
back
to
the
default
by
author
list
and
try
to
kick
the
role,
and
we
see
that
there
there
is
my
command
set
extension
and
if
we
click
there
to
just
load
the
dialogue
and
and
wait
for
all
the
metadata
to
be
fetched
and
present
us.
So
how,
however,
mania
lookup
fields,
basically
I
would
have
in
the
site
pages
vibrating.
It
would
try
to
list
them
all
and
after
its
I
think
it
will,
it
will
actually
encounter
a
lookup
threshold
and
and
version
1
fail.
E
But
since
I'm
presenting
version
2,
it
will
do
as
many
requests
as
as
needed
to
fetch
all
possible.
Perhaps
you
might
have
for
some
reason
if
you
decide
to
do
that,
I'm
using
react.
So
obviously,
if
I
flick,
basically,
that's
the
tactical
control
and
I
can
try
to
start
tithing
info
just
office
just
based
on
what
is
there
and
if
I
would
have
my
multi
lookups
fields
here.
It
would
allow
me
to
continue
populating
value.
It
just
does
not
allow
me
anymore.
E
E
E
E
Let's,
let's
investigate
what
are
the
properties
here
and
I
must
apologize?
The
properties
will
not
take
effect.
Some
of
them
at
least
will
not
take
effect.
My
think
that
by
Python
I
will
need
to
refresh
the
page,
but
that's
just
technical
demo,
and
if
you
are
interesting
in
the
solution
it
is,
you
will
be
available
on
those
VFX
github
repository
with.
In
the
example
section
I
think
you
have
the
pull
request
button
so
I'm
not
sure
if
it
has
gone
through
or
not,
but
I
hope.
E
And
regarding
the
refiners,
how
I
call
them?
Basically,
those
look
up
lists,
look
up
the
fields
those
would
be
listed
here.
When
we
open
up
the
configuration
panel,
it
actually
does
a
request,
a
synchronous
requests
to
fetch
all
of
them
and
list
there
and
I
allow
basically
two
two
modes:
if
I
just
take
it
in,
don't
specify
anything
here.
E
Publish
and
yeah
that's
it.
My
ship
also
also
the
Clear
button
works.
Of
course,
I
think
I
showed
that
and
I
guess.
One
more
thing:
I
tried
to
remain
there
apart
as
responsive
as
possible
in
the
design,
so
I
would
to
collapse
the
browser
a
bit
and
the
they
should
jump
one
under
the
other.
But
let's
see
if
I
can.
E
E
It
then
becomes
responsive.
So
why
should
we,
you
know
the
best
time
in
making
our
own
components
if
we
might
want
to
reuse
something
that
looks
amazingly
the
same
as
the
rest
of
the
sharepoint.
So
that's,
that's!
Basically
what
I
wanted
to
show
and
the
result
of
code
there,
but
you
can
give
you
eat
on
your
own
leisure
when
becomes
available
as
part
of
the
story
and
any
questions
just.
A
E
B
Related
on
the
on
premises,
so
I
quickly
through
a
quick
PowerPoint,
a
slide
on
it.
If
I
get
this
slide
moving
on
those
come
on,
that's
not
the
slide.
Let
me
see
it's
in
the
manage
content.
It's
still
uploading
and
it
is
flipping
that
right
now
so
so
touch
ask
around
a
ship
on
2016
support
and
the
ship
one
frame
of
support,
and
we
talked
about
the
shipment.
2019
support,
so
I
think
it's
worthwhile
to
clarify
and
what
will
be
supported.
What's
the
probability
of
getting
an
updates,
for
example,
for
SB
2016
and
the
experience.
B
So,
let's
see
if
we
can
get
this
slide
on
the
other
side,
unreal
come
on.
It's
not
that
complex
slide
it
isn't.
It
really
isn't
do
I
need
to
show
it
from
my
screen.
I
can
show
it
from
my
screen.
That's
fine
as
well!
So
let
me
share
my
screen
my
primary
screen.
When
I
have
three
screens,
you
need
to
be
careful
on
which
one
you
actually
share
and
somebody
needs
to
confirm
whenever
my
screen
is
available.
B
Talking
sweetie
subscribe,
probably
helps
cool,
okay,
a
cigarette
excellent,
so
that's
the
means
that
other
people
caught
it
most
widely
as
well.
So
if
we
think
about
the
shipment
framework
and
SharePoint,
let's
say
the
version
so
obviously
back
in
whatever
timeframe
phone
premises.
I
can't
remember
when
this
was
this
was
early
2016
and
wasn't
it
almost
more
than
a
two
years
ago
we
released
SharePoint
2016,
or
was
it
even
earlier
than
that?
I
can't
remember
anyway,
as
part
of
that
Chevonne
2016.
B
That
was
really
is
still
kind
of
almost
on
in
line
with
2013
in
user
experience
and
then
at
some
point
we
started
pushing
out
more
on
experiences
in
SharePoint
Online.
Now
in
SharePoint
Online
we
released
first
a
pre
version
than
1.0
version
in
25th
of
February
2017,
and
then
the
1.1
version
was
the
one
which
we
actually
poured
it
back
to
ship
on
2016.
B
So
we
basically
said
that
as
part
of
the
feedback
to
Siwon
2016
feedback,
we
will
support
ship
on
framework
1.1,
which
will
then
enable
modern
web
parts
in
on-premises,
which
is
a
great
thing.
Obviously,
because
then
you
can
build
SharePoint
framework,
1.1
customizations
and
they
will
work
both
on
premises
and
also
online.
Now
and
I'll,
come
back
on
the
immediate
logical
question
for
our
question
on
that
one.
B
Actually,
I
can
probably
say
that
it
was
pretty
recent
work
on
the
SharePoint
framework
or
the
whole
code
of
SharePoint
Online,
and
then
we
start
polishing
and
making
sure
that
it
works
in
on-premises
properly
without
to
have
the
dependencies
to
the
cloud,
because
on-premises
customers
cannot
have
a
dependency
on,
let's
say,
office,
racist
first
idea.
So
whenever
that
fork
happens,
Japan
framework
was
at
the
version
of
one
point,
four
point:
one
which
is
the
latest
version
also
for
SharePoint
Online.
B
So
you
can
kind
of
an
assumed
that
the
capabilities
which
are
in
one
point
four
point
one
will
be
supported
in
on-premises
with
certain
exceptions,
because
now
that
the
the
problem
of
this
one
is
really
and
that,
for
example,
the
one
point
four
point:
one
acid
packaging
or
the
CDN
hosting
has
a
dependency
on
office.
365
Syrian
and
you
do
not
have
that
in
on-premises.
So
we
can't
really
ship
that
or
it
might
be
optional
shipping
off
that
one
as
part
of
the
one.
A
I'll
jump
back
to
the
slides
and
we'll
start
to
close
out
the
meeting
and,
let's
face
it,
gets
back
on
quickly.
So
I
want
to
thank
Louise
and
Oleg
for
those
fantastic
demos
really
great
stuff
and
like
I
said
before,
if
you
would
like
to
demo
on
this
call
absolutely
welcome
and
invite
you
to
do
so.
Just
reach
out
to
myself
on
twitter
at
mediocre,
bowler
very
happy
to
get
you
on
the
schedule.
A
A
Jumping
back,
this
did
not
get
updated.
Sorry
about
that,
so
our
next
SPF
XJS
meeting
will
be
May.
10Th
May
10th
is
the
next
SPF
X
J
s,
Sig
call
the
next
drought,
general
Sig
call
will
be
May
3rd,
so
I
hope
to
see
folks
on
those
calls
they
say
I.
Imagine
you
would
like
to
finish
your
thoughts.
Yeah.
B
So
but
basically,
I
think
it's
pretty
logical
what
is
actually
getting
shape,
where
is
it
getting
shipped
and
on
2019,
and
we
will
support
modern
experiences,
the
standard
library
at
least
10
pages,
and
therefore
you
can
actually
build
extensions
in
there
now
reality
is
that
whenever
the
2019
will
be
shipped
and
there
is
already
a
new
operations
available
shipments
online,
this
is
just
given
the
cloud
moves
faster,
then
on-premises,
because
we
can't
update
your
on-premises
without
you
as
permissions
to
do
that.
That's
C,
Hughes
and
shipment
as
service
packs,
huge.
B
Anyway,
on
SPC,
there
will
be
absolutely
more
information
on
all
of
this,
and
this
slide,
which
you
saw,
was
quite
speculative.
Well,
it's
not
really
speculative,
it's
just
explaining
how
things
actually
work,
and
hopefully
that
opens
up
the
the
thinking
on
how
do
we
ship
stuff,
if
there's
any
urgent,
urgent
questions
and
AC
I
do
apologize
if
I
took
all
the
time,
but
hopefully
I
answer
some
of
the
questions
already
in
there
in
there,
as
we
were
chatting
on
the
iron
window,
any.
B
B
Well,
technically,
if
it's
anything
related
on
timelines,
anything
related
on
is
this
gonna
be
supported
when
we
can
TV
edit
SBC
is
really
when
we
announced
new
stuff
and
more
details
around
the
stuff
which
might
be
in
the
roadmap
pages
right
now.
So
we'll
update
the
roadmap,
also
slides
after
that,
but
I
think
that's
pretty
much
it
anything
new
recording
pending.
Okay,
we
have
two
minutes
on
modern
I.
B
B
Any
news,
unloading,
external
libraries,
multiple
glands
issue-
would
love
to
have
built.
Yes,
the
the
library
thinking
is
SPECT
out.
It
is
now
waiting
for
resources
to
get
implemented.
So,
let's
see
when
it's
actually
getting
packaged
most
likely,
unfortunately
not
in
1.5,
but
eventually
in
the
next
version.
I
think
we're
running
out
of
time.
Patrick
any
last
words
for
this
community
call,
no
cool.
So
thank
you,
everybody
for
joining.
Thank
you
for
your
questions.
Thank
you
for
your
input.