►
Description
See more details on covered topics from https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Patterns-amp-Practices-JS-amp-SP-Fx-Special-Interest/m-p/15154#M479
Presentation available for download from http://docs.com/OfficeDevPnP.
A
Hello
and
welcome
to
SharePoint
framework
and
JavaScript
special
interest
group
weekly
meeting
for
September
22nd
2016
every
time.
I
say
that
I
do
glance
down
at
the
date,
because
I've
gotten
that
wrong
on
the
slide
before
I'm
Patrick,
Rodgers
I'm
joined
here
with
a
basa
you've
owned
it
and
we're
going
to
go
through
another
great
weekly
meeting,
I'm
going
to
talk
a
little
bit
about
that
weekly
schedule
here.
A
At
the
end,
we
talked
a
little
bit
about
that
last
week,
but
let's
dive
right
in
so
starting
off
as
we
do
every
week
for
folks
that
might
be
new
to
the
call
or
new
to
listening
the
recordings.
This
is
the
SharePoint
JavaScript
special
interest
group,
JavaScript,
client,
side,
development,
SharePoint
framework,
special
interest
group,
so
targeting
all
those
sort
of
client-side
development
areas
and
we're
part
of
the
larger
SharePoint
patterns
and
practices
program.
And
so
we
aim
to
do
two
things
during
this.
A
A
We
got
drop
number
four
update
number
four
of
that
is
live
now
as
if
yesterday,
I
want
to
say
maybe
two
days
ago,
we'll
talk
about
that,
get
an
update
there
and
then
as
well
building
the
JavaScript
core
component
library,
which
is
to
help
aid
so
efficient
data
access
and
make
it
a
little
bit
simpler
to
use
a
the
SharePoint
rest.
Api
is
in
the
context
again
of
that
client-side
development
or
in
fact,
as
well
node.js
development.
A
So
the
aim
is
to
support
kind
of
that
broad
in
big
air
coach,
JavaScript
platform
for
folks
typescript,
of
course,
as
well
included
in
that,
and
so
you've
got
two
legs
down
at
the
bottom.
The
one
at
the
top
is
to
our
AKA
ms
sharepoint
pnp
community,
and
that
goes
now
to
the
microsoft
tech
community.
Where
you
can
post
your
questions
there,
it's
still
early
days
we're
still
working
out
exactly
how
all
that's
going
to
work.
A
I
know
it's
not
exactly
on
parity
with
what
we
were
doing
in
Yammer
at
this
point,
but
it
it
is
where
we're
at
for
now
and
then
as
well.
The
devil,
office.com
/
sharepoint,
is
sort
of
your
landing
page
and
launch
point
for
a
lot
of
different
updates
and
ideas
and
links
and
things
around
a
SharePoint
in
general
sharepoint
development
and
especially
the
SharePoint
framework.
It's
also
a
great
place
to
get
access
and
find
samples
and
tutorials,
and
we
are
working
to
improve
and
evolve
all
of
those
resources
as
we
go.
A
So
if
you
have
specific
feedback
around
those
things,
certainly
open
to
hearing
that
a
great
place
to
do
that
is,
of
course,
in
the
tech
community.
Just
let
us
know
there
what
you
really
feel
about
how
things
are
going
so
our
agenda
for
this
week
latest
updates
about
the
SharePoint
framework.
We've
got
some
updates
again
for
the
j
s
core
component
and
then
I've
got
a
great
community
demo
from
waldeck
again
around
Azure
from
client-side
web
parts
with
implicit
flow.
Really
great
pattern,
really
great
demos.
So
look
forward
to
that
as
well.
A
B
So
a
few
things
from
this
site,
so,
first
of
all,
the
top
number
four
I
came
out
yesterday
yesterday
morning,
pacific
time.
Well,
actually
it
was
released
on
an
evening
or
night
time
on
pacific
time,
but
the
release
notes
were
coming
out
at
six
a.m.
pacific
time
so
which
is
like
six
well
write
about
almost
24
hours
ago.
The
release
notes
are
containing,
what's
actually
updated,
there's
a
lot
of
internals
updated
on
the
on
the
system
as
well,
and
the
release
notes
are
also
explaining
how
to
upgrade
your
existing
stuff.
B
Can
we
go
to
the
following
slide,
because
here
you're
actually
leading
and
patrick
on
still
I'm
not
going
to
take
over
because
you
you
continue
in
a
second,
so
these
are
coming
step
by
step.
So,
first
of
all
the
the
number
four
is
the
number
number
one
thing:
if
you
click
one
more
time,
you're
my
lovely
assistants,
Patrick
there
we
go
awesome
there.
B
We
go
so
and
one
thing
kind
of
related
on
this
one,
because
we're
still
seeing
questions
around
it
so
dead
of
calm,
/
sharepoint
is
the
location
for
all
of
the
tutorials
and
technical
articles.
This
multiple
upcoming
guidance
articles,
which
are
in
a
queue
there
already
some
of
them,
are
already
written.
Some
of
them
are
in
technical
review
right
now
and
those
will
get
merged.
The
diff
drove
home
/
SharePoint
by
ignite,
which
means
by
Monday
most
likely.
B
We
do
welcome
contributions.
So
if
you
go
to
the
sbf
ducks
repo,
you
can
actually
contribute
articles,
or
if
you
find
an
issue
on
the
existing
articles,
you
can
actually
do
that
as
well.
The
SharePoint
framerate
port
sample
repo
fully
active
now
we're
getting
actually
a
lot
of
nice
activities
on
that
one.
So
if
you
click
one
more
time,
Patrick
here's
a
list
of
all
of
the
web
parts
which
we
have
currently
available
in
a
deaf
branch.
So
within
the
the
SharePoint
framework,
webpart
sample
repo,
we
are
doing,
creature
emerges
between
the
dev
and
monster.
B
So
it's
using
the
office
graph
API,
not
the
Microsoft
graph
API,
because
Microsoft
graph
does
require
the
ad
implicit
flow
to
to
be
completed
so
the
office
graph
API.
So
you
can
call
with
an
identity
and
access
token
what
the
person
already
has,
because
the
javascript
is
hosted
in
SharePoint.
If
we
are
accessing
joseph
graph,
we
need
to
do
an
additional
things
with
an
azure
ad
implants
it
flow,
then
we're
going
to
walk
through
or
well
deck
is
going
to
work
that
through
this
call
as
well
react
organizational
charts,
react,
search.
B
Sharepoint
crude
is
there
as
well
and
to
do
web
part
sample
the
ship
and
crew
from
my
perspective
is
probably
the
most
valuable
one,
the
show
how
do
we
do
typical
operations
using
angular
react,
BMP,
JavaScript,
core
component
and
also
without
any
any
library,
so
it
actually
has
four
different
web
parts
and
then
you
can
compare
differences
between
angular
reactant,
a
score.
So
really
great
example,
and
we
do
have
a
webcast
on
that
one
as
well
by
the
way
in
the
PMP,
a
video
channel
due
to
a
webpart
sample
well,
is
coming
from
engineering.
B
We
will,
but
it
that's
way
too
complex.
So
we
will
further
simplify
that
one.
It
is
using
unnecessary
complexity
within
the
implementation,
because
it's
coming
from
the
real
engineers
who
seem
to
think
that
everything
has
to
be
complex
by
default,
so
we'll
get
it
further
simplified
and
much
more
fine-tuned
later
on.
But
more
than
welcome,
we
do
welcome
community
contribution.
So
if
you're
writing
and
a
scenario
if
you're
writing,
something
which
is
which
is
demonstrating
new
capabilities.
B
All
of
that
all
of
those
samples
are
more
than
welcome
to
the
repository
and
you
will
absolutely
get
credited
in
our
monthly
communications
to
pnp,
but
I
think
that's
it.
I
don't
actually
have
anything
more
on
the
SharePoint
framework
site
right
now,
so
everybody
has
been
more
and
more
and
more
or
less
concentrating
on
ignite
ignite
in
Atlanta
is
next
week
and
we
don't
have,
let's
say
humongous
amount
of
additional
things
for
this
week,
but
after
ignite
there
will
be
more
and
more
additional
interesting
stuff
in
the
queue.
B
A
So
a
little
quick
update
here
on
the
JavaScript
core
components
activity
continues
there
in
the
core
components,
as
always
we'll
talk
a
little
bit
about
contributions
and
how
you
can
get
involved
in
a
second,
but
first
I
want
to
pause
and
thank
everybody.
That's
contributed
so
far
to
that
core
component,
the
JavaScript
core
component
very
much
appreciate
it.
Thank
you
to
everybody
that
has
contributed.
A
It's
been
a
little
quiet
in
the
last
couple
weeks,
but
we've
got
a
few,
a
nice
little
fixes
from
some
folks
and
then
we've
also
have
some
folks
reports,
some
issues
which
is
fantastic
love
to
get
those
issues
in
I.
Don't
love
to
get
issues
in,
but
I
do
love
when
they're
reported,
so
we
can
get
them
fixed
and
resolved
and
just
make
a
better
product
for
everybody.
But
I
really
appreciate
that
and
as
always
thank
you
to
everybody
is
contributed
weather
reporting
issues
or
contributing
code
through
poor
requests.
A
It's
very
much
appreciated
by
myself
and
rest
the
core
team
as
well.
Your
names
will
bubble
up
to
the
monthly
patterns
and
practices
meeting
to
get
you
some
extra
recognition
there
I
think
I
haven't
said
this
for
a
couple
weeks
or
maybe
I
have
again,
please
double-check
the
author's
file.
If
your
name
is
not
correct
or
you
would
like
to
be
listed
somehow
differently,
for
example,
with
a
company
name
as
well,
or
something
like
that
very
happy
to
make
those
changes
very
happy
to
get
folks
the
recognition
they
absolutely
deserve
their.
A
So
thanks
again
to
everybody
that
has
contributed
so
what's
been
happening,
I've
kind
of
condensed.
It
will
talk
about
this
a
little
bit
here
in
a
second
but
I'm
kind
of
condensed.
Before
we
used
to
kind
of
step
through,
we
had
a
stand
up,
and
then
we
had
a
what's
going
on
in
in
the
Yammer
and
the
git
er
and
all
those
sort
of
things
so
I've
kind
of
condensed
it.
A
The
one
slide
so
what's
been
happening
just
to
kind
of
not
break
things
out
and
make
the
conversation,
hopefully
a
little
bit
more
clear
as
to
what's
you
know,
been
happening
all
up
here
around
the
JavaScript
core
component,
so
to
go
through
these
a
few
issues
reported
with
the
post
install
dependency
on
typing.
So
let
me
explain
this
a
little
bit
and
explain
what
we're
doing
to
resolve
this
so
now
that
a
lot
of
folks
are
starting
to
actually
install
the
package
in
their
sharepoint
framework
Jax.
A
It
was
found
that
and
I
I
knew
this,
but
I
didn't
know
it
was
sort
of
a
blocker.
So
you
have
a
dependency
on
this
library
called
typing's,
which
is
what
we
chose
within
the
core
component
to
use
to
pull
in
our
typing
information
for
the
typescript
project
and
I
added
that
I
thought
at
the
time,
hopefully
as
a
post,
install
step
for
the
the
library.
So
when
you
installed
it,
you
would
automatically
get
the
Taipings
added
to
your
project,
and
that
would
be
great
except
the
the
problem
with
that
approach
is
not.
A
Everybody
has
typing's
and
you
have
to
have
typings
globally
installed
in
this
case,
to
make
this
integration
work.
So
not
everybody
has
typing's
installed
and
not
everybody
wants
to
use
pipings
at
all
right.
They
might
have
some
other
tool
as
with
everything,
an
open
source,
there's
other
tools
out
there.
So
what
the
steps
we've
taken
I
have
removed.
A
We
will
update
the
documentation,
both
the
getting
started
using
the
library
documentation
in
your
projects
and
getting
in
the
getting
started,
contributing
documentation
to
reflect
that
they'll
now
be
an
extra
step
to
install
the
Taipings,
but
I'm
going
to
make
sure
in
the
documentation
it's
going
to
list
out
what
the
Taipings
are
that
are
required
have
sample
typing's
that
JSON
files.
If
you
want
to
continue
to
use
typing's
or
you
can
take
the
values
from
there
to
whatever
tool
you
might
want
to
use.
So
hopefully
this
is
removing
a
optical
to
adoption.
A
Obviously,
I've
talked
a
lot
in
the
past
about
keeping
those
two
hats
on
both
the
development
hat,
the
contribution
hat
and
then
as
well,
the
hat
for
usage
and
consumption
of
our
work.
So
hopefully
this
is
going
to
help
with
that
consumption
story,
but
that
work
is
not
checked
in
yet
so
for
now
no
changes
to
what
anybody
is
doing
and,
like
I
said,
we'll
update
the
documentation
and
make
that
very
clear
when
I
do
like
the
105
release,
blog
post
I'll
explain
it
again
in
there
as
well
as
described.
A
You
know,
with
pointers,
additional
steps
for
install
so
great
feedback
on
that
really
appreciate
a
malbec
and
based
on
some
other
folks,
actually
internally
here
at
Microsoft
I
think
they
caught
that
one
so
we'll
get
that
result
appreciate
that
getting
robbed
questions
on
large
list,
I've
seen
there's
a
couple
out
there.
Now
there's
been
some
of
the
past
on
large
lists.
We
are
using
the
rest
api's
for
our
calls
and
as
such
we
are
limited
by
with
the
API
is
support,
and
that
is
a
good
thing.
We
don't
want
to
circumvent
those
api's.
A
So
if
you
are
working
with
a
large
list,
you
will
have
to
get
it
in
paged
chunks
of
data,
which
is
from
a
performance
standpoint
much
better
and
would,
unless
you're
doing
something
via
like
a
timer
job.
I
would
encourage
you
that
I
I
can't
really
think
of
a
good
case
in
the
browser
where
I
would
need
to
get
all
the
items
from
a
very
large
list.
So
again,
please
do
think
about
performance
when
working
with
large
lists.
A
If
you
do
need
to
get
the
data
from
a
large
list,
we
do
support
through
the
REST
API.
You
can
actually
do
there's
a
paged
items
collection
and
you
can
go
through
that
method.
To
get
and
aggregate
all
those
items
you
could
store
them
all
an
array
or
you
know
I,
would
more
recommend
kind
of
process
to
them
as
they
come
through
sort
of
speed,
things
up
and
again
help
performance,
but
we
are
limited
by
the
API
as
we
should
be,
so
we
won't
be.
A
A
So
question
on
using
the
blob
/
file
types
from
form,
I
tried
to
answer
that
in
the
issue.
So
hopefully
that's
clear,
I'm,
not
sure.
If
the
gentleman
that
I
question
is
on
the
call
have
a
look
at
that.
Please
do
let
us
know
if
that
works,
for
you
or
not,
and
we'll
try
and
get
you
sorted
out.
There
matching
questions.
There
was
a
question
on
patching.
A
Remember
the
batch
object,
has
its
own
execute
method,
and
so
that
execute
method
is
needs
to
be
called
that
the
the
methods,
all
the
the
what
I
call
child
promises
will
not
be
executed
until
that
batch.
That
executes
is
called
as
they're
sent
in
that
batch
and
then
thatching
does
have
limits.
So
large
batches
may
not
all
complete
something
to
keep
in
mind
as
well,
working
with
batching
and
then
one
other
note,
as
of
the
one
dot
0
dot
for
release
the
bats.
A
Execute
method
does
return
a
promise
and
that
promise
is
designed
to
resolve
once
all
of
the
child
promises
contained
in
that
batch
have
resolved.
There
might
be
a
bug
with
that
related
to
post
requests,
somebody's
mention
that
out
there
in
the
issues
list,
having
a
chance
to
look
at
that,
so
there
might
be
an
issue
but
get
requests.
A
So
if
you're
batching
a
set
of
get
requests,
those
should
all
be
working
just
fine
and
as
expected
there
we
are
gotten
some
great
feedback
again
from
the
community
that
when
using
a
library
with
web
pack
and
then
using
so
importing,
say
the
web
object
and
then
trying
to
package
your
project
in
web
pack.
So
if
you
wanted
to
open
a
web
with
a
specific
URL
and
not
directly
from
like
the
PM
p
dot
s
P
dot
web
kind
of
entry
point,
there
are
some
issues
around
packaging
of
specifically.
A
While
those
classes
are
exported,
there
seems
to
be
an
issue
with
webpack
picking
those
up,
and
essentially
the
idea
is.
We
need
to
sort
of
export
those
near
the
top
level,
so
working
on
that
again,
great
feedback
from
the
community
and
so
working
on
that
I'm,
trying
to
start
out
with
exporting
the
more
limited
set
of
things.
A
So
we
don't
clutter
the
entire
interface
but
again
that'll
be
part
of
leading
in
the
next
point
105.
So
once
in
my
mind,
105
once
we
get
those
typing
issues,
I
mentioned
resolved,
which
those
are
resolved
but
then
also
getting
this
export
stuff
and
this
web
pack
stuff
resolved
I
think
we'll
be
all
set
to
do
a
10,
5
release,
I
think
that's
enough.
A
Improvements
to
you
know
provide
value
to
another
release,
but
so
targeting
that
tentatively
in
my
head
for
the
week
after
ignite.
So
if
you
have
other
things
out
there
in
the
community
that
you're
working
on
or
would
like
to
get
into
an
upcoming
release,
you've
got
about
a
two
weeks
notice
for
getting
that
stuff
in.
A
A
hitter
is
a
great
place.
If
you
have
quick
questions
or
just
you
know,
sort
of
more
informal
and
then
use
the
community
for
those
times
when
you've
got
something.
You
know
that
might
be
worth
sharing
with
the
whole
community
right.
So
you've
got
a
question
that
you
think
might
apply
to
lots
of
folks.
You
know
use
that
community,
because
that
way
we
can
sort
of
share
that
information
out.
I
think
the
git
er
is
great
for
quick
things,
but
but
stuff
tends
to
get
lost
in
this
sort
of
stream.
A
So
that's
what's
been
going
on
looking
forward
to
the
105
release
again,
I
think
some
great
improvements
and
fixes
to
our
usage
story,
which
I
think
is
super
valuable
opportunities
to
contribute,
want
to
remind
everyone
again
write
a
web
part
if
you've
written
a
web
part
would
love
to
have
you
demo
it
on
this
call,
simple
or
complex
I
think
it's
very
valuable
for
us
to
all
learn
from
each
other
and
see
what
folks
in
the
community
you're
doing
I
know
a
lot
of
the
time.
I
see
folks
do
stuff.
A
I
personally,
maybe
would
never
have
thought.
Oh
so
I
think
it's
very
valuable,
so
it
encourage
everybody
have
a
shot
at
writing
a
web
part
in
the
SharePoint
framework,
and
let
us
know
it
would
love
to
have
you
show
it
off
on
this
call
and,
as
always,
just
bonus
points
for
using
the
jas
core
library
vote
imaginary,
bonus
points
that
don't
actually
get
you
anything,
but
the
bonus
points
nonetheless,
testing
any
help.
We
get
like,
I
said
earlier,
getting
great
feedback
and
great
issues
coming
in.
A
Don't
love
when
there's
issues
but
I
love
getting
them
reported,
so
we
can
get
them
resolved.
So
if
you're,
using
library,
testing
library,
let
us
know
if
you
run
into
problems
because
we
do
want
to
address
those
as
quickly
and
as
efficiently
as
we
can
help
writing
tests.
I'm
gonna
keep
saying
that
probably
as
long
as
I
live
so
help
writing
tests.
Just
comment
on
issue
number
42
grab
an
area
and
then
still
looking
for
anybody.
They
would
like
to
help
with
with
styling
our
documentation
site.
A
So
I
think
it's
a
really
high
visibility
opportunity
for
someone
that
might
want
to
get
involved.
There
has
a
lot
of
CSS
experience
and
it
uses
handlebars
templates.
So
if
you
will
already
know
or
want
to
learn,
handlebars
great
opportunity
there,
but
super
high
visibility
opportunity
to
contribute
and
styling
the
site,
and
if
you
have
questions
on
how
to
get
started
with
that,
there
is
a
github
issue
for
that.
You
can
comment
on
and
I'll
respond
to,
try
and
help
you
out.
A
If
you're
looking
to
get
involved
with
styling
the
documentation
and
by
styling
I
mean
you
essentially
have
free
reign
to
lay
out
the
site,
improve
the
navigation
experience,
it
cetera
I'm
wide
open
to
suggestions
on
that.
So
changing
the
specialist
group
meeting
to
bi-weekly
we
mentioned
this
last
week
and
I
think
it
makes
a
lot
of
sense.
So
our
upcoming
schedule
for
this
meeting
is
going
to
be
today.
September
22nd
we're
going
to
have
the
meeting
as
everybody
here
on
the
call
is
guest.
A
Then
we're
going
to
do
a
special
live
from
ignite
meeting
at
the
office.
Dev
pnp
booth
on
September
29th.
That's
going
to
be
at
ignite.
So
if
your
attic
night
open
invite
to
come
on
by
and
be
part
of,
the
show
we're
gonna,
try
and
hopefully
won't
be
too
loud.
Folks
to
be
able
to
hear
is
still,
but
so
come
by,
say:
hi
be
live
on
the
webcast
from
ignite
and
we'll
be
gathering
questions
and
ideas
and
and
attic
night
as
well
so
come
by
just
kind
of
generally.
A
The
pnp
booth,
if
you're
at
ignite,
meet
folks
from
the
core
team,
we're
they're
kind
of
on
a
revolving
schedule,
would
be
really
excited
to
meet
anybody.
That's
going
to
be
there
from
the
community
and
it's
your
feedback
both
on
the
jas
core
component.
This
special
interest
group,
as
well
as
you
know
anything
patterns
and
practices,
so
stop
on
by
and
see
us
and
then,
after
that,
our
next
meeting
will
be
october.
13Th,
so
we'll
be
skipping
a
week
and
then
we'll
go
from
there
to
having
an
every
other
week.
A
Meeting
after
october
of
13
and
the
goal
here
is:
we've
gotten
again
responding
to
feedback
from
the
community.
We
have
a
lot
of
patterns
and
practices
meetings
and
a
lot
of
folks
were
saying
it
was
just
too
much
and
they
were
having
to
sort
of
skip
things
that
they
might
want
to
go
to,
but
that
they're
there
week
was
having
patterns
and
practices
meetings.
A
You
know
almost
every
day
right
and
so
our
goal
here,
and
not
just
for
the
special
interest
group
we're
doing
this
kind
of
all
up
in
patterns
and
practices,
is
to
have
fewer
but
more
valuable
meetings.
I
think
all
of
these
meetings
are
valuable,
but
I
think
if
we
can
pack
a
little
bit
more
content
into
a
bi-weekly
meeting,
make
it
a
little
bit
more.
A
You
know
have
more
stuff
happen
between
the
meetings
write,
a
weekly
cadence,
not
a
lot
happens
each
week,
but
hopefully
now
with
a
bi-weekly
meeting,
will
get
a
little
bit
more
happening
each
meeting
and
have
a
little
bit
more
updates
to
share
as
we
go
through,
but
will
also
remain
active
on
the
various
social
channels,
so
the
Gator
github,
the
community,
those
are
still
going
to
go.
You
know
every
day
feel
free
to
post
there,
but
these
meetings
are
going
to
move
to
bi-weekly,
we'll
be
updating
the
invitation
and
then
as
well.
A
I
will
up
for
the
first
couple
of
skip
weeks.
I
will
join
in
and
probably
just
be,
showing
a
static,
slaw,
reminding
folks
we've
gone
to
bi-weekly,
so
just
won't
update
everybody
on
the
call
for
that.
Hopefully
we
won't
lose
anybody
in
the
transition,
and
so
now
I
think
waldeck
is
on
the
call.
We're
all
set
got
a
really
cool
demo
coming
up
waldeck.
Are
you
all
set
I.
C
Awesome
so
the
sample
that
I
like
to
show
you
guys
today
is
one
that
uses
react
and
the
Microsoft
graph
to
show
you
the
list
of
upcoming
meetings
for
the
current
user.
So
with
that,
let's
add
the
web
more
to
the
page.
The
workbench
and
I
am
logged
in
I'm
cheating.
Sorry
for
that,
it's
likely
the
fact
that
you
get
yes.
So
now
you
can
actually
see
the
way
it
works,
but
actually
skip
the
first
important
step
right.
So
imagine
let
me
clear
it
again.
B
Chester
kind
of
elaborate
on
that
one
so
obviously
won't
be
every
single
time,
you're
accessing
a
page
with
this
kind
of
a
web
part,
because
that
is
storing
the
access
token
for
that
app.
So
it
will
be
the
first
time
and
then
there
will
be
the
two
weeks
refresh
token
for
the
app
by
default
right
product.
Yes,.
C
But
then,
with
implicit
flow
you
don't
get
get
the
Refresh
token.
So
that's
a
security
measure.
That's
in
place,
yes,
gasps!
It's
point,
yeah
good
point,
so
we
will
explain
all
of
it
so
I.
Actually,
now
that
we
talked
about
the
micelle
graph
and
and
all
implicit
flow
in
more
detail,
we
will
have
tutorial
that
will
and
will
have
actually
both
tutorial
and
the
guidance
that
will
explain.
All
of
that.
B
Then
I
have
to
actually
slightly
elaborate
on
that
one,
because
it's
not
just
for
Microsoft
craft
right,
because
it
could
hear
various.
It
could
be
your
custom
web
service,
which
is
which
could
be
connected
to
your
own
premises
as
an
example.
So
it
could
be
whatever
custom
web
api,
which
has
a
service
bus
to
connect,
the
dawn
premises,
to
get
data,
and
all
of
that.
So
it's
not
only
microsoft
craft
but
anyway
the
process
exactly
the
same.
Yes,.
C
So
so
it
is
relevant
to
everything
that
you
have
set
as
a
secured
with
a
with
a
ad
yeah
yeah.
So
with
that,
let
me
just
finally
click
the
button.
Ok
and
now
pay
attention,
because
it
will
go
very
fast
because
I
am
already
SAS
and
in
the
only
thing
that
you
will
see
is
pop
up
that
that
pops
up
disappears
and
it
works.
C
C
C
In
react,
and
actually
only
refresh
the
web
part
or
the
the
part
of
the
web
part
that
shows
the
data
right
so
with
that
we
can
really
easily
do
that,
and
what
you
see
eventually
is
that
we
reach
out
to
the
Microsoft
graph
and
I
can
show
you
that
in
the
network
stack
so
here
you
can
see
that
we
have
the
whole
all
flow
and
we
get
the
tokens.
So
if
you
write
really
fast,
you
can
get
my
access
token,
which
is
good
for
the
next
two
minutes.
C
And
then,
when
I
convert
them
to
you,
you
you
you
you
you
to
see.
It
turns
out
that
what
one
of
the
events
is
not
today
but
a
but
actually
tomorrow,
so
that
that's
why
we
get
for
you
for
events
here,
but
you
only
see
three
on
a
page
so
the
way
it
works
and
that
sample
depending
on
when
you
watch
the
video
or,
if
you
are
now
in
a
call,
will
be
available
to
you
very
soon.
C
Right
and
it
actually
is
available
in
the
dev
branch,
and
it
will
be
available
as
an
official
sample
approved
and
check
verified
soon.
So
it's
a
react
with
a
part
where
we
have
one
component
that
does
all
of
the
job
and
we
use
the
80
GS
library
to
actually
authenticate
with
us
and
80.
Oh
and
we
use
it
with
implicit
flow.
C
So
for
that
the
first
step,
if
we
go
to
azure
to
our
at
your
portal
at
your
ad,
actually
there's
the
nice
thing
since
not
that
long,
you
have
the
ability
to
access
your
as
your
ad
apps
from
the
new
portal,
which
is
an
old
vet
new
now,
but
that
ability
is
really
great
and
although
the
interface
isn't
exactly
the
same,
the
one
thing
that
we
can
really
easily
do
is
edit
the
manifest
directly
in
browser.
So,
for
example,
here
let
me
go
all
the
way
back
here.
C
I
am
in
my
ad
I
choose
apps
from
here.
I
get
the
list
of
all
my
apps
that
I
created
I
open
this
app
I
can
click
the
manifest,
and
here
I
can
actually
see
the
contents
of
the
manifest
in
browser.
So,
if
I
wanted,
for
example,
to
enable
implicit
flow
in
the
past,
I
would
have
to
go
to
this
page.
I
would
have
to
to
click.
Manage
manifest.
Download
manifests
open
that
in
editor
edited
upload.
It
again
here.
I
can
do
all
of
that
directly
in
browser.
C
So
I
give
you
a
year:
I
I
can
choose
all
implicit
flow.
I
can
set
it
the
truth,
save
and
I'm
done,
but
then
also
in
our
end.
So
that's
my
app
that's
how
my
web
part
get
access
to
tune
a
calendar
right
and
it
will
refer
to
do
it.
I
have
to
grant
it
access
to
my
calendar
and
I.
Do
it
by
Taipings
one
of
these
goods
and
then
another
one
which
I
know
by
heart,
know
which
I
don't
so
actually.
C
For
this
part,
although
you
could
edit
it
here,
if
you
need
the
goods,
it's
just
easier
to
go
to
the
outside,
and
here
you
can
choose
that
you
want
to
have
the
microsoft
grass
and
you
can
just
pick
the
right
permission
here
from
the
list,
which
is
read
user
calendars
and
that
will
translate
internally
into
one
of
these
two
entries.
I.
Don't
know
which
one
well.
B
B
C
Exactly
that,
because
that's
actually,
if
you
think
about
all
interested
flow,
the
contract
between
so
the
only
way
as
your
ad
can
trust,
whoever
issues
to
request
his
base
on
URL
of
the
page.
So
that's
the
contract
between
the
web
part
and
a
ad
that
definitely
says
that
I
am
the
leopard.
I
am
the
one
who
you
can
trust
right,
because
if
you
think
about
it,
there
is
no
other
way.
So
eventually
you
will
end
up
with
multiple.
C
C
So
that's
definitely
a
thing
that
you
have
to
take
into
account
and
that's
definitely
I
think
that
we
will
include
in
the
guidance
how
to
work
with
that.
Once
all
of
that
is
in
place,
you
can
use
a
towel
jas
actually
sign
in
and
older
is
simple
and
comes
down
to
calling
this
authentication
on
text
bubble.
C
Whole
game
and
80
GS
library
will
take
care
of
all
of
the
flow
and
login
page
papa
page
and
all
that
and
of
course,
for
that
you
have
to
pass
some
additional
info
like,
for
example,
the
ie
ie
D
of
your
app
on
the
endpoints
to
which
you
want
to
have
access.
So
you
have
to
pass
all
of
that,
but
once
you
do
you
do
and
you
pass
the
config
that
you
have
here
do
a
towel
which
you
do
in
constructor
here.
C
You
can
actually
also
say
that
you
want
to
use
pop
up
and
not
the
authentication
flow
based
on
a
hash
that
will
reload
the
whole
page
and
then
with
that
you
also
have
to
say
that
whenever
the
pop-up
comes
back,
you
want
to
react
to
it
and
with
that,
as
you
can
see
in
react,
we
only
change
the
state
of
user
at
which
we
keep
track
track
of
here
and
what?
What
a?
Never
that
changes?
We
actually
load
the
meeting.
C
So
initially,
this
I'm
in
state
is
false
and
then,
whenever
is
changed
to
true,
we
update
only
the
web,
part
or
or
actually
even
the
part
of
of
the
web
part
where
the
meetings
are
are
shown.
So
with
that
we
can
really
easily
and
lightweight
reacts
from
the
web.
Part
2
changes
that
that
take
place
out
out
out
of
it.
B
Gonna,
just
a
quick
comment
on
down
the
latest
point
with
world
accelerator
yeah
and
the
battery
care.
You
can
take
over
the
presentation
already,
but
really
the
challenge
mobile.
So
we
can
do
the
implants
that
flow
without
your
ad,
but
like
what
excited
the
challenge
of
this
one
doing.
This
is
the
fact
that
if
you
have
web
parts
from
multiple
different
vendors
and
there
would
be
a
malicious
client-side
web
part
which
is
sniffing
if
there's
any
any
client
IDs
in
the
page
or
access
tokens
in
debate,
you
could
theoretically
leak
that
now,
which
sounds
horrible.
B
But
then
again,
the
only
way
you
can
actually
put
the
client-side
web
part
on
a
page
is
that
the
tenant
administrator
explicitly
installs
the
client-side
web
part
and
makes
that
available.
And
while
you
are
doing
the
client-side
web
part
installation,
we
are
explicitly
raising
a
big
red
flag,
which
is
where
we
are
saying
that
you
need
to
trust
these
things.
B
These
are
almost
like:
the
classic
server-side
full
trust
web
part,
because
in
the
2007
or
2010
environments
or
2
2013
or
in
own
premises
in
general,
if
you're
using
a
server-side
code,
you
are
actually
accessing
anything
what
the
user
has
success.
So
in
the
same
way,
the
client-side
web
parts
are
full
trust.
Web
parts
they're
just
running
in
the
browser
side
running
in
the
JavaScript,
because
they're
built
with
JavaScript.
B
So
it's
not
really
that
much
different
than
it
when
it
goes
in
the
phone
solutions,
but
we
want
to
make
sure
that
people
do
understand
the
technical
and
the
security
implications,
so
additional
guidance
coming
out,
tutorials
coming
out
or
article
around
that
one
and
there
will
be
additional
support
natively
within
the
product
as
well,
around
the
implicit
flow
capable
or
kidding
access
on
the
data
in
in
creve.
When
we
don't
know
now,
let's
say
we
or
we
can't
comment
at
this
point.
B
A
Great
great
points,
guys
waldeck,
awesome
demo
as
always,
really
appreciate
it.
If
you
guys
haven't
checked
out
the
demos
that
are
the
samples
that
are
out
there,
please
do
there
some
really
valuable
content
out.
There
really
shows
off
some
great
techniques,
and
so
the
points
that
were
made
I
think
in
the
past
a
lot
of
developers
have
just
sort
of
defaulted
to.
You
know:
site
collection,
full
control,
kind
of
a
manifest
with
their
permissions
and
I.
A
Think
as
we
move
into
the
world
of
client
development,
it's
really
something
folks
are
going
to
need
to
concentrate
a
little
bit
more
on
and
remember
that
any
permissions
you
exposed
to
the
browser
whether
you've
written
anything
to
use
them
or
not
a
user
could
do
those
things.
So
we
actually
had
a
question
thing
goes
on
get
er
around.
A
Why
can't
we
just
elevate
users
using
a
client,
ID
and
secret
in
the
browser,
and
the
answer
is
theoretically,
you
could
I
suppose,
but
you're
exposed
mean
whatever
permissions
you've
given
to
that
client
ID
secret
pair
to
the
world,
and
then
anybody
could
take
that
and
do
anything
so
something
to
keep
in
mind.
I
think
permissions
folks
are
going
to
need
to
be
a
little
more
focused,
I'm
a
little
more
careful
around
exactly
what
gets
granted
to
what
both
in
the
azure
ad
space
as
well.
A
D
A
question
sure:
yes,
yes,
yeah,
we're
in
the
process
of
migrating
our
office,
2010
or
I'm.
Sorry,
our
sharepoint
2010
team
sites
on
Prem
to
office
365.
We
have
some
customizations
that
were
written
using
server
side
code
and
I
plan
on
reengineering
them
using
the
PMP
library
and
I'm
just
curious
what
the
best
place
to
store
that
is.
I
had
heard
some
mention
in
on
the
discussion
boards
that
people
thought
that
should
be
put
in
the
content
type
hub
site
so
that
it
would
be
accessible
by
everyone
that
I
could
have
just
one
copy.
A
So
lots
always
do
that
you
could
you
could
pick
a
SharePoint
site,
whether
it's
the
content
type
up
or
not,
and
use
that,
as
essentially
as
a
CDN
understanding,
you
have
to
make
sure
permissions
work
so
that
folks
can
get
to
that
particular
site.
So
some
folks
will
set
up
a
specific
site
collection
with
no
other
content
other
than
those
JavaScript
files.
So
you
can
do
that.
We
are
looking
at
getting
a
the
JS
files.
Add
it
to
a
public,
a
CDN,
but
a
lot
of
them
are
based
on
popularity.
A
So
I
would
encourage
everyone
in
the
call
to
star
our
repo
and
then
we're
looking
at
trying
to
use
a
shoot
wall.
That
can
remind
me
it's
ed.
Njs
com
provides
the
public
of
CDN,
so
we're
looking
at
that
and
there's
also
in
the
future
facebook
and
talk
two
timelines,
maybe
but
there's
actually
going
to
be
in
sharepoint
online,
I'm
not
about
to
say
something.
I
shouldn't
visit
your.
B
D
A
D
A
Recommend
that
because
then
you
can
just
make
the
permissions
that
site
just
anonymous
wide
open.
You
know
whatever
it's
your
organization
and
because
you
don't
necessarily
want
everybody
to
get
into
the
content
type.
Oh
and
you
then
have
to
worry
about
library,
permissions
and
all
that
kind
of
stuff.
So
I
like
the
idea
of
just
setting
like
sites
/,
CDN
right
and
then
our
library
jquery
will
react
whatever
else
you
might
use,
that's
a
great
place
to
just
put
it
and
use
that
as
a
CDN
and
one.
B
Additional
comment
on
whatever
we
are
about
to
release
related
on
this
one
dam
and
which
might
happen
still
today,
we're
just
we're
bending
for
a
final
reveal
is
going
to
actually
be
available
immediately.
So
so
it
will
actually
target
exactly
your
question
and
most
likely
it's
the
right
suitable
solution
for
you.
So
please
watch
step
toward
officer
comes
last
blocks
or
have
a
look
on
the
the
office
dev
Twitter
account
or
my
account
in
Twitter
or
FSB
and
FB
MP
Twitter
account
will
use
all
of
those
in
the
communications
so
great.
B
A
A
B
D
Yeah,
it's
just
an
example
of
the
question.
I
asked
to
bet
to
sue
things
back.
They
said
it
was
transcribing,
see
job
to
typescript.
Does
the
last
point
you
were
talking
about
with
privileges
have
been
sorted,
have
any
effects
on
the
elevated
privileges
issue
when
you're
accessing
lists
in
them
in
it
in
typescript,
and
that.
B
D
B
Actually
work
so
the
scenario
actually
how
you
can
make
the
real
elevation
to
work
is
that
because
the
typescript
is
always
convert
it
to
javascript
so
and
within
javascript,
we
do
not
have
a
native
way
of
elevation.
So
you
cannot
actually
say
that
in
the
sense
of
sharepoint
elevation,
because
30
point
elevation
means
that
hey,
I'm
not
going
to
actually
execute
using
that
particular
account
who's.
Using
the
browser,
I'm
going
to
execute
the
code
using
either
system
account
or
a
specific
alternative
account.
B
The
classic
way
of
doing
that
was
to
with
the
system
account
and
that's
the
how
everybody
has
been
using
that
within
the
server
side
code.
Now,
how
can
we
do
that
within
a
client-side
web
part
is
related
on
actually
what
Welbeck
showed
today,
because
it
relates
on
the
implicit
flow,
and
why
does
it
relates
on
that?
Well,
because
you
want
to
actually
build
a
custom
web
api
which
is
hosted
in
microsoft,
azure
and
that
will
be
secured
use
in
the
usher
security.
B
But
then,
within
your
client-side
web
part,
you
call
that
web
api
and
that
web
api
is
then
going
to
do
elevation
to
a
specific
account
or
to
an
appt
only
token
and
do
the
modifications
which
the
identity
hoods
are
executing
the
decline
side.
Web
part
does
not
have
permissions.
Hopefully
that
made
it
make
sense.
It's
just
the
natural
kind
of
a
limitation
in
javascript,
because
we
can't
in
JavaScript
I
cannot
say
that
hey
I'm,
going
to
run
the
chava
script
in
an
alternative
identity,
but
capability
doesn't
exist.
B
If
you,
if
the
person
who
is
running
executing
the
typescript
or
in
the
end
it
to
typescript,
is
always
a
converted
to
JavaScript
and
then
that's
executing
in
a
browser.
If
the
person
has
permissions
to
a
sharepoint
list,
then
those
permissions
are
still
there
if
the
person
does
not
have.
If
you
have
a
scenario,
let's
say
classic
scenario,
where
we
want
to
collect
feedback
from
our
end
users
related
on
whatever
event
or
whatever
you
probably
don't
want
that
all
of
the
intruders
have
access
to
all
of
the
other
people's
answers
as
well.
B
D
B
You
would
have
to
implement
a
secured
Web
API.
The
JavaScript
would
be
using
the
usher
ad
and
implicit
flow
to
call
that
Sakura
Web
API
hosted
in
Microsoft
the
share,
that's
the
one
which
is
then
using
app
only
or
a
specific
account
to
write
to
that
list.
So
answer
is
yes,
but
the
scenario
gets
much
more
complex
in
in
those
kind
of
scenarios
and
that's
why
we
want
to
actually
get
an
Oracle
out
and
a
sample
out
and
all
of
that
out,
so
that
people
are
able
to
understand
what
needs
to
happen.
D
B
So
all
of
the
modern
you
is
and
all
of
the
modern
UX
is
pretty
much
already
using
at
least
the
office
you
have
fabric
styles
and
within
certain
time
frame,
all
of
the
you
is
will
be
aligning
more
and
more
to
the
office.
You
I
fabric
react
components
as
well,
which
are,
however,
in
a
pretty
early
alpha
state.
B
Well,
not
in
all
of
us
data
would
say
better
stage
at
this
point,
so
the
chosen
framework
for
SharePoint
engineering
is
react,
but
it
doesn't
mean
that
you
have
to
do
react
and
then,
as
part
of
that
chosen
framework
to
react
with
it,
doesn't
matter
which
framework
you
actually
use.
You
should
be
aligning
the
office
you
I
fabric
and
the
SharePoint.
You
guys
will
be
aligning
the
office.
You
have
fabric.
B
Which,
by
the
way,
makes
a
lot
of
sense?
Let's
make
sure
that
if
we
are
preaching
for
every
single
developer
that
they
should
be
using
of
HCI
fabric,
wouldn't
it
make
sense
that
the
SharePoint
would
be
using
that
as
well
done.
Sir,
is
obviously
that,
yes,
it
does
just
takes
a
while
for
us
to
catch
up
as
well.
A
B
B
One
so
probably
shouldn't
say
this
out
loud,
but
the
later
today
there
will
be
a
massive
rebuilt
of
the
or
new
release
of
the
fabric
site,
and
that's
probably
related
on
that
one.
So
there
will
be
a
significant
changes
on
the
fabric
portal
and
which
will
then
have
much
more
additional
information
and
where
we
are
heading
and
all
of
that
and
that
probably
the
problem,
what
you're
seeing
is
related
on
done.
D
A
A
Thanks
to
waldeck
I
know
we
had
to
drop,
but
thanks
to
him
for
a
great
demo
again
and
just
a
reminder
if
anybody
writes
a
web
part
and
would
like
to
demo
it
on
this
call,
please
just
get
in
touch
complex
are
simple:
every
demo
is
valuable
and
it's
great
to
share
with
the
community
so
encourage
folks
who
have
interests
to
do
that.
So,
thank
you.
Everybody
appreciate
it.
They
said
you
have
anything
to
close
out
no.
B
Not
really
not
really,
we
will
update
the
invites
accordingly
and
by
the
way
on
I
chose
questions
on
the
office
hours
will
like
mentioned
yesterday
in
office
hours
will
reprint
the
office
hours,
say
special
interest
group
for
the
see
some
core
component
and
the
BMP
engine
and
the
powershell
we're
not
going
to
change
the
schedule.
So
if
you
do
have
office
hours
in
white
already
within
your
calendar,
that's
the
schedule.
B
We
kind
of
update
the
invite
just
to
have
additional
or
updated
text
and
description
and
we'll
work
with
patrick
to
get
the
javascript
interest
group
invite
updated
as
well
as
a
biweekly,
invite
what
I
think.
That's
it
dude
thanks
everybody
thank
you
for
joining
and
the
recording
will
be
available
within
24
hours.
I
think
that's
fair
cool.