►
Description
In this video we cover the latest with SPFx, the release of 1.0.5 of the JS Core library, and demo new supported functionality in 1.0.5 as well as a pattern for "elevating" calls from the client side using a provider hosted add-in. Detailed agenda and covered topics is available from https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Patterns-amp-Practices-JavaScript-Special-Interest/m-p/22202#M655.
A
Hello
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group
weekly
or
bi-weekly
meeting
it's
October
13
2016
on
Patrick
Rodgers,
Senior,
Program
Manager
its
office,
you
65,
I'm
joined
by
mesa.
You
Bonin
also
I,
think
your
title
is
still
Senior
Program
Manager,
but
now
with
the
onedrive
for
business
and
SharePoint
engineering.
Is
that
correct?
That
is.
A
So
we
got
I
think
a
really
good
meeting
or
call
this
week
for
everybody,
a
couple
of
good
demos,
we're
going
to
talk
about
the
105
released,
and
then
we
got
some
great
sort
of
a
demo
around
kind
of
the
concept
of
elevating
permissions
from
client
script.
Obviously
we're
not
doing
it
directly
in
the
browser
but
sort
of
the
patterns
to
follow
to
solve
the
same
sorts
of
problems
that
we've
solved
in
the
past,
with
elevated
permissions,
but
first
a
little
bit
about
who
we
are
and
what
we're
doing.
A
This
is
a
special
interest
group,
part
of
the
larger
sharepoint
patterns
and
practices
program,
and
we
realized
it's
been
almost
probably
a
year
now,
I
think
we've
been
doing.
The
special
interest
group
calls
that
we
realized
that
the
patterns
and
practices
program
had
gotten
sort
of
so
large
and
had
so
many
different
areas
of
interest.
It
would
be
impossible
to
kind
of
cover
them
in
sort
of
one
call
there's
just
too
much
going
on
so
we
started
this.
A
This
is
a
great
opportunity,
we'll
talk
about
this
a
little
bit
later
as
well,
if
you've
written
something
in
the
SharePoint
framework
and
would
like
a
chance
to
show
it
off
to
the
community
just
get
in
touch
with
us
and
we'll
be
very
happy
to
give
you
a
slot
to
demo
what
you've
done
on
this
call.
I.
Think
that
really
helps
the
community
learn
from
each
other
and
see
the
cool
stuff
folks
are
doing.
I
know,
I,
always
learn
a
little
bit
when
I
see
what
different
people
have
done
with
the
stuff.
A
So
it's
it's
really
cool
to
see
what
people
come
up
with,
because
it's
not
always
things
I
necessarily
would
have
thought
of
myself
and
the
other
part
of
this
call
is.
We
do
talk
about
the
JavaScript
core
component
and
building
that
evolving,
that
in
line
with
SharePoint
framework
and
how
to
benefit
the
SharePoint
framework,
as
well
as
those
scenarios
so
running
it
in
node
or
running
it,
possibly
a
ensure
point,
but
not
using
the
SharePoint
framework,
which
is
becoming
less
and
less
of
a
use
case.
A
Does
the
SharePoint
framework
gets
closer
to
GA,
but
it's
still
an
area
we
do.
You
know
what
I
give
some
attention
to
as
well.
Two
great
ways
to
get
involved
join
us
at
the
SharePoint
community,
which
is
now
tech
community
at
microsoft,
com
or
use
that
akms
link
that
will
take
you
to
the
right
spot
and
then
also
dev
office.
A
Calm,
/
sharepoint
is
sort
of
your
landing
page
now
for
all
things:
sharepoint
development,
whether
it's
the
sharepoint
framework
or
sort
of
see
some
stuff,
all
those
sorts
of
things,
that's
kind
of
your
one-stop-shop
for
sharepoint
development.
So
that's
kind
of
what
we're
all
about
here
in
the
JavaScript
specialist
group.
So
let's
talk
about
what
we're
going
to
go
over
this
week,
we've
got
some
from
based
on
the
latest
updates
around
SharePoint
framework.
I.
A
But
waldeck
will
tell
us
all
about
that,
and
it
will
have
time,
of
course,
at
the
end
for
open
discussion,
questions
QA.
You
can
of
course
ask
your
questions
in
the
IM
and
we'll
do
our
best
to
answer
those
as
we
go,
but
we'll
try
and
leave
some
time
at
the
end.
For
a
you
know,
open
discussion
folks
can
come
off
mute
and
ask
their
questions
directly
to
the
team,
so
getting
in
the
SharePoint
framework
I'll
hand
this
over
to
visa.
To
give
us
some
updates.
There.
B
Thank
you,
I'm
going
to
take
over
us
and
/
sender,
few
updates
on
this
side.
So,
let's
see
when
it's
actually
loading,
so
I
can
control
that.
So,
first
of
all
the
neutral
it's
been
a
while,
since
we
did
a
SharePoint
framework
truck,
it's
been
three
or
four
weeks
because
we
stabilize
the
situation
for
ignite
and
we
do
want
to
actually
release
anything
which
would
actually
pray
stuff.
So
the
neutral
number
five
will
be
Alps.
B
I
would
estimate
today
or
tomorrow,
and
so
it's
gonna
come
out
relatively
soon,
so
have
a
look
on
the
social
media
communications,
especially
Twitter.
It's
either
me
off.
Instead
B&B
or
office,
dev
Twitter
accounts,
which
we
use
all
communications,
more
visible
and
I'm
going
to
meet
somebody
from
here.
Thank
you.
So
the
truck
number
five
who
is
going
to
come
out
and
let's
talk
about
that
one
in
a
second
as
well-
did
I.
Oh
I,
have
an
interesting
animation
here.
B
So
trove
number
climb
is
coming
out
soon,
sharepoint
landing
page,
just
to
make
sure
that
everybody
is
aware
of
this
once
again,
I'm
going
to
repeat
this
in
every
call,
delta.com
/a
point-
and
this
contains
tutorials
and
all
future
technical
topics.
So
we
will
use
this
as
the
landing
page
for
all
the
documentation
which
is
coming
from
this
moment
forward
and
we're
going
to
release
more
and
more
articles
and
documentation
from
engineering
as
well
in
this
location
in
the
future.
B
B
What's
the
responsive
at
what
story
spread
that
the
community
responsive
framework
yeah,
give
me
once
again,
so
no,
not
actually
online
I
need
to
go
to
the
poor
request
and
have
a
look
on.
So
how
do
you
use
bootstrap
to
actually
make
your
make
your
client
side
back?
Part
responsive,
it's
a
great
article,
but
this
is
a
good
example
of
an
area
which
we
do
not.
Actually,
we
cannot
take
it
directly
within
the
official
product
documentation,
because
our
official
recommendation
is
true.
B
The
product
is
that
people
will
be
using
interface,
UI
peppery
from
a
consistency
perspective.
Now
that
does
not
mean
that
you
would
not
be
able
to
use
bootstrap.
You
can
absolutely
use
bootstrap
within
your
client
side
brake
parts,
but
we
want
to
kind
of
keep
this
dislocation
as
of
official
microsoft,
recommended
patterns
and
also
the
approaches
how
to
do
stuff,
so
we're
working
on
that
guidance
sooner
or
later
to
be
included
in
the
documentation
around.
What's
what's
going
to
be
available
for
what
we
are
willing
to
take,
that's
official
documentation.
C
So
I
open
them
yeah.
If
I
may
ask,
would
it
be
an
idea
that
before
you
start
on
your
own,
to
write
dogs
too,
for
example,
to
raise
an
issue
on
which
we
could
all
agree
that,
yes,
we
need
that
topic
and
well
what
you
would
include
and,
and
then
once
all
of
that
is
approved,
you
would
go
and
ride
the
dogs
and
then
you'll
be
merged
right.
So
that
way,
those
don't
be
a
waste
of
time
and
effort
on
every
one
side.
True.
B
I
think
it's
a
if
if
people
are
aware
of-
and
maybe
we
should
actually
are
the
documentation
in
a
way
that
they
had
a
issue,
your
such
as
the
no
no
documentation-
that's
great
out
here
actually
and
then
we
can
have
a
discussion
on
okay,
that's
fine
and
please
do
write
it
will
submit
in
and
we'll
get
the
documentation
for.
That's
a
really
good
enhancement.
B
I'm
going
to
write
that
down
somewhere
in
my
one
notes
and
we're
going
to
have
a
discussion
with
other
people
in
in
redmond
from
that
good
point
and
then
on
the
moving
on
on
things,
because
we
want
to
make
sure
also
that
we
had
time
for
the
demos.
So
there's
multiple
new
samples
and
webcasts
available
I
do
have
a
list
of
them
actually
coming
up
soon
quickly
on
a
ship
on
framework
and
I
drop
five.
B
So
this
is
going
to
be
released
like
mentioned
pretty
soon,
so
we're
waiting
for
the
server-side
deployment
to
hit
one
hundred
percent.
And
after
that
we
cannot
release
the
NPM
packages
and
freed
me
files
and
all
that
and
one
of
the
big
things
around
the
top
five.
Is
that
we're
moving
into
typescript
too,
because
types
of
Scripture
is
now
life
or
in
GA
or
rtm
whatever.
We
want
to
call
that.
B
So
all
of
the
SharePoint
framework
elements
have
been
upgraded
to
the
applied
scripture
and
the
comment
from
the
engineering
side
or
the
dice
were
actually
doing
this
in
practice.
But
it
was
actually
surprisingly
easy
thing
to
do
and
which
is
say
a
which
is
a
good
thing
and
we'll
give
some
guidance
on
the
on
how
to
upgrade
your
existing
web
parts
and
how
to
do
that
as
well.
B
Obviously,
I
fabric
react
has
been
upgraded
to
version
0.5
to
this.
Numerous
improvements
and
changes
in
the
base
classes
work
with
kind
of
a
shuffling
certain
things
around
within
the
framework,
so
making
sure
that
they're
in
final
locations,
so
the
packets
they're
in
the
right
packages
and
so
we're
not
going
to
change
them
after
the
the
top
five.
Well,
who
knows
we're
still
in
dev
preview,
but
that's
objective
and
we,
they
will
say
an
issue
in
technical
template.
B
So
if
you
wanna
write
your
client-side
web
parts
using
knock
out
that
there
was
an
issues
with
that,
one
on
the
top
five
or
so
pre
sorry
previous
drops
and
those
have
been
fixed.
So
that's
a
big
plan
as
well
and
we
are
looking
into
also
updating
the
existing
samples
to
the
top
five
sooner
or
later
so
that
from
a
demo
perspective.
So
from
Nigel's
comment
from
a
video,
let's
say
webcast
perspective:
we're
not
going
to
upgrade
any
of
the
existing
webcast.
B
Now
we
will
absolutely
rerecord
tutorials
and
let's
actually
have
a
list
on
on
those
things.
So
the
videos
on
right
side
and
webcasts
disa,
just
the
latest
webcasts,
which
we
have
available
for
sharepoint
framework
and
all
of
these
are
with
me
and
well
deck.
Then
there's
the
sharepoint
framer
of
tutorials,
and
this
is
a
five-part
series
where
we
actually
explain
how
to
build
a
bit
part
and
all
of
that
and
that's
built
if
I
remember
correctly,
on
top
of
trop
one.
B
So
it's
about
time
that
we
actually
upgrade
those
videos
and
I'm
going
to
work
on
that
next
week.
So
we're
looking
into
having
that
updated
set
of
videos
then
available
within
a
few
weeks
or
maybe
end
of
next
week.
There's
a
lot
of
older
videos
and
webcasts
available
as
well,
but
from
a
resourcing
perspective
and
scheduling
perspective.
It's
just.
We
cannot
obviously
go
back
and
we
record
all
of
these
webcasts.
That's
not
a
sustainable
model.
So
we're
not
going
to
do
that.
B
We
kind
of
keep
on
upgrading
our
stuff
to
the
latest
web
cast
or
latest
version
and
then
place
a
webcast,
and
maybe
maybe
we
should
actually
pinpoint
or
worse
diversion
in
the
videos
which
were
using,
which
is
good
practice
as
well.
On
a
sample
sites,
so
we
do
have,
is
it
12
individual
samples
already
in
the
repo,
so
we're
looking
into
expanding
the
set
of
sample
still?
B
So
as
an
example,
if
you're
looking
into
a
new
dimension
on
office
craft,
let's
add
that
web
part
on
the
existing
sample,
or
rather
than
implementing
another
office
craft
craft
integration
sample
into
repo
the
new
web
parts
here
is
the
react
usher
ad
with
API,
which
is
in
the
death
cramps
right
now,
so
that's
showing
how
to
actually
call
a
sacred
ash.
Your
ad
wet
API,
using
client-side
web
port.
There
are
certain,
let's
say
things
to
be
aware
of
that
and
we're
looking
into
releasing
our
article
around
up
on
as
well.
B
There's
the
reactors
be
elevated
privileges
which
small
deck
is
going
to
demonstrate
later
today.
Well
on
this
call
within
a
few
minutes
and
then
there's
react
to
do
basic,
which
is
actually
really
great
web
part
coming
from
checks
and
that's
kind
of
a
simplified
to
react
web
part,
which
is
showing
good
practices
on
building
react
based
web
part.
So
it's
splitting
a
nice
way
to
the
components
to
all
of
the
communication
channels,
and
all
of
that
has
been
thought
through.
B
So
if
you're
kind
of
out
looking
into
slightly
above
the
getting
started
client-side
web
parts,
we
would
recommend
you
to
have
a
look
on
to
react
to
do
basic
because
that's
really
showing
great
set
of
capabilities.
How
the
handle,
when
the
web
part,
is
not
configured
when
it
is
configured.
What
if
the
lists
are
missing
and
all
of
those
capabilities
is
demonstrated
them
so
super
super
gullible
web
part.
That's
now
missing
a
really
detailed,
read
me.
B
Tab
of
subjects
is
for
working
on
that
one,
so
it
should
be
out
there
latest
tomorrow
and
in
the
dev
branch.
So
that's
a
really
one
one
thing
which
we
would
recommend
you
to
have
a
look,
and
one
thing,
maybe
dimension
around
the
samples
and
the
frameworks
themselves.
So
in
the
SharePoint
framework
you
can
use
whatever
JavaScript
framework
you
one.
So
you
can
build
stuff
using
a
more
shake.
Berry
react
amber.
It
doesn't
really
matter.
We
know
Microsoft,
we
needed
to
make
a
decision
at
some
point
and
our
chosen
flavor
how
we
build
our
stuff.
B
Our
first
party
web
parts
is
react.
It
doesn't
mean
that
you
need
to
do
that,
but
and
that's
the
reason
why
there
will
be
more
react.
Examples
available
also
in
a
sample
sweeper,
and
we
are
looking
into
releasing
some
of
the
first
party
web
parts
as
an
open
source
web
parts
as
well.
So
all
of
those
will
be
react
because
we're
investing
heavily
on
the
react
platform
by
building
the
react,
based
components
and
controls
as
well
as
you
are
prick
react
components
so
that
you
don't
have
to
worry
about
the
styling.
B
You
don't
have
to
worry
about.
Building
the
presentation
layer
you
can
concentrate
more
on
just
consuming
on
angular
site
is
ten
GUI
fabric,
which
is
a
great
community
for
doing
something
similar
as
well,
so
just
to
clarify.
Why
there's
more
react.
Examples
in
here
huge
I
think
that's
it
from
my
side.
So
let's
let
let's
let
a
Patrick
to
take
over
and
move
into.
B
What's
new
and
latest
on
the
B&B
JavaScript
core
component
side,
which
is
a
HR
script
library
like
whatever
other
effort
product
service,
we
provide
police
out
there
and
that's
the
kind
of
a
clarifying
and
kind
of
elaborate
on
that
one.
So
you
do
not
need
to
use
the
mvhs
core
component
when
you
write
stuff
for
the
SharePoint
framework,
but
you
can
so
it's
a
third
party.
So
it's
a
community-driven
wiper
eat
which
is
making
the
development
easy
for
you
towards
SharePoint.
So
Patrick
you're
gonna
be
about
that
today
anyway.
A
So
this
bassist
Ted
JS
core
component,
is
something
we've
been
working
on
now,
since
we
learned
internally
about
what
was
coming
with
the
SharePoint
framework,
the
goal
is
to
make
it
easier
for
developers
just
the
way
in
the
same
way
that
the
see
some
core
library
does.
It's
not
something
you
have
to
use,
but
it's
something
we
hope
you
will
use
and
hope
you
find
helpful
and
useful
in
your
development
to
help
you
maybe
not
have
to
memorize
or
look
up
all
the
different
rest,
URLs
and
those
sorts
of
things.
A
So
a
couple
different
links
there
at
the
bottom.
First,
the
github
repo,
absolutely
welcome
everybody
as
contributions
there
and
report
issues
there,
as
well,
with
the
105
release
that
I'm
going
to
talk
through
we've,
updated
the
documentation
around
contributing
and
around
both
and
then
consuming
and
using
the
library
as
well.
We
got
the
NPM
package
which
is
updated
to
105,
as
I've
said
now
a
few
times
just
earlier
this
week,
and
the
Gators
get
her
a
conversation
or
get
her
still,
no
idea
what
to
call
get
er
the
chat
get
her
chat.
A
Finger
is
a
great
place
to
get
in
touch
with
folks
ask
questions
and
everybody's
fairly
responsible,
responsive
on
that,
as
well
as
a
question
so
trying
to
help
out
as
much
as
we
can
there
so
jumping
in
always
want
to
say
thank
you.
We've
got
two
new
contributors
to
talk
about
this
week.
Elio
and
Andrew
both
have
contributed
some
cool
fixes
to
the
library,
so
those
were
rolled
into
the
105
release
so
great
stuff
from
both
of
those
guys
to
thank
you
to
them
and
thank
you
to
all
of
our
contributors.
A
You
make
the
project
possible.
So
it's
very
much
appreciated.
As
I've
said
in
the
past,
please
do
double
check
the
author's
file
make
sure
I've
got
your
name
right
and
do
let
us
know
if
you'd
like
any
additional
information
by
your
name,
for
example
a
Twitter
handle
or
a
company
name,
something
like
that
very
happy
and
want
to
get
you
the
recognition
you
you
should
have
and
deserved
in
that
authors
file,
and
then
we've
said
this
on
a
few
calls.
A
If
your
company
is
allowing
you
time
to
contribute
to
the
patterns
and
practices,
whether
it's
the
JS
core
or
any
of
the
patterns
and
practices
projects,
if
you're,
actually
contributing
on
company
time
and
your
company
would
like
to
have
a
logo
sort
of
associated
with
the
patterns
and
practices
program,
we're
very
happy
to
do
that.
There
is
a
bit
of
a
legal
process.
A
Now
we
found
out,
we
have
to
go
through
to
do
that,
but
it's
not
a
huge
deal
and
very
happy
to
work
with
you
and
get
your
logo
and
that'll
be
as
part
of
the
monthly
call
so
getting
used
in
great
recognition
on
that
call
for
you
and
your
company
for
the
for
allowing
you
to
contribute
to
the
project.
So
thank
you
to
everybody
that
has
contributed
and
will
contribute
in
the
future.
Very
much
appreciated
by
all
of
us
in
the
patterns
and
practices
program.
A
So
what's
been
happening.
We
did
the
105
release
this
week,
big
news
there
and
we're
going
to
kind
of
talk
through
this
on
the
demo.
But
we
did
move
this
as
well
to
typescript
20,
which
changes
both
your
development
story
and
your
consumption
story.
A
little
bit.
We've
exported
a
bunch
of
the
classes
out
of
the
library
to
help
you
one
use
the
classes
in
your
projects
more
easily
and
two
helps
with
the
web
pack
and
some
of
the
other
bundlers
being
a
to
bundle.
A
Those
things
up,
which
then
helps
in
with
the
SharePoint
framework
story,
and
then
we
got
some
fixes
in
there
and
I
pipe
fixes
twice,
which
I
really
meant
to
type
enhancements,
so
pardon
that,
but
so
got
some
good
enhancements
and
some
fixes
into
the
105
there
as
well
will
demo
that
today
got
a
question
about
creating
content
types.
Currently,
you
cannot
create
content
types,
that's
not
something!
That's
super
well
documented
in
rest,
in
fact
not
really
documented
at
all.
A
But
if
there's
interest,
we
can
certainly
look
at
adding
that
and
so
try
and
take
a
look
at
that
where
to
ask
your
SharePoint
framework
questions.
The
tech
community
at
microsoft,
microsoft,
com,
as
well
as
stack
exchange
stack
exchange,
are
both
great
places
to
ask
your
SharePoint
favorite
questions.
You're.
Certainly
welcome
to
ask
them
in
our
get
er
channel
for
the
repo
and
we'll
do
our
best
to
help,
but
the
actual
product
group
is
monitoring
the
tech
community
and
stack
exchange
as
well
for
your
questions
there.
A
So
it
might
be
a
slightly
a
better
place
to
ask
those
and
then
we've
got
a
some
stuff
coming
from
Sergei
around
the
sharepoint
off
and
enhancing
that
story
in
node.
So
right
now,
for
those
of
you
that
have
been
on
past
calls,
we
showed
you
using
a
client
ID
in
a
secret
he's,
got
a
library
that
he's
actually
got
a
pull
request,
setup
that
I
haven't
had
a
chance
to
look
at
it.
Just
came
in.
A
I
think
this
morning
or
I
just
saw
it
this
morning,
so
we'll
have
some
off
improvements
and
we're,
hopefully
to
get
him
doing
a
demo
on
that
on
our
next
call
on
october
28,
I
believe-
and
I
apologize-
I
edited
this
in
the
brow
october-
twenty
seventh
and
we'll
we'll
get
a
good
demo
on
that.
So
looks
like
some
of
my
edits,
didn't
quite
save
and
then
graph
support.
There's
a
question
there.
Not
currently,
we
don't
currently
call
or
support
calling
the
microsoft
graph.
A
It's
a
slightly
different
pattern
than
calling
the
sharepoint
api's
in
terms
of
the
auth
needs,
and
things
like
that
generally
requires
like
a
delay
s,
something
we
can
look
at
I
have
mixed
feelings
about
it,
whether
that
would
sort
of
grow
this
library
too
much
or
maybe
defocus
it.
Maybe
that
should
be
a
separate
library,
something
I'm
very
happy
to
continue
the
conversation
about
in
terms
of
graph
support
and
then
issues
are
being
actively
reported.
So,
thank
you.
A
Everybody,
who's,
reporting
issues,
I,
don't
love
to
see
issues
but
I
do
love
to
see
them
getting
reported.
So
it's
something
we
can
work
on,
improving
looking
at
making
those
fixes,
so
we
are
working
on
each
of
those
as
they
come
in.
We
do
appreciate
all
the
feedback
and
if
anybody
has
some
time
and
would
like
to
help
out
with
some
of
those
issues
that
are
being
reported,
that's
very
much
appreciated
as
well,
but
do
keep
those
issues
coming
in
I.
A
Think
that's
great
and
it's
going
to
help
us
just
improve
the
library
for
the
benefit
of
everybody.
So,
thank
you,
the
folks
that
are
using
library
and
then
letting
us
know,
but
they've
run
into
problems
or
have
ideas
for
enhancement,
so
great
stuff
from
the
community
there
and
then
again
the
links
at
the
bottom
to
the
git
er
and
the
community.
If
you
want
to
be
sort
of
part
of
the
conversation
or
have
questions
great
way
to
get
involved
so
opportunities
to
contribute
these
kind
of
remain
unchanged
right.
A
A
webpart
demo
on
this
call
would
really
love
to
see
more
from
the
community.
Around
demoing
webparts
we've
had
some
great
demos.
The
last
few
calls
want
to
keep
those
going,
make
sure
we're
all
learning
and
contributing
you
know
to
each
other's
growth
in
the
SharePoint
framework
space
in
the
client
development
spaced
as
bassist
Ted
and
we've
said
before.
A
You're,
not
absolutely,
of
course,
required
to
use
the
J
s
core
library
and
your
web
parts
would
still
love
to
see
them
demoed,
but
would
love
to
see
you
used
to
the
Jazz
core
library
in
the
web
parts
as
well,
but
certainly
absolutely
not
a
requirement
to
demo
it
on
the
call
or
to
show
it
off.
I
think
we
can
all
learn
from
you
know,
seeing
everybody's
approach
to
solving
these
problems
and
again
still
looking
for
help
with
testing
reporting
issues.
Folks
are
doing
that.
A
That's
fantastic
love
to
see
those
issues
coming
in
writing
tests
still
working
through
that
and
then
help
styling
the
documentation
I
didn't
want
to
mention.
The
docks
were
not
updated
as
part
of
the
105
release
type
dock,
which
is
the
bat
tool,
I
guess
I'll
say
we
you,
sir,
the
package
to
generate
the
documentation,
doesn't
work
with
typescript
20
currently
and
I
spent
more
time
than
I'm
happy
to
admit
trying
to
make
it
work
with
to
not
oh.
A
In
fact,
I
was
looking
at
trying
to
submit
a
pull
request
to
those
folks,
but
couldn't
quite
get
it
going
and
finally,
it
had
actually
other
work
to
do
so.
We'll
take
a
look
back
at
that,
but
do
want
to
still
get
some
help.
Styling
and
the
UX
for
the
documentation
site.
I.
Think
that's
a
great
opportunity
for
someone
in
the
community.
A
Looks
like
I
can
see
it.
It's
there.
It's
there
greater
vedepo
perfect.
So
what
I
wanted
to
show
you
guys
is
some
of
the
new
105
features.
Like
so
I
mentioned,
we've
gone
to
typescript
20,
so
that's
a
fairly
big
change,
and
if
we
look
here
this
is
that
testing
project
I've
showed
on
a
few
calls
and
you
can
actually
download
this
I've
got
a
new
blog
post.
Updating
that
sort
of
in
quotes,
node
console
app
project,
and
so
one
thing
you'll
note
right
away
is
there's
no
typing's
folder.
A
A
But
this
removes
the
need
for
using
another
tool,
whether
you
wanted
to
use
typing's,
whether
you
wanted
to
use
TSD
or
one
of
the
again
open
source,
many
options,
it
sort
of
removes
that
need,
and
so
it
makes
the
installing
experience
a
little
bit
easier
and
what
this
does
actually
solved.
We
had
several
different
issues
reported
on
some
problems
with
typing's
and
things
like
that
parmi,
so
folks
that
didn't
have
typings
installed
globally.
A
The
post
install
step
we
had
in
104
to
install
the
Taipings
was
failing
for
folk
stuff
like
that,
so
this
removes
kind
of
that
dependency
on
typing's,
as
well
as
removes
the
dependency
on
installing
as
tool
to
set
up
all
your
typing's
for
your
project,
and
that
also
as
well
applies
to
the
folks
who
are
contributing.
You
no
longer
need
to
install
the
Taipings
and
things
like
that
when
using
with
with
two
dot,
o
compiling
or
trans
piling.
Sorry,
please
don't
jump
on
me
for
that.
A
So
that's
a
big
change
but
I
think
a
really
important
change.
It
makes
things
a
lot
simpler
and
I
think
a
lot
easier
and
solves
actually
some
issues
that
were
reported,
which
is
always
great,
so
no
need
for
typing's,
that's
great!
That
will
install
those
at
typing's.
You
can
actually
use
that
as
well
in
your
projects
to
pull
in
typing's
through
the
at
type,
so
you
can
just
do
an
NPM
install
at
types
/
and
then
the
name
of
the
library
so
at
type
/
SharePoint.
Something
like
that.
A
The
next
thing
I
want
to
show
is
this
is
something
folks
have
been
on.
The
call
have
seen
this
pattern
before
and
I'm
importing
pnp,
and
this
off
thing
is
just
me
running.
The
P&P
set
up
with
my
client,
ID
and
secret,
so
I,
didn't
have
to
kind
of
broadcast
that
to
the
world,
so
you
can
sort
of
ignore
that
and
I've
got
my
site
URL
and
as
before,
I'll
just
hit
at
five,
and
you
can
see
I'm
doing
p
and
PSP
web
select.
You've
all
seen
this
before
and
nothing
nothing's
really
changed
their.
A
That
pattern
still
works,
so
you
get
a
so
no
breaking
changes
there.
Nothing
like
that,
and
then
we
should
see
me
so
we
see
here
we
got
our
title
back
from
the
web
log
to
the
console.
So
that's
kind
of
neat,
but
what
I
wanted
to
show
you
is
one
of
the
big
enhancements
we've
done
in
the
105
release
is
I
can
now
import
web
directly
out
of
the
top
of
spp
and
pjs.
So
this
is
now
exported.
A
Class
and
I
can
I
can
come
in
here
and
say:
let
my
w
equal,
a
new
web
and
I
can
give
it
a
site
URL.
So
this
solves
a
problem.
That's
come
up
a
lot
where
folks
wanted
to
open
other
webs,
and
this
didn't
necessarily.
There
were
ways
to
do
it.
It
didn't
work
a
really
great
or
at
all,
with
web
pack
or
other
Butler's.
It
worked
with
in
typescript,
but
not
necessarily
when
you
try
and
bundle
it
up.
So
this
is
a
great
improvement
that
this
will
now
work
with
web
pack.
A
So
you
can
see
I've
just
created
a
new
web.
You
can
give
it
any
absolute
URL
to
any
web
and
I'm
just
going
to
hit
f5
and
you're
going
to
see
the
same
thing
work
again,
but
with
the
advantage
that
I've
been
able
to
set
I'm
using
the
same
site
URL,
but
you
could
of
course
use
any
other
site
URL
here.
It
does
need
to
be
absolute
and
you
do
need
to,
of
course,
have
registered
the
add-in
in
that
site,
so
the
permissions
and
all
that,
of
course,
still
apply
and
are
no
different.
A
And
if
we
look
at
you
can
see
now,
I've
got
my
title
and
everything
works,
just
as
we
would
have
expected
there
so
very
cool
there.
One
of
the
other
things
that
this
actually
lets
you
do
now
is
you
can
do
an
import,
a
star
as
say
p
and
p
NS
so
saying
the
pnp,
namespace
and
so
I
could
say
p
and
p
NS
dot
web
and
that's
still
going
to
work
as
we
expect,
which
you
can
also
do
to
pnp
done
in
s
and
see
all
the
classes
were
exporting
on
intellisense
here.
A
So
one
of
the
big
advantages
with
this
is
you'll
be
able
to
more
easily
access
all
the
internals
of
our
library
you'll
be
able
to
type
strongly
type
your
input
parameters
to
methods
so
things
that
take
a
certain
parameters
that
were
typed.
You
can
now
type
those
you'll
also
be
able
to
strongly
type.
For
example,
here's
list
update
result,
so
we
can
actually
strongly
type
our
results
coming
back
out
of
list
update.
A
The
other
thing
it
allows
you
to
do
is
much
more
easily
and
you
can
do
this
either
way,
so
we
could
say
p
and
p.
Ns
lager,
dot
log,
and
I
can
log
things
and
if
I
wanted
to
let
my
listener
equals
p
and
p
NS
dot
a
console
listener,
and
I
would
do
a
new
on
that.
That's
a
class,
a
new
console
listener
and
I
can
now
much
more
easily
as
an
example
subscribe
my
listener
to
the
logger,
and
then
I
can
do
in
here.
A
I
can
log
my
message
and
I'm
actually
going
to
use
the
right
which
takes
just
a
string
there
on
the
logger
and
if
I
were
to
run
this,
I'm
now
going
to
get
the
exact
same
result.
But
instead
of
writing
to
the
console
directly,
I'm
writing
to
my
logger
and
my
logger
is
using
the
console
listener
and
go
to
back
to
my
debug
console.
A
A
So
I'll
just
run
this
now.
Apologies
for
that
I
didn't
look
at
my
notes
quite
closely
enough,
and
so,
if
you're
below
the
log
level,
like
most
logging
things,
it's
not
actually
going
to
log
that.
So
it
does
that
you
can
set
the
log
level
on
the
logger.
But
if
we
look
now
at
the
console,
you'll
see
we've
gotten
written
out
to
the
console
our
log
message
through
the
logger
and
you
can
subscribe
multiple
loggers
of
course.
A
A
So
this
is
hopefully
a
great
enhancement
for
folks,
that's
going
to
let
things
work
a
little
bit
easier,
make
it
a
lot
easier
to
interact
with
the
library
and
interact
with
the
different
classes.
So
things
like
that
and
we'll
just
hit
f5
and
we'll
see
that
this
approach
also
works
as
well,
so
showing
the
different
ways
of
importing
things
out
of
the
library.
A
A
You
can
see,
we've
built
up
all
our
files
and,
if
I
go
to
the
browser,
one
thing
I
wanted
to
show
you
is
in
a
google
chrome.
We
get
some
questions
still
about
this.
That
can
I
load
unsafe
scripts
and
answer
is
yes,
I
can
so
I've
loaded
those
unsafe
scripts?
Now
and
if
we
hit
f12-
and
we
look
at
the
console
we
should
see
here-
is
our
logged
message
there
on
the
console.
A
This
message
can't
go
away
for
whatever
reason,
but
so
here's
our
message
and
we
logged
that
to
the
console
and
so
I've
also
set
up
I,
wanted
to
show
another
feature
of
web
pack.
I've
got
a
div
in
there
in
the
here.
We
go
on
that
page
and
so
I
want
to
show
two
features
here.
I've
got
a
little
div,
I
added
it's
just
in
a
script
editor
web
part.
A
So
if
I
save
that
web
park
will
web
pathway
part
web
pack
will
invalidate
because
it
sees
the
files
of
change,
we're
watching
those
files,
it's
going
to
bundle
that
back
up
I
can
refresh
the
page
and
see
my
changes.
So
a
very
simple
change,
but
again
very
similar
if
not
the
same
functionality
is
in
the
SharePoint
framework,
but
just
a
way
to
play
with
the
javascriptcore
alive
directly
outside
of
the
sharepoint
framework.
A
Unquote,
real
projects,
real
sort
of
stuff
to
do-
and
the
last
thing
I
wanted
to
show-
is
something
that
I
can
do
now,
and
this
is
again
in
that
sample
project
you
download
it,
but
I
can
do
a
gulp
bundle
and
I
get
some
linting
errors.
So
that's
a
great,
but
what
we've
got
now
in
the
dist
is:
we've
actually
got
a
min
ified
version
of
our
files,
so
this
is
the
entire
web
packed
version
and
you
might
be
asking
yourself
well
big
deal.
We've
seen
webpack
work.
A
What's
really
cool
about
this
is
this
is
now
working
with
the
105
release
and
doing
allowing
you
to
export
these
classes
directly
and
use
the
web
class
directly,
which
is
something
that
prior
to
105,
would
fail
and
would
not
work.
So
this
is
a
great
improvement
for
those
folks
using
webpack
are
those
folks
using
the
sharepoint
framework
and
wanting
to
use
105
or
reviews.
I'm
sorry.
I
wanted
to
use
the
j
s
core
with
the
sharepoint
framework.
A
This
is
a
great
enhancement
to
let
these
things
be
bundled
up
correctly
and
work
in
the
way
you
would
expect
you
know
for
things
to
work
with
web
back.
So
I
think
a
great
enhancement
there
did
want
to
touch
on
one
other
thing
and
just
mention
it
out.
Loud
I
went
through
and
I
removed
a
lot
of
the
the
selectable
properties
from
a
bunch
of
classes.
I
mentioned
this
in
the
the
release,
notes
blog
post,
but
wanted
to
talk
about
that
a
little
bit.
The
reason
I
did,
that
was
simply
to
save
space.
A
We
gained
11
k
in
the
middle.
I
packaged
which
is
kind
of
a
lot
just
for
removing
these
selectable
properties
and
what
I
mean
by
selectable
properties
is
stuff.
You
can
just
use
dot
select
on
so
instead
of
having,
for
instance,
on
file,
we
used
to
have
an
explicit
name
property
or
you
could
save
file
named,
get
and
get
just
the
name
back
if
you're
doing
that
in
your
code.
A
The
way
to
now
do
that
is
that
file
dot,
select
and
get
that
information
back
so
really
excited
to
gain
that
space,
but
did
want
to
mention
it
out
loud
for
those
folks
who
might
want
to
do
those
sorts
of
things
and
a
couple
other
mentions.
So
we
got
some
great
stuff
in
the
pipeline
on
web
hooks
and,
as
I
mentioned
before,
of
improvements
in
the
off
a
story
within
node.
A
A
Those
are
outlined
in
the
two
blog
posts
around
using
typescript
20
20,
some
of
the
differences
in
how
your
projects
are
going
to
build,
and
things
like
that,
and
if
you
find
issues
of
course
report
those
so
I'll
hand
this
over
now
to
a
wall
deck.
If
you're
ready
to
check
that
stuff
out
Patrick.
Can
you
share
the
sample
the
sample
is
on
the
blog
post.
Let
me
grab
a
link
to
that,
so
you
can
download
it
directly
from
the
sort
of
updated
console
app
discussion
here.
C
I
am
so,
can
you
see
my
screen
and
hear
my
voice
I
sure,
can
you're
making
a
walker
awesome
so
as
you've
heard-
and
you
might
have
experienced
yourself
already
when
you
build
client-side
web
bars,
there
is
no
ability
to
run
elevations
right
because
you
run
in
browser
and
you
run
inside
the
context
of
the
current
user.
So
there
there
is
no
way
for
you
to
elevate
privileges
and
get
access
to
resources
that
you
are
not
allowed
to
access
by
yourself.
C
Nevertheless,
there
might
be
still
requirements
that
they
require
you
actually
to
be
able
to
do
them.
So
imagine
that
you
would
have
a
web
part
that
allows
you
to
indirectly
right
to
a
list
that
you
cannot
access
so
like
Paul
or
request
for
HR.
So
you
would
only
be
able
to
write
a
request,
but
you
wouldn't
be
able
to
access
that
list
and
then
there
are
ways
to
achieve
that
in
the
SharePoint
frameworks.
Client-Side
web
parts
in
a
way
a
bit
different
than
in
a
pass.
C
C
C
What
you
see
here
is
we
are
here
in
SharePoint
on
online,
but
the
workbench
is
on
my
localhost
and
if
you've
worked
with
Shepherd
framework
client-side
web
parts
a
bit,
you
know
that
you
cannot
do
that.
Cross-Domain
call
client
side
right.
So
then
that
that
that's
one
and
also,
if
that
what
effort
was
to
put
on
a
page
and
I,
would
login
to
the
site
using
an
account
that
cannot
xls
I
would
still
be
able
to
create
item.
C
So
the
way
this
works
is
that
web
part
uses
a
custom
web,
a
API,
that's
registered
as
a
SharePoint
Eden.
That
has
appt
only
write
permissions
to
this
list
right.
So
if
we
look
at
the
code,
let
me
jump
to
the
code
here.
We
have
the
web
part,
and
here
we
hear
you're
here
here
we
have
the
API
that
we
call
from
inside
the
web
part.
So,
let's
zoom
in
on
a
code,
its
built-in
react,
so
I
hope
that
you
can
follow
that.
C
And
what
we
see
here
is
that
we
have
the
create
item
function
that
that's
attached
to
button
on
the
go
apart
and
whatever
that
is
click.
We
issue
a
post
request
to
our
custom,
build
web
api
at
this
URL,
and
we
should
we
issue
a
post
request
and
we
send
along
the
title
that
we
typed
in
the
input
box
dapi
on
its
part.
If
we
go
to
that,
is
in
c-sharp
web
api
api.
C
So
that's
one
way
you
can
go
around
that
if
we
go
back
to
our
list.
Sorry
for
that
Rome
browser.
If
you
look
at
the
item,
let
me
zoom
that
in
a
bit,
if
you
view
the
item
here,
we
can
see
that
this
item
has
been
created
by
the
PMP
&
evasion
API.
So
so
that
means
that
it
has
not
been
created
by
the
user
logged
into
the
page,
but
it's
actually.
C
Created
by
the
add
in
that
we
use
inside
the
API,
and
we
have
an
article
that
explains
you
step
step
step
by
step
like
how
do
you
go
around,
creating
that?
How
do
you
edges
or
that
API
in
your
side?
How
do
you
grant
that
permissions?
So
all
of
that
will
be
available
to
you
you
to
check
how
it
works,
but
the
basic
I
idea
is
that
from
inside
the
web,
part
with
with
credentials
that
you
have
you
have
no
permissions
to
that
and
to
access
a
resource.
C
B
Yeah
so,
while
the
cannot
just
slightly
elaborate-
because
this
is
a
such
a
classic
scenario,
but
I
would
say
that
the
classic,
the
really
really
simplistic
business
scenario
is
something
okay.
I
want
to
have
a
feedback
report.
I
want
to
have
a
feed
perfect
part
on
the
front
page
of
my
intranet,
where
people
can
go
and
submit
but
say
how
they
feel
and
what's
the
feedback
and
whatever
to
be
able
in
shipment,
to
be
able
to
people
to
actually
write
a
list.
B
These
people
actually
need
to
have
a
read
permissions
to
the
list
as
well,
and
that
would
then
mean
that
that
the
person-
yes,
he
can
write
to
the
list
using
the
web
part,
but
he
would
actually
be
able
to
read
also
the
other
people's
feedback
and
that's
not
really
what
we
typically
one.
So
we
need
to
elevate
really
classic
scenario
from
sharepoint,
2007,
2010-2013
and
so
on.
B
So
the
model
is
accepted
the
same
as
in
adding
model
or
adding
model
implementations,
but
we
just
do
it
now
within
the
client-side
web
parts,
and
this
is
one
of
the
samples
which,
with
no
doubt
wanted
to
actually
create
because
there's
a
lot
of
questions
around
the
elevation
from
the
community
sooner
or
later.
So
we
have
this
one
available
and
the
immediate
kind
of
a
follow-up
question
would
be
that:
hey
okay.
But
what?
If
now?
What?
If
somebody
is
just
calling
that
web
api?
Is
it
secured?
B
What
about
the
traffic
between
the
client-side
web
part
and
that
web
api
with
salsa
dinner?
Sure?
And
the
answer
is
right:
now,
with
this
sample,
we
knowingly
make
a
decision
that
we
didn't
want
to
show
how
it
can
be
secured,
but
but
it
can
be
severe,
accusing
dasha
ad
implicit
float,
so
we'll
work
on
a
sample
or
wallet
is
actually
already.
There
is
a
sample
around
that
pond
as
well,
which
is
actually
been
showing.
B
C
B
A
That's
great
and
I
think
the
other
point
to
make
is,
while
you're
elevating
permissions
you're
only
elevating
what
you're
providing
right.
So
it's
not
an
open
elevation
of
something
that
you're
creating
holes
in
the
security
of
the
site.
It's
very
specific
in
this
case
adding
a
list
item.
You
can
imagine
other
scenarios,
but
this
isn't
wide
open
anything
to
your
site
and
you
can
of
course
tailor
their
permissions
of
that
web
api
in
quotes
add
in
to
exactly
what
you
need
as
well,
so
you're,
not
over
permission
anything
in
the
chain.
Yes,.
C
Yeah,
yes
and
I,
guess
that
that
what
you
say
is
actually
a
nice
end
point
right,
because
you
don't
need
to
have
like
eaten
nothing
all
or
are
all
approach.
What
you
could
do
is,
you
could
have
separate,
add
in
with
different
permissions
and
dessert
with
each
ate,
with
each
API,
so
even
with
each
operations.
So
with
that
you
can
really
tightly
sealed
down
all
the
excess
and
if
one
of
them
would
breach
that
would
only
break
only
that
one
API
and
not
all
of
them.
B
Too
and
I
have
to
say
one
more
example
since
we're
talking.
This
is
an
awesome
discussion,
because
I
personally
I
think
this
is
the
holy
crail
off
of
enterprise
development.
How
do
I
actually
call
an
external
API
from
the
from
the
client
side
paper
and
one
if
we
think
about
the
web
api?
What's
wild
ex
showed?
Can
you
actually
ball
to
go
to
the
code?
The
most
simplistic
way
to
secure
this
with
a
baby
I
which
isn't
that
wrong
security?
B
It's
around
limiting
the
access
of
calling
direct
API
is
actually
at
a
course
limitations
on
the
web
api
site,
so
you
could
actually
add
a
course
limitation
for
the
production
tenant,
which
means
that
if
the
call
is
coming
from
the
production
tenant,
it's
fine.
If
it's
tries
to
come
from
anywhere
else,
we
would
not
execute
that
there's
way
to
still
go
around
that
as
well,
but
still
the
most
simplistic
way
of
getting
this
slightly
more
security
than
right
now.
Yep.
A
A
So
now
we
got
plenty
of
time
for
Q&A
from
folks.
If
there's
any
kind
of
open
questions
on
anything
you've
seen
today,
sharepoint
framework,
a
core
library
or
client-side
development
in
general,
but
while
we're
kind
of
waiting
for
folks
to
type
their
questions
or
come
off,
you
I
did
have
one
editorial
note
I
forgot
to
mention
earlier
did
want
to
apologize.
The
video
didn't
come
through
from
our
recording
at
ignite,
which
is
a
huge
bummer
for
me
personally,
because
I
thought
that
was
a
fun.
A
fun
call.
So
sorry
about
that.
A
Frankly,
not
sure
because
we
had
video
for
like
the
first
five
seconds
and
then
it
stopped
recording.
So
apologies
there,
no
video,
but
the
you
can
get
all
the
audio
as
well
so
questions
what
was
the
framework
ur
idea
for
securing
the
web
api,
so
wall
decks
answer
that
Azure
Active
Directory
is
great.
At
that
point
it
really
is
up
to
as
well
you
the
developer,
so
Azure
Active
Directory
has
a
great
obvious
choice
and
there's
other
choices.
A
A
A
So
I've
talked
to
some
people
lately
about
risks
associated
with
implicit
flow.
It
seems
to
me
that
the
risk
can
be
mitigated
by
how
the
tokens
are
handled
by
the
client,
for
example,
if
you
put
the
token
and
a
cookie
other
scripts
in
the
user
agent
could
access
and
use
it
thoughts
on
best
practices,
so
I
don't
know
if
they
sell
Baalbek
want
to
tackle
that
one
I'm.
C
Sure
yeah,
so
I
guess
the
problem
that
you
say
is
is
valid
one
and
there
is
no
way
for
you
to
secure
them,
because
these
tokens
are
actually
available
to
any
element
on
the
page.
So
imagine
that
you
would
have
two
airports
on
the
page
if
one
of
them
would
would
request
an
access
token.
At
that
point,
currently
the
way
it
all
works
or
actually
all
inclusive
flow
works
is
that
every
element
on
that
page
has
access
to
death
token,
and
there
is
no
way
for
you
two
to
work
around
it.
C
B
And
when
I
think
of
it,
when
you
are
installing
client-side
web
parts,
and
that
is
a
tenant
level
operation
and
when
you're
doing
that,
we
are
clearly
pointing
out
that
by
the
way
these
are
fortress
with
pots.
So
it's
absolutely
true.
If
we
start
accessing
and
storing
those
tokens
there,
if
and
there
would
be
a
malicious
client-side
web
part
on
the
on
the
page,
it
could
actually
access
that
the
information
as
but
why
would
you
install
the
part
lieutenant?
B
So
it's
the
same,
there's
kind
of
a
scenarios
with
farm
solutions
back
in
the
2007
or
noreen
on
premises
in
general.
People
don't
consider
that
but
farm
solutions
have
full
access
on
anything
within
the
clock,
so
they
can
actually
access
all
the
confidential
information
within
the
farm.
So
it's
no
doubt
practice
actually
review
the
code.
B
A
Thanks
guys
any
other
questions
from
anybody
in
the
audience.
In
that
case,
I,
don't
see
anybody
typing
so
I'll
just
say
thank
you
to
all
doc
for
another
great
demo,
thanks
to
visa
for
some
great
updates
from
sharepoint
framework
and
thanks
to
all
of
you
for
joining
the
call
and
participate
in
look
forward
to
talking
to
you
guys
shortly.
Remember.
Our
next
meeting
will
be
october.
A
27
we're
going
bi-weekly,
so
October
27th
is
the
next
meeting
and
we've
already
got
hopefully
a
great
demo
from
Sergei
lined
up
there
and
we'll
look
to
have
a
second
demo
there
from
somebody
from
the
community
as
well.
So
if
you
write
a
web
part
or
interested
in
doing
a
demo,
please
just
get
in
touch
would
love
to
feature
you
on
the
call.
So
thank
you.
Everybody
have
a
great
rest
your
week
and
we'll
be
talking
soon.
Take
care,
hi.