►
Description
Recording of the SharePoint - SPFx and JavaScript (client-side) development Special Interest Group community call from January 30, 2020.
Topics covered:
Updates on SharePoint Framework from Microsoft SharePoint engineering, latest on PnPjs Client Libraries, Office 365 CLI, SPFx Reusable Controls, and on the PnP Yeoman Generator. Two demos were delivered:
1) Low-code SharePoint web part to provision Teams structures as personal apps. This demo is about surfacing SharePoint applications in Teams.
2) Using Microsoft Graph to get group member presence details in SPFx solution.
Also, in this session: Darrel Miller @Darrel_Miller, on the Microsoft Graph Developer Experience team, presented the case for layering a Graph Fluent API upon the PnPjs Core library. Feedback from the PnP Community is requested. This call was hosted by Patrick Rodgers (Microsoft).
• Demo: Low-code SharePoint web part to provision Teams structures as personal apps | Bob German (Microsoft) | @Bob1German
• Demo: Using Microsoft Graph to get group member presence details in SPFx solution | Luis Mañez (ClearPeople) | @luismanez
Additional details on topics covered during this call may be found in the SharePoint Developer Blog post for this call at: http://aka.ms/spdev-blog
All previously recorded SharePoint SPFx & JS Dev SIG community calls: https://www.youtube.com/playlist?list=PLR9nK3mnD-OXdcwfcHGsGr78nHWLRsv1x
All SharePoint PnP Developer Community demos: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWSbg0o9a7mx_E7s2u7h_o2
SharePoint PnP Developer Community channel on YouTube: https://aka.ms/spdev-videos
More information on SharePoint Framework library components is available at: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/library-component-overview.
You can download an invite for this bi-weekly community call at: http://aka.ms/spdev-sig-call.
For details around the open-source work being done by the SharePoint PnP Development Community, visit http://aka.ms/sppnp.
A
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group
bi-weekly:
sync,
it
does
January
30th
2020
I
always
have
to
glance
to
make
sure
you've
gotten
the
date
right.
So
our
agenda
for
today
is
latest
updates,
of
course,
on
SharePoint
framework
from
engineering
times
and
practices
program
updates,
and
we
got
three
great
demos.
A
First,
from
Bob
on
low
code,
SharePoint
webparts
to
provision
team
structure,
the
next
from
Louise
on
using
Microsoft
graph
to
get
group
member,
presents
details
and
then,
finally,
from
Darryl
a
discussion
around
how
the
Microsoft
graph,
JavaScript,
SDK,
fluent
API,
could
be
shaped
or
how
that
could
work.
I
wants
to
get
some
feedback
and
talk
to
folks
through
so
his
ideas
and
hear
from
folks
as
well
their
ideas
so
excited
for
that
conversation
as
well
and
in
the
interest
of
time
kind
of
want
to
get
moving
here
to
get
through
the
three
demos.
A
So
we
got
as
always
want
to
go
through
our
opportunities
to
participate
in
the
patterns
and
practices
program.
First
and
foremost,
we
definitely
encourage
everybody.
That's
interested
to
reach
out
to
us
about
doing
a
demo.
Those
demos
could
involve
anything
around
SharePoint
framework
and
anything
involving
any
of
our
at
PNP
offerings
and
then
really
more
generally,
anything
client-side
development
as
well
generally
fits
into
this
call,
so
you're
all
doing
neat
work
for
your
customers
or
for
your
companies.
Those
could
be
web
parts
or
application
customizers
something
around
provisioning.
A
I
would
love
to
have
you
get
on
the
call
and
share
that
with
the
wider
community
to
reach
out
just
reach
out
to
myself
or
visa
and
we'll
get
you
started
on
a
demo
just
like
for
my
folks.
We
are
booked
out
a
little
bit
on
demo,
so
it
might
not
be
like
the
very
next
call
that
we
can
get
you
booked
but
don't
be
discouraged.
A
We
will
get
you
booked
on
a
call
we'll
get
you
demoing
love
to
have
those
demos
and
I
know,
as
I've
said
before,
I
always
learned
something
neat
from
each
of
the
demos
and
I
hope
you
all
do
too
as
well.
You
can
always
contribute
on
github.
We
welcome
and
encourage
contributions
across
all
of
our
projects
on
github
and
those
contributions
could
take
a
number
of
forms.
You
can
report
issues.
A
Of
course
we
don't
like
issues,
but
we
love
to
hear
when
their
issues
simply
so
we
can
get
them
fixed
and
resolved
so
that
everybody
has
a
better
experience.
You
can
also
submit
request.
So
if
you
have
a
little
bit
of
time
and
you'd
like
to
help
out
with
either
fixing
an
issue,
perhaps
or
adding
a
new
feature,
adding
some
new
functionality,
this
is
for
any
of
our
libraries
absolutely
encourage
you
to
do
so.
You
know,
submit
those
pull
requests,
get
that
code
out
there
and
love
to
have
those.
A
It
really
speeds
up
dev
time
and
help
makes
everything
a
little
bit
better
for
everybody
again
and
then.
Finally,
if
you
have
a
little
bit
of
time
to
help
out,
sometimes
people
have
questions
in
those
issues
lists
they're
more.
How
do
I
kind
of
questions
you
might
know?
The
answer
to
those
questions
so
certainly
encourage
you
to
jump
in
and
help
out
those
folks.
If
you
happen
to
know
the
answer,
it
gets
them
an
answer,
a
little
bit
faster
and
just
helps.
A
You
know,
folks,
generally
in
the
community,
work
together
and
get
their
work
done
and
then,
finally,
of
course,
we
always
encourage
feedback
on
everything
we
do.
So
how
are
these
calls,
how
our
documentation?
Where
else
can
we
help
and
of
course,
positive
feedback?
Is
okay
too?
If
you
all
really
enjoy
something
we
do.
Let
us
know
we
can
try
and
do
more
of
it
or
bring
that
a
little
bit
more
to
the
floor.
Of
course,
if
you
need
help
getting
started
with
github
or
really
contributing
to
these
projects,
david
warner
has
started.
A
A
sharing
is
carrying
a
set
of
guidance
and
calls.
I
think
the
next
one
I
saw
is
tomorrow,
if
I'm
not
mistaken,
so
certainly
encourage
you
to
join
that
it's
a
great
place
to
ask
questions,
figure
out
how
to
use
github
how
to
make
contributions
and
then
get
your
questions
answered
in
kind
of
a
very
direct
format
there
so
encourage
you
to
check
that
out.
So
some
links
there
for
you,
a
kms,
SP
Doc's,
will
take
you
to
the
all
up,
SharePoint
developer
documentation.
A
So
that's
if
you're
new,
to
or
using
SharePoint
framework
as
well
as
add-ins
as
well
as
managed
code
solutions.
All
of
that
can
be
found
there
in
the
s/pdif
Doc's
SPF
videos
will
take
you
to
our
SharePoint
past
practices.
Youtube
channel.
That's
got
videos
not
just
on
the
recordings
of
all
of
our
phone
calls,
but
different
video
series
on
getting
started
or
using
different
pieces
of
the
app
PNP
ecosystem
of
things
and
there's
a
great
new.
Just
a
you
know,
kind
of
a
plug
for
p.m.
A
PJs,
great
new
video
series
coming
on
using
PPG
sv2
working
with
David
Warner
on
he's
been
doing
a
great
job
on
those
videos.
The
first
one
is
out
so
certainly
encourage
you
to
check
that
out
and
we'll
have
new
ones
coming
very
shortly,
but
there's
a
ton
of
great
content
there
across
all
of
the
P
and
P
offerings.
A
So
if
you
wanna
get
started
on
provisioning,
you're
looking
to
get
into
using
the
react,
controls
different
things
like
that,
do
you
check
out
the
videos
and,
if
you've
missed,
of
course,
any
of
our
phone
calls
that's
how
to
get
caught
up
and
watch
the
recordings
there.
Sp
dev
issues
takes
you
to
the
SharePoint
modern
SharePoint
issues
list.
So
that's
stuff
around
the
modern
SharePoint
experienced
as
SharePoint
framework.
That's
a
place
to
report.
Any
issues
ask
questions
and
folks
will
do
their
best
to
help
you
there
or
potentially
redirect
you
to
the
correct
place.
A
B
Cool
yeah:
this
is
not
gonna.
Take
too
long
from
a
shipment
framework
side
of
the
house,
because
the
1.10
came
out
quite
recently
few
updates
and
they
will
say
Twitter
tweet
earlier
today,
just
letting
everybody
know
office
dev
and
the
classic
office
there
for
twenty
one
or
twenty
K
thousand
followers
have
been
renamed,
and
it's
now
Mike's
resist
defied
developer
or
Microsoft
365
and,
if
asked
account
and
as
part
of
that
transition,
we
also
actually
flicked
our
office.
Debt
BMP
account
as
well
and
not
necessarily
related
on
that.
B
But
we
wanted
to
make
things
in
line
or
aligned
for
the
future
things
as
well,
so
they're,
most
announcement
official
announcement
that
we're
moving
in
a
way
from
office.
365
dev
has
snack
usage
as
well
to
the
mystory
justified
their
usage.
Spf
X
usage
will
be
still
SPF
X
because
no
name
changes
there
and
and
also
maybe
a
small
reminder
on
that.
One.
Please
use
these
tags
because
I
see
a
lot
of
tweets
and
COO
tweets
from,
but
the
people.
B
But
then,
if
you
don't
use
hashtags,
we
don't
actually
find
them,
but
this
personally
I
follow
hashtags
and
maybe
on
one
point
related
on
myself,
365
partners
and
practices.
We
are
looking
into
extending
that
side
also
for
non
dev
topics.
So
it's
not
that
our
community
is
only
limited
on
the
TIF
topics,
because,
especially
in
myself,
to
resist
if
I
SharePoint
I
mean
all
of
these
environments,
it's
not
just
about
dev.
B
It's
it's
a
combination
of
everything,
so
there
will
be
admin
scripts
and
PowerShell
script,
galleries
and
all
that
stuff,
if
sooner
or
later,
more
on
that
slightly
later
couch.
So
there's
a
quick
question
from
Russell
Crowe
is
office.
365
now
Microsoft
resisted,
that
is
the
official
transition
of
the
naming
in
office.
365.
So
you'll
see
one
of
the
official
marketing
material
being
transitioned
on
using
my
software.
It
is
to
five
rather
than
office,
365.
So
that's
what
it
means.
Now.
On
the
shipment
framework
side
of
the
house,
we
are
backing
krause
curve.
B
You
can
actually
see
the
nice
drop,
which
is
caused
by
always
the
holiday
season,
so
you
can
actually
see
the
holidays
impact
always
on
this
and
this
time
again
the
holiday
was
quite
long
from
the
early
mid
December
to
meet
Jen,
and
we
are
again
back
on
the
growth
track
on
the
usage
of
ship
and
framework.
So
everything
is
looking.
B
Good
people
are
adapting
our
patterns,
which
is
great,
so
it's
a
safe
bit
to
do
nice
of
teams
tabs
and
all
that
stuff
using
one
framework
as
well
on
this
roadmap
slide
and
nothing
actually
moving
from
here,
there's
no
ETA
for
the
next
version.
Yet
so
we
do
not
know-
and
we
don't
have
an
update
when
there
will
be
at
one
point
ten
point,
one
potentially
or
one
point:
eleven
we'll
see
how
that
one
goes.
The
next
big
things
will
be
the
apps
or
support.
B
So
you
will
be
able
to
get
you
up
on
framework
based
solutions,
even
though
they
would
be
targeted
on
teams
or
office
settings
in
the
app
source
and
you're
able
to
take
advantage
of
them.
The
unified
tool
chain
for
my
accessories
is
the
fiber
clothes
is
coming
as
well.
Probably,
you
can
expect
more
details
on
that
one
in
build
or
in
SPC,
because
that's
how
we
always
communicate
these
things
as
well,
but
we
keep
you
up
to
date
on
the
community
calls
as
well.
B
If
the
support
for
fluid
framework
and
works
faster
in
a
loop-de-loop,
hopefully
we'll
get
to
that
monthly
release
cycles
quite
fast
and
more
and
more
extensions
queued
up
as
well,
but
that's
it
from
my
side
to
quickly
update
on
the
on
the
situation.
Nothing
too
traumatic,
all
sense
to
last
two
weeks,
at
least
so.
Let's
go
to
BMP
Jason.
A
Two
updates:
we
did
release
a
to
0-2
and
we
actually
unpublished
2:01
because
of
the
the
module
difficulties
we
were
having.
So
apologies
for
that,
but
I
think
that's
all
resolved
now
and
we've
now
have
two
sets
of
packages.
So
the
at
P
and
P,
slash
SP
package,
for
example,
is
going
to
be
a
composed
of
ES
modules,
so
can
keep
using
that
for
SharePoint
framework
and
all
your
client-side
dev
needs.
A
And
then
we
have
a
separate
set
of
packages
now
for
common
je
s,
and
this
is
related
to
support
node
versions
that
don't
support
es
modules
or
node
apps.
That
can't
support
es
modules
and
all
of
those
are
just
mirrored
packages
that
are
gonna
be
of
the
form
like
at
P
and
P,
slash,
SP,
common
jeaious
and
there's
a
mirror
package
for
each
of
the
other
packages,
and
they
all
generally
work
the
same.
A
The
easiest
thing
to
do
is
to
split
them
into
two
packages,
and
that
way
each
can
have
the
exact
settings
and
and
module
shapes
that
they
need
and
I
want
to
say
thanks
to
everybody
who
helped
test
that
and
helped
report
those
issues
around
the
modules
and
for
your
understanding
as
we
got
through
that,
but
that
should
all
be
resolved.
Now.
Fingers
crossed
I,
like
I
mentioned
before
the
video
series
is
coming
out
first
videos
out
more
on
the
way
very
soon.
A
Those
are
great
really
excited
to
see
those
coming
together
and
then
to
0-3,
as
well
as
the
next
release
for
the
one
branch.
The
v1
branch
planned
for
February
14th,
so
we'll
have
fresh
updates
out
on
February
14th
that
202
release
really
was
just
to
resolve
the
module
stuff,
not
any
real
new
functionality
included
in
that
so
P
P
dot,
github,
/p,
p
GS
for
your
docs
hash
tag,
PG
us
on
Twitter.
A
You
always
follow
me
at
mediocre
bowler
on
Twitter
for
all
your
pee
and
PJs
updates
office,
365
CLI
new
preview
version
available
2.6
with
new
commands
for
exporting
custom
power
platform,
connectors,
retrieving
information
about
Yammer
groups,
five
new
commands
for
reporting
on
SharePoint
usage,
removing
the
graph
schema
extra,
not
removing
the
scheme,
extensions
from
the
CLI,
removing
the
commands
to
remove
the
graph
schema
extensions
from
a
graph
entity
object.
Daryl
can
correct
me
later
on
my
working
around
that
filtering
command
output
and
then
improved
performance,
and
then
it
some
improved
externalizing
of
SPF
X
dependencies.
A
So
a
great
improvements
great
to
see
that
preview
version
out
and
coming
along,
you
can
always
install
the
latest
beta
from
NPM
npm
install'
g
g
@
PE,
/
office365
CLI
at
next
hashtag
office
uses
five
CLI
on
twitter.
There's
a
get
ur
channel
there,
as
well
as
again
that
link
to
the
docs
certainly
check
out
the
CLI.
If
you
haven't
great
tool
to
have
in
your
tool
belt
around
cross-platform
managing
of
your
resources.
A
Next
up
the
reusable
SPF
X
controls.
This
is
a
set
of
two
libraries.
The
first
react:
controls
are
designed
to
be
used
in
the
body
of
your
webparts
or
body
of
your
application
customizers
to
help
display
content.
So
these
use
the
office
UI
fabric,
or
both
of
these
sets
of
the
controls,
use
the
office
UI
fabric.
To
give
you
a
great
out-of-the-box,
look
and
save
you
a
ton
of
dev
time
on
commonly
used
controls,
some
new
stuff,
there's
a
new
beta
117
out
for
the
react
controls.
A
These
are
the
body
controls,
so
automatic
localization
of
labels.
Some
bug
fixes
the
possibility
to
hide
deprecated
and
available
for
tagging,
equal,
false
terms
and
then
updated
the
telemetry
package
dependency
as
well.
For
those
controls,
the
116
is
the
current
version
of
the
property
controls.
These
are
controls
designed
to
be
used
in
the
Edit
pane
of
your
web
part.
So
the
again
giving
you
a
great
out-of-the-box
appearance
to
your
experience.
A
Saving
you
a
lot
of
dev
time
to
get
that
stuff
into
your
web
parts
and
out
to
your
users
so
check
both
of
those
out
more
information
can
be
found
at
the
links
there
at
the
bottom.
Github
is
SP,
FX
property
controls
for
the
property
controls
and
SP
FX
controls
react
or
the
content
controls
and
both
of
those
are
react
based
controls
so
definitely
want
to
check
those
out.
A
So
last
but
not
least,
the
SP
FX
generator
111
is
out
version.
111
of
the
generator
is
out.
This
is
a
SharePoint
or
I'm.
Sorry,
this
misspeak.
This
is
a
yeoman
generator
built
on
top
of
the
out-of-the-box
SharePoint
framework
generator,
so
you're
gonna
get,
as
I've
said,
a
real
quote-unquote
real
SharePoint
framework
project
with
all
the
same
dependencies
under
the
hood
from
Microsoft,
but
with
the
ability
to
have
a
lot
more
control
and
a
lot
more
options.
A
As
you
set
this
up
for
the
kind
of
dependencies,
you
include
the
libraries
you
include
and
so
forth
upgrades
in
this
111
version,
so
you
now
can
create
110
SharePoint
Framework
projects,
improved
yarn
and
P
NPM
supports
no
relation.
Microsoft
graft
tap
types
have
been
added
in
there
as
an
option
and
then
update
dependencies
for
handlebars
in
view
a
preview
of
the
office
UI
fabric
7
is
included
as
well
as
a
bunch
of
bug
fixes.
A
So
a
great
release
excited
to
see
progress
continued
to
be
made
the
generator
and
encourage
folks
to
use
that
to
help
them
get
started
on
their
projects,
especially
if
you
want
to
support
some
of
the
things
not
supported
right
by
the
out-of-the-box
generator,
so
a
great
way
to
kind
of
another
great
tool
to
keep
in
your
tool
belt.
So
keep
that
in
mind
before
getting
your
project
started:
npm,
install',
g
@
pu,
/,
generator,
SP,
FX,
documentation
there,
aka
OMS,
P,
&,
P
generator
and
then
as
well.
A
A
C
Everybody
doing
I'm
doing
real.
Well,
thanks
for
the
opportunity
to
be
on
the
call
today
sure
sure,
good,
all
right
so
yeah,
my
name
is
Bob
Sherman
I
work
with
partners
a
lot
here:
I'm
a
partner,
Technical
Architect
at
Microsoft,
and
so
I'm
all
I've
been
working
a
lot
on
teams,
applications
lately
and
a
lot
of
the
partners.
I
work
with
don't
have
a
lot
of
developers
and
so
they're.
Looking
for
those
low
code,
kinds
of
solutions
and
I
was
kind
of
inspired
into
this
whole
direction
by
at
the
team's
airlift.
C
Seeing
kara,
wanna
gotta
move
show
this
feature,
which
is
it's
just
a
link
here
in
the
team
sidebar
that
opens
up
the
learning
pathways
SharePoint
site.
So
this
is
just
an
amazing
training
capability
and
you
know
a
lot
of
great
work
that
went
into
this,
but
the
it's
a
SharePoint
site
that
gets
provisioned
by
the
SharePoint
provisioning
engine
and
here's
how
it
works
inside
of
teams.
So
what
she
did
here
is
actually
really
pretty
simple
right
teams
has
a
manifest
just
like
SharePoint
framework,
and
you
can
see
here
that
it's
this.
C
This
particular
solution
has
some
static
tabs.
In
it
right
and
then
we're
just
taking
those
static
tabs
we're
installing
this
going
into
the
team's
administration
portal
and
I
guess
I'm,
maybe
I'll
take
the
time
to
show
this
or
not,
but
actually
coming
in
here
to
app
policies
and
painting
that
up
there
for
everybody
and
I'm
I'll
go
back
to
that
if
I
have
time
but
I'm
just
gonna
stay
quick
couple.
C
Other
examples,
though
it's
like
well,
why
couldn't
you
use
this
for
any
SharePoint
page
so
that
everybody
who
knows
how
to
build
SharePoint
pages,
could
use
this
kind
of
technique?
It
works
great
for
SharePoint
framework,
which
is
which
we
love
but
is
not
friendly
for
the
Loko
developers
right.
What?
If
I
wanted
to
do
this
without
look
well
outlook?
Integration
is
coming,
but
here's
a
here's,
a
quick
and
dirty
version
of
it.
What
if
I
wanted
to
use
this
with
a
power
app
I'm,
not
a
power
apps
person?
C
C
Tabs
static
tabs
are
only
visible
in
what
they
call
personal
view,
which
is
these
things
that
are
on
your
toolbar
on
your
sidebar
or
here
in
the
little
pop-up,
and
if
you
wanted
to
put
a
tab
inside
of
a
a
team
or
or
a
group
chat
right
and
and
here's
here's
another
example
by
the
way,
just
a
SharePoint
home
page
right.
Anything
a
list
could
be
useful
in
this
context
right
and
sort
of
make
an
app
out
of
it.
Maybe
I
want
to
actually
add
that
to
a
team.
C
So
let
me
show
you
an
example:
if
I
go
here
into
well,
actually
let
me
show
you
a
little
open
source
sample
so
in
order
to
open
this
up
to
low
code
developers,
who
maybe
aren't
gonna
want
to
write
the
configuration
code
to
do
this.
I
created
this
little
sample
web
part,
and
you
can
put
this
web
part
on
any
modern,
SharePoint
page
and
turn
the
SharePoint
page
into
a
configuration
page
that
works
in
teams.
So
it's
it's
really
simple.
C
C
So
what
I
can
now
do
is
take
this
URL
here
of
the
configuration
page
that
I've
just
created
and
this
time
I'm
going
to
instead
of
manually,
editing
the
the
team's
manifest
I'm
going
to
use
a
tool
called
app
studio,
team's
app
studio
and
here's
here's
a
little
SharePoint
tabs
app
and
inside
of
there
I've
just
pasted
this
URL
to
that
configuration
page
right.
So
I've
got
a
couple
personal
tabs
here.
These
really
don't
have
anything
to
do
with
my
demo
that
they
would
they
actually
work
here.
C
Underneath
of
this
personal
experience,
but
I
want
to
show
the
the
configure
about
the
configuration
tabs
so
I've
got
my
wet
apart,
set
up
on
a
page.
I've
got
the
page
URL
as
my
team
tab.
Now,
if
I
go
to
test
and
distribute
this
I
can
install
it
from
here
and
I
can
put
this
into
a
team
or
into
a
group
chat.
So
let
me
pick
a
team
and
I'll
just
go
ahead
and
put
this
into
the
amazing
project.
Team
set
up
the
tab
and
what
will
happen?
C
Is
teams
will
open
up
the
configuration
page
and
as
it
does
it,
it's
actually
going
to
show
my
web
part
here
on
that
little
page.
So
I
can
pick.
Let's
look
at
the
autonomous
vehicles
we'll
put
that
in
there
as
a
tab
and
save
that-
and
this
is
really
only
like
five
lines
of
code
inside
that
does
the
configuration
most
of
the
code
and
it's
there's
not
a
lot
of
code.
C
Most
of
the
code
is
just
giving
the
user
the
choices
and
stuff,
but
even
that's
not
very
much
note
that
I
can
also
come
back
here
now
and
change
the
settings
on
this
tab
and
I
go
back
to
that
same
configuration
experience.
No
I
really
want
the
research
page
on
here.
Please
and
that
changes
the
page,
but
not
the
name
of
the
tab,
is
just
kind
of
that's
a
different
function
here.
So
I
can
do
that
manually.
C
So
that's
really
it
I
mean
there's
not
a
lot
there,
except
for
I
feel
like
this
could
be
extremely
powerful
for
loco
developers.
I've
written
a
couple
of
blog
articles
on
this
on
how
to
get
started
with
all
the
details
of
how
to
set
up
a
learning
pathways
and
then
how
to
use
this
new
configurable
web
part
to
build
these
kinds
of
solutions
into
group
chats
and
teams.
So
that's
it
and
maybe
I
took
less
than
10
minutes,
giving
the
other
demos
more
time.
I
knew
this
would
be
a
simple
one.
Great.
C
In
this
in
this
world
of
SharePoint,
you
find
yourself
writing
these
little
pieces
of
glue
code
right,
and
this
is
a
perfect
example.
It's
just
this
little
piece
of
glue
code
that
opens
up
a
whole
set
of
scenarios
for
people
who
don't
who
don't
want
to
open
up
start
coding
in
SharePoint
framework
boom,
settle
and.
B
I
have
to
save,
as
I
hear
from
my
sign
that
that's
that's
a
great
example
of
the
simplicity
of
surfacing
SharePoint,
specific
capabilities
as
an
application
in
teams,
because
teams
isn't
kind
of
an
application
host,
and
this
this
shows
how
simple
it
is
actually
to
serve
ace,
individual
applications
and
I'm
functionalities,
plus
the
fact
that
now,
after
ignite
2019,
we
we
support
the
private
apps
and,
and
you
can
easily
make
those
things
happen
as
well,
so
really
really
cool
stuff
yeah.
Thanks
all.
D
Yeah
the
sample
that,
by
the
way
there
is
already
available
in
the
weight
point
producer
and
David,
will
text
the
link
in
there
in
which
I
take
a
minute.
Thank
you,
sir
yeah
I'm
gonna
show
you
how
we
can
use
the
new
presence
and
point
in
the
graph
API
to
get
the
presence
information
of
the
different
members
of
an
existing
group
into
SharePoint
so
before.
D
So
yeah
I
have
from
Tim
site
morale
teams
I
created
on
here.
So,
as
you
can
see,
there
are
five
members
and
with
the
out
of
the
box
and
person,
information,
there's
no
presence
at
least
not
so
far,
so
I
thought
it
was
good
to
create
the
web
part
that
uses
this
API
and
give
us
the
same
members
information
but
with
the
presence
I
con
as
well.
So
let's
see
how
it
works
in
the
warpage.
The
web
part
is
running
here.
So
if
we
have
the
presence.
D
D
It's
saying
VC
now:
okay,
so
before
diving
into
the
SPF
Xcode
I'm
gonna
show
you
how
we
can
use
the
endpoints
just
from
postman.
So
we
can
see
the
kind
of
thing
requests
we
need
to
do
and
the
kind
of
the
response
we're
gonna
grab
from
the
from
the
endpoint.
So
here
in
postman,
I'm
using
the
Microsoft
graph
postman
collections,
another
open
source
project
with
a
bunch
of
requests
in
in
graph,
which
is
really
a
great
resource,
so
I'm
gonna
grab
a
new
access
token,
just
in
case.
D
D
So
in
this
case
we
need
to
do
a
post
request
to
the
a
communications
get
presences
by
user
ID
and
we
need
to
send
a
list
of
the
different
user
IDs.
So
if
we
send
a
request,
you're
gonna
get
for
each
of
the
users
with
the
user
ID.
So
you
can
do
the
match
the
availability
and
activity
and
by
the
way,
if
you
are
sending
a
user
ID,
that
is
not
actually
a
valid
user
ID
in
your
directory.
D
You
are
just
getting
the
presence
unknown,
so
the
request
is
not
gonna
fail,
but
you
are
getting
presence
unknown
in
the
in
the
response.
So
these
are
the
two
different
end
points
in
the
graph
API
to
get
presence
information.
So
let's
take
a
quick
look
to
the
coding
spear
facts
and
actually
before
that
I'm
going
into
the
serpent
admin
center,
because
in
order
to
use
these
endpoints
in
the
in
SPF
edges
in
the
graph
client,
we
first
need
to
grab
permissions.
D
We
need
to
add
the
present
with
all
permissions
for
the
Microsoft
graph,
API
and
I
thought
this
using
the
great
office
265
CLI.
So
in
the
readme
file,
you
have
the
command
that
you
need
to
run
in
order
to
add
the
permission
today
to
the
service
principle
for
the
scope
presence
with
all.
So
once
we
have
the
scope
avid
into
the
into
the
permissions,
we
can
call
the
the
endpoint
using
the
graph
client,
and
this
is
what
I'm
about
the
solji.
D
That
is
doing
the
call
to
the
graph
API
as
well
in
order
to
get
all
the
different
members
of
the
of
the
sample
inside.
So
as
you
can
see,
we
are
calling
the
groups
Airport
with
a
group
ID
and
the
members
and
that's
what
I
give
us
the
different
members
of
the
of
the
group
and
and
just
will
buff
it
into
a
custom
interface
and
returning
that
dictionary
to
them
and
to
the
main
function
and
then
I
just
get
it.
D
The
different
user
IDs-
and
the
next
call
is
the
gang
members
presence
and
if
we
take
a
look
to
this
function,
this
is
doing
the
post
to
the
graph
API
upon
that.
I
just
showed
you
a
minute
ago
in
postman.
Get
presence
is
by
using
ID
with
the
different
user,
IDs
and
F.
We
got
in
there
in
the
first
call,
and
this
is
what
I'm
returning
the
dictionary
of
the
different
people,
but
in
this
case
included
also
the
information
from
presence,
availability
and
activity.
D
The
display
name
of
the
user
I'm
also
so
in
the
department
and
the
activity
in
the
tertiary
takes
extra
information
with
the
activity
and
the
presence
property
is,
is
gonna
serve
you,
the
availability
from
the
from
the
graph
API,
and
in
this
case
we
need
to
do
some
kind
of
conversion,
because
currently
is
not
the
same
information
that
is
coming
back
in
this
availability
feel
from
graph
and
the
options
that
we
have
in
this
present
fill.
So
basically,
I'm
here
is
marching
here.
D
So
with
the
volatility
from
graph
is
saying,
in
VC
or
within
either
or
a
by
level
of
a
level
level
and
using
the
proper,
a
persona
presence
option
and
to
just
render
them
the
component.
So
that's
pretty
much
everything
actually
there's
not
much
golden
on
the
wood
part,
so
just
get
in
the
members
and
calling
the
API
with
the
list
of
user
IDs,
as
I
saw
you
in
enforcement.
So
any
question
just
feel
free
to
drop
the
message
on
the
on
the
chat
and
that's
actually.
A
E
E
Okay,
I,
just
it's
always
good
people
to
be
able
to
see
my
facial
expressions
when
I
say
certain
things
cuz.
So,
yes,
my
name
is
Darrell
Miller.
Let
me
share
my
screen
and
a
little
bit
about
the
role
that
I
play.
If
you
want
to
reach
out
to
me,
I
spend
a
sad
amount
of
time
on
Twitter,
so
it's
always
an
easy
place
for
you
to
be
able
to
find
me.
So
it's
Darryl
underscore
Miller
on
Twitter
I
do
work
on
the
graph
developer
experience
team
I
own.
E
The
the
SDKs
is
one
of
the
things
that
I
do
across
all
the
different
languages
and
also
I
actually
sit
on
API
review,
so
that
get
presence.
Api
review
was
one
that
I
sit
on.
So
if
there
are
things
consistently
across
the
the
graph
API
that
you
think
we
should
fix
things
that
you
think
we
could
do
better.
Let
me
know
because
I
can
get
involved
in
a
lot
of
those
kind
of
API
reviews.
E
If
you've
been
following
along
closely
with
the
PNP
Jas,
you
may
have
seen
the
the
the
PR
that
came
about
and
was
a
little
bit
of
a
hoo-ha
about
removing
graph
components:
I'm
the
bad
guy,
with
kudos
to
Billy
Elish
there,
who
communicated
that
whole
thing
fairly
poorly
glad.
We
got
that
fixed
and
it's
actually
a
good
thing,
because
it's
what
triggered
this
whole
presentation
here
and
I
hope
moving
forward.
We
can
have
a
lot
more
closer
conversations
between
p.m.
PG
@
p.m.
PJs
group
and
our
graph
SDK
team.
E
E
Now,
when
I
say
consistent,
I'm,
not
trying
to
say
well
everybody's
gonna
code
in
c-sharp,
but
just
in
a
different
language,
the
idea
is
that
we
do
things
that
are
native
to
the
language,
but
have
a
bunch
of
common
components
so
that,
when
we're
sharing
ideas
and
talking
about
capabilities,
we
can
talk
about
things
using
common
language.
So
this
is
kind
of
our
architectural
diagram
for
all
of
the
SDKs
that
we
build
and
the
piece
that
I
really
want
to
talk
about
today
is
the
area.
That's
called
the
request.
E
Builders
in
here,
the
green
layers
are
ones
that
we
actually
code
generate
and
the
blue
layers
are
ones
that
are
curated
artisanal
code
and
I.
Think
this
is
really
where
the
main
difference
between
the
approach
with
the
graph
SDK
team
and
the
PM
pjs
team
go.
We
code
generate
a
whole
bunch
of
stuff,
and
we
do
that.
E
Based
on
the
metadata
that
comes
out
of
the
graph,
it
comes
out
as
C
STL,
which
is
this
ugly
ugly
XML
document
that
is
exposed
under
the
dollar
metadata
endpoint
of
graph,
and
then
we
take
that
C
STL
and
we
feed
it
through
a
bunch
of
Machinery
and
we
generate
a
set
of
well.
First
of
all,
we
said
generate
a
set
of
models
and
in
the
typescript
world
or
in
the
JavaScript
world
we
generate,
if
you
just
flip
over
here
for
a
moment,
the
typescript
typing's
module.
E
So
all
the
models,
if
you
want
typescript
types
for
all
of
the
models
of
graph,
you
can
pull
this
in
either
by
an
NPM
package
or
if
I
definitely
typed,
and
so
we
generate
all
the
malls
and
we're
currently
doing
that
for
JavaScript.
What
we
currently
don't
do
for
JavaScript
is
generate
request,
builders
and
there's
few
reasons
why
we
don't
do
it.
One
is
just
we
just
haven't,
had
resources
to
do
it.
E
There
was
some
initial
feedback
that
we
don't
need
to
do
it
and
over
time
we've
had
more
and
more
feedback
that,
yes,
we
really
really
should
do
it
now.
The
thing
is,
this
is
something
that
PM
pjs
has
built
into
that
with
the
graph
library
within
PM
PGS,
but
it's
not
auto-generated
and
the
challenge
with
graph,
of
course
is
it
keeps
growing
and
getting
bigger
and
bigger
and
bigger
all
the
time.
E
E
The
entire
surface
area
with
a
fluent
API
would
be
a
significant
amount
of
effort
and
I
wish
that
on
nobody,
especially
not
community
folk
who
were
actually
doing
this
in
their
spare
time,
so
we
want
to
build
fluent
API.
There
already
is
one
in
PMT
in
PN
PJs.
How
do
we
make
sure
that
we
do
something
that
benefits
everybody
in
the
most
effective
way?
E
So,
let's
take
if
we
go
into
the
PNP,
Doc's
and
I'm
just
jealous
that
you
have
so
many
ducks.
I
have
a
whole
bunch
of
ducks
that
I
still
need
to
push
for
our
SDKs,
but
let's
not
get
sidetracked.
So
in
order
to
retrieve
the
set
of
contacts
related
to
a
particular
user,
we
have
a
graph
kind
of
root
object
and
then
using
darting
we
can
go
and
access
other
collections
that
exist.
E
If
you
want
to
get
to
a
particular
user
use
get
by
ID
and
then
you
go
off
and
retrieve
the
contacts
which
in
CSD
L
language
is
referred
to.
As
a
navigation
property
off
of
the
user,
now,
if
we
go
and
look
at
our
Docs
and
the
one
thing
that
we
do
have
that
I
do
really
really
like
is
if
you
go
and
look
in
our
reference
documentation
and
you
go
through
the
examples
that
are
here.
E
E
Okay,
we
have
a
route
object
and
in
this
case
it's
hitting
dot
me,
but
you
can
hit
dot
users
just
the
same,
and
then
we
go
to
contacts
and
the
only
difference
here
really
is
we
insert
this
call
to
dot
request
here
and
it's
an
explicit
action
that
says:
okay,
I
finished,
finding
the
entity
that
I'm
looking
for
and
now
I
want
to
make
a
call,
and
we
end
up.
There
are
places
where
you
can
do
additional
stuff,
which
we'll
show
in
a
minute
here.
E
So,
as
you
can
see,
we're
not
too
far
off
on
that
first
example
like
we're
doing
fairly
a
similar
kind
of
thing.
Oh,
that
was
in
c-sharp,
though
the
way
it
currently
works
in
JavaScript.
Is
you
hear
up
the
client
and
then
we
have
this
API
method
and
you're
expected
to
construct
the
URL
yourself,
which
and
sometimes
it's
good.
Sometimes
it's
a
real
pain
in
the
butt.
So
if
we
added
the
fluent
interface
absolutely
we
would
keep
the
same
mechanism
of
doing
it.
E
In
fact,
we've
had
requests
that
we
add
this
kind
of
make
a
custom
request
just
using
a
path
back
into
the
c-sharp
language.
So
that's
probably
something
we're
going
to
add
into
the
c-sharp
language
and
actually,
if
you
flip
over
to
java
you'll
see
we,
it
basically
looks
the
same
as
a
few
extra
parentheses
in
Java,
juggs,
client
up
meetup
contacts
and
now
we
say
build
requests,
just
a
style
difference.
E
E
E
So
here
in
c-sharp
we
knew
up
an
object.
We
take
the
root
object.
We
go
to
the
invitations
collection,
we
stick
on
this
extra
request
and
we
do
add
async
and
pass
the
object
in
really
really
very
similar.
Java
scripts
is
slightly
different
in
just
that.
We
create
the
the
object
and
then
we
do
post.
So
we're
sticking
in
most
cases
with
the
HTTP
method.
There's
some
exceptions
to
that,
but
that's
again
pretty
much
a
style
issue.
E
Looking
at
going
and
getting
an
individual
item
now
the
example
I
picked
from
the
PMP
Jess
example.
Here
is
simply
going
and
retrieving
a
team,
so
we
say
teams
get
by
ID
and
go
and
retrieve
an
individual
team
entity.
If
we
look
interestingly,
the
team's
Doc's
have
that
magic
attribute
that
stopped
us
from
actually
creating
the
doc.
So
I'm
gonna
go
look
at
going
and
getting
a
group.
It's
basically
the
same
thing,
and
here
it's
a
case
of
we
say
we
take
the
root
object
instead
of
saying
doc
get
my
ID
we're
taking
advantages.
E
E
We
say
execute
on
it
now:
I'd
love
to
point
you
to
the
documentation
and
where
we
show
you
how
to
do
this
in
the
graph
SDK,
but
it's
not
pushed
up
yet
so
I'm
gonna
have
to
pull
you
over
to
my
vs
code
here,
and
here
is
the
example
that
does
approximately
the
same
thing
in
in
dotnet.
You
take
the
root
object.
E
You
make
requests
here,
I'm
going
off
and
getting
a
user
and
you
say
me
dot
request,
and
the
idea
is
that
that
dot
request
just
constructs
a
request,
object
that
you
can
then
hold
on
to.
So
here
we
go
and
get
the
list
of
events.
We
create
a
request,
object
you
hold
on
to
it.
Now
we
create
a
request,
content
object
which
is
equivalent
to
the
peon
PJs
batch,
and
we
add
it
in
and
you
compare
ID
parameters
to
this
add
batch
request
step
in
order
to
specify
the
order.
E
In
the
same
way
it
was
done
in
the
PM
PJs
and
then
they
execute
instead
of
actually
executing
on
the
content
itself.
We
simply
just
take
the
batch
endpoint
and
we
do
post
with
that
batch
can't.
So
really
not
a
long
way
apart.
Let's
go
back
to
here.
Go
back
to
here,
and
the
last
set
of
examples
I
want
to
show
is
I
did
struggle
a
little
bit
to
find
some
good
examples
that
showed
using
the
OData
querying
capabilities
on
top
of
the
fluent
API.
But
I
did
find
this
example,
which
was
pretty
good.
E
So
here
we
go
SP
web
and
then
we
go
and
say
dot
file.
We
do
get
folder
by
store
over
a
relative
URL
and
we
do
dot
files,
and
then
we
use
the
projection
capability
select
and
the
dot
top
capability
all
right.
So
this
just
applies
on
top
of
these
objects,
because
I
believe
it
works
because
they
derive
from
the
OData
queryable
bank's
class.
E
Flying
back
to
the
way
this
works
in
dot
there
we
go
over
here
we
go
look
at
this
particular
example.
Where
we're
going
and
getting
a
set
of
users,
we
go
and
we
build
the
request,
object
and
then
the
request
object
comes
back
and
it
has
the
abilities
for
doing
these.
Things
like
select
if
you
actually
go
into
the
SDK.
There's
a
bunch
of
other
examples
in
here
of
how
you
do.
E
How
you
use
the
Select,
how
you
do
filtering
and
order
by
and
the
very
expanding
and
using
top
and
all
of
these
kind
of
things,
largely
it's
the
same
concept?
Okay,
so
hopefully
what
I've
demonstrated
here
is
what
the
PN
pjs
graph
library
has
built
is
really
not
that
far
away
from
what
our
fluent
library
in
c-sharp
is
already
building
and
something
that
we
could
build
in
the
JavaScript
typescript
world.
Also,
at
this
point
at
what
my
ideal
outcome
would
be
is,
is
we
aligned
on
the
fluent
style
and
and
I
think
you're?
E
The
PNP
J's
team
has
experience
with
people
using
the
particular
style
that
you're
using
and
I
think
if
I,
when
I
didn't,
create
a
link
to
it,
but
somewhere
in
this
Docs,
there
is
a
description
of
the
the
OData
queryable
I'm,
not
gonna,
be
able
to
find
it
in
the
moment,
but
anyway,
there's
a
set
of
parameters.
With
regards
to
setting
query
headers
with
regards
to
setting
just
HTTP
headers,
we
could
follow
that
set
of
conventions
in
use
our
generation
mechanism
to
generate
a
set
of
what
we
call
request.
Builders,
and,
ideally,
we
could
layer.
E
Those
request
builders
on
top
of
our
existing
JavaScript
core
or
hopefully
on
top
of
the
PNP
Jay
escort,
so
it
would
be
an
opt-in
module.
The
PM
pjs
could
pull
in
and
layer
a
fluent
api
on
top
of
that
core,
and
so
we
would
create
the
base
stuff
for
either
the
v1
or
the
beta
and
then
from
a
community
perspective,
it's
like
if
there
are
other,
more
richer
expressions
or
things
that
we
just
can't
do
from
a
code
gen
perspective
for
some
reason
that
those
could
be
the
only
things
that
would
have
to
be
manually.
E
Handcrafted
and
coding.
I
have
gone
through
the
thought
exercise
of
well.
We
could
maybe
just
adopt
the
PNP
j/s
core,
because
it's
serving
largely
the
same
process.
The
challenge
we
had
is
one
of
the
major
efforts
that's
going
on
at
the
moment
within
the
whole
graph.
Sdk
work
is
aligning
with
the
Azure
SDKs
and
I,
don't
know
where
that's
going
to
take
us
and
whether
that's
going
to
end
up
generating
some
difficulties
with
now.
We've
got
to
align
three
different
orgs
with
with
it
within
the
company.
E
So
that's
my
proposal
so
far
and
I
would
like
to
explore
further
this
idea
of
being
able
to
generate
that
sort
of
fluent
API
is
that
would
work
for
both
our
JavaScript
core
that
is
currently
used
by
SPF
X
and
the
p.m.
PJs
core,
using
the
fluent
style
that
you've
already
created
as
our
starting
point
for
work
and
with
that
I
didn't
leave
a
whole
lot
of
time,
but
feedback
would
be
thoroughly
appreciated.
A
E
There's
a
side
conversation
I'm,
not
really
what
the
official
answer
is,
nobody
knows
and
it
might
not
make
a
difference.
We
believe
that-
and
we
are
working
with
the
teams
at
the
moment
in
order
to
fight
to
provide
a
way
that
teams
can
make
breaking
changes
to
the
graph
that
actually
aren't
breaking
changes.
It
follows
a.
E
Methodology
that
allows
new
things
to
be
introduced
and
then
things
to
be
deprecated
over
time.
It's
kind
of
a
little
similar
to
the
graph
QL
versioning
model,
and
we
think
that
that
might
allow
us
teams
to
be
able
to
go
and
fix
things
without
having
to
do
a
Big,
Bang
v2,
because
at
the
moment,
in
order
to
coordinate
the
50
different
service
teams
to
align
on
a
release
date
for
when
they
can
shift
all
of
their
stuff
to
v2
has
proved
very
challenging.
To
get
to
stay
tuned.
A
E
We
are
a
github
repo.
We
accept
I
hate
to
say
that
we
accept
all
requests.
Just
should
I
should
use
the
phrase
sharing
is
caring
right.
We,
we
have
accepted
contra
community
contributions.
We
are
going
through
change.
Some
changes
within
our
team
at
the
moment,
so
we
are
a
little
behind
in
providing
the
necessary
feedback
to
community
involvement.
E
At
the
moment,
we
have
not
explicitly
done
a
lot
of
outreach
with
regards
to
community
involvement
because
we
have
sort
of
spent
the
last
12
months
or
so
really
getting
this
kind
of
common
architecture
together
and
to
get
our
requirements
that
we
feel
are
necessary
out
there
in
the
public
and
we
are
getting
into
a
place
where
we
built
up
all
of
our
infrastructure
for
releasing
and
management
and
triaging
issues
to
a
state
where
we
are
in
a
better
position
to
start
accepting
community
contributions.
We
do,
we
just
haven't
been
so
good
at
it.
B
Worth
mentioning,
maybe
is
the
Microsoft
graph
SDK
dotnet
contribution
repository.
This
is
a
place
where
people
doing
government
development
can
contribute
and
add
stuff
to
the
community
like
testing
unit
testing
tooling,
like
handlers
for
each
for
errors
and
so
on
and
so
forth,
and
with
the
Segway
I'll.
Let
you
talk
more
about
that.
E
Yes,
the
the
good
thing
Paul
started
this
and
the
advantage
of
this
is
you
can
go
and
add
new
features
without
kind
of.
If
we
decide
that.
Yes,
that's
something
that
would
be
really
great
in
core
that
you
can
keep
using
your
feet.
Your
kit,
your
capability,
if
we
happen
to
slightly
redesign
it
when
it
gets
integrated
into
core.
A
A
Fantastic
excited
to
see
that
I
think
that's
February
13th
off
the
top
of
my
head
and
so
excited
to
have
you
back
Thank,
You
Lewis,
for
your
demos.
Let
me
actually
get
back
to
the
slides,
so
we
can
close
out
and
then,
of
course,
Darryl
on
Twitter.
You
can
always
catch
up
with
him.
If
you
have
further
questions
or
feedback,
he
definitely
is
looking
to
hear
from
folks
who
are
using
SPF,
X
and
client-side
development
on
shaping
what
these
JavaScript
libraries
might
become.
So
definitely
a
great
opportunity
to
get
involved
there.
A
Next
SharePoint
framework,
JavaScript
meeting,
February,
13th,
I'm,
sorry,
I,
didn't
say
thank
you
to
Bob
as
well
for
demoing,
so
Lois,
Bob
and
Darryl.
Thank
you
to
all
three
of
you
for
the
great
demos
today
and
great
discussion
next
to
SharePoint
framework
JavaScript
meeting
February
13th
2020,
so
we'll
see
all
of
you
hopefully
back
then,
and
our
next
general
SharePoint
dev
cig
will
be
next
Thursday
February
6th.
So
talk
to
you
all
soon
have
a
great
weekend.