►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 14th of March. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
Demos:
Vesa Juvonen - Preview on library component usage with SharePoint Framework 1.8
Laura Kokkarinen – SharePoint Framework built Microsoft Teams tab using Microsoft Graph to manage team membership
Nanddeep Nachan – Accessing Google APIs from SharePoint Framework solutions
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
special
urges
grouped
by
weekly
sync.
It
is
March
14th
2019.
Welcome
to
the
call
this
week
excited
to
have
everybody
on
the
call,
hopefully
the
daylight
savings
time.
Confusion
hasn't
messed
too
much
with
folks
schedules.
I
want
to
get
right
in
this
week
to
the
agenda
will
start
off.
As
always,
with
an
engineering
update
on
SharePoint
framework.
A
We've
got
patterns
and
practices
program
updates
for
the
different
offerings,
so
the
PJs
library,
the
office
365
CLI,
the
SPF
X,
reasonable
controls
and
the
PNP
yeoman
generator
and
they've
got
some
great
demos
coming
the
first
from
Laura
Koch
our
ribbon
cooker
written
sorry.
It
took
me
a
second
there
and
then
none
of
the
Nashawn
is
gonna.
Do
his
demo
there
on
steps
to
access,
Google,
API
from
SharePoint
framework
and
then
Laura
is
doing
managing
themes
from
an
SPF,
X
webparts.
So
two
great
demos
there
David
things
for
her
demo
title
is
wrong.
Uh-Oh!
B
A
But
let's
go
ahead
and
get
started.
First,
I
want
to
say
happy
pi
day
to
everybody.
It
is
3:14,
so
that's
pi
day,
so
I
hope
everybody
gets
to
go
out
and
enjoy
some
wonderful
pie
today
out
there
in
the
world,
but
first
a
statement
on
Microsoft
teams.
We
are
aware
the
team's
exists
and
we
would
love
to
use
it.
A
Unfortunately,
there
are
some
limitations
in
its
current
functionality,
specifically
around
having
presenters
versus
audience
members
and
who
can
share
their
screen
and
who
can
take
control
and
things
like
that,
and
we
do
very
much
want
to
switch
and
we'll
do
so
just
as
soon
as
the
product
supports
the
capabilities
we
need
to
make.
These
calls
run
smooth.
So
just
we
are
working
on
that.
So
we
are
keeping
an
eye
on
that.
It's
not
us
necessarily
being
stubborn
or
not
wanting
to
move.
A
It's
just
simply
a
need
to
be
able
to
better
control
the
call
and
how
the
call
flows.
Then
teams
really
lets
us
do
at
this
point
in
time,
but
so
we
will
switch
just
as
soon
as
we
Han
do,
of
course,
like
the
highlight
opportunities
to
participate
in
SP,
FX
and
JavaScript
special
interest
group
always
encourage
you
to
do
demos,
so
we
always
have
great
demos
of
all.
These
calls
encourage
you
to
meet
your.
A
Basic
con,
so
you
can
do
demos
across
anything
SharePoint
framework
related,
so
web
parts
application,
customizers
provisioning
any
of
the
stuff
you
might
create
with
SharePoint
frameworks.
Similarly,
any
of
the
at
PNP
stuff,
so
the
PJs,
the
CLI,
the
reasonable
trolls
or
the
yeoman
generator
are
all
make
great
demos
and
of
course,
any
combination
of
those
things.
So
using
those
things
with
an
in
SharePoint
framework
is
always
really
cool
to
see.
A
So,
if
you're
working
on
something
awesome
and
I
know,
many
of
you
are
out
there,
I
would
encourage
you
to
reach
out
to
myself
or
visa
on
getting
on.
One
of
these
calls
to
do
a
demo
very
much,
encourage
you
to
do
that.
Reach
out.
I
would
love
to
get
you
on
a
call.
It
might
not
be
the
immediately
next
call
just
due
to
scheduling,
but
we'll
get
you
on
just
as
soon
as
we
can
so.
Please,
just
let
us
know
I
would
love
to
have
you
on
the
call
as
well.
A
A
I'll,
let
you
know,
but
never
get
back
from
you
I,
certainly
apologize.
If
we've
missed
a
message,
please
do
reach
back
out,
try
and
hit
us
on
Twitter
or
somewhere
and
very
sorry.
If
we
haven't
gotten
back
to
somebody,
that's
absolutely
an
oversight
and
not
purposeful,
so
apologies
there
if
you
feel,
like
we've,
missed
getting
back
to
you,
so
very,
very
sorry
for
that
and
then
as
well
always
appreciate
feedback.
So
how
are
the
calls
going?
How
are
the?
How
is
our
documentation?
A
B
B
Few
reminders:
AKMs
SPF
Docs
documentation
for
SharePoint
SharePoint
framework.
One
point
eight
is
coming
out
relatively
soon.
The
docs
will
be
updated
when
we
release
the
1.8
as
an
example.
The
videos
I
came
SSP
their
videos
and
then
the
issue
list
is
very
important
for
you
to
report
any
issues
towards
us
as
well.
If
there's
any
differences
asian
issues,
if
it's
an
out-of-the-box
issue,
that's
not
the
location
to
actually
report
those
now
a
few
reminders-
and
this
one
is
a
repeat
from
last
time.
B
So
please
remember
that
there
is
an
existing
SharePoint
framework
developer
training
package
which
exists
already
from
six
modules.
It
will
be
further
extended
with
three
additional
modules
relatively
fast,
and
this
is
for
you
to
take
advantage
anyway,
one
so
you're
able
to
reuse
the
material
you're
able
to
redeliver
the
material
you're
able
to
do
you
use
it
for
self
learning.
There's
videos,
presentations,
hands-on,
Maps
demos
available
within
this
material.
So
please
take
advantage
of
this
options
and,
if
there's
anything
which
we
need
to
adjust
on
these
things,
please
that's
no!
B
So
basically
you
can
go
to
that
service.
You
can
sign
in
against
your
tenant
and
you're
able
to
provision
good,
looking
site
example,
content,
which
you
can
then
reuse
within
any
tenant
in
the
world.
Now
this
is
in
public
preview,
so
there
are
small
hiccups
here
in
there
which
we
are
still
addressing
and
we
keep
on
evolving
this
as
we
move
along
on
this
journey.
Few
things,
if
you
have
tested
this
and
you're
running
into
issues
or
you've,
been
getting
exceptions.
First
of
all,
please
report
them
just
the
second,
the
typical
exceptions.
B
What
we're
seeing
all
the
time
with
people
is
people
are
missing
is
that
they
don't
read
the
pre
requirements.
Some
of
the
templates
do
contain
SharePoint
framework,
extensibility
or
extensions
and
read
parts,
and
the
app
catalog
has
been
exists
on
your
site
and
please
to
remove
em,
remember
to
meet
yourself
when
churning
on
the
call
now,
so
you
need
to
have
an
app
catalog
in
the
site
for
some
of
the
templates,
not
for
all
of
the
templates.
B
So
if
you're
running
into
an
exception,
try
another
template
which
doesn't,
for
example,
have
customizations
all
of
the
templates
actually
have
detailed
lists
to
what
they
contain
and
you're
able
to
actually
have
a
look
on
what's
available
in
them
now,
and
what
else
that?
Oh,
if
you
are
using
this
for
deployment
of
the
SharePoint
starter
kit,
which
is
an
open
source
reference
solution,
the
starter
kit
itself
can
be
installed
to
any
tenant
as
well
using
this
solution.
But
it
requires
that
you
are
a
term
store
administrator.
B
That
is
a
pre
requirement
for
that
template
to
actually
succeed.
So
please
have
a
look
on
the
documentation,
have
a
look
on
the
notes
and
guidance
around
the
service
as
well,
but
please
give
us
also
feedback.
We
will
add
additional
solutions
and
samples
in
this
service
as
well,
so
you
can
easily
provision
call
content
on
the
existing
tenants,
cute
dun-dun-dun
now.
B
So
a
quick
answer
from
your
noses
question.
Please
report
the
errors.
If
you're
getting
errors,
please
do
report,
those
don't
know
where
we
can
fix
theirs
is
by
us
knowing
that
something
goes
wrong,
so
we're
able
to
then
get
the
people
on
top
of
it.
Now,
from
the
SharePoint
framework
perspective,
the
growth
continues.
We
we
saw
a
massive
jump
on
January
and
then
slightly
slowing
down
the
growth,
but
now
we're
again
seeing
a
next
jump,
which
means
that
additional
set
of
customers
are
again
taking
more
importance
and
modern
SharePoint
framework
customizations
into
yours.
B
The
growth
is
just
unheard
of.
You
can
see
the
yellow
marker
on
between
the
post
lights,
which
are
actually
showing
the
growth
curve
in
in
a
direct
line,
which
is
it's
pretty
insane?
How
fast
to
use
it
system
is
currently
growing.
Now
a
few
things
related
on
SharePoint
framework,
so
SharePoint
framework
1.8
is
gonna,
go
out
really
soon.
It's
gonna
be
released
in
March.
2019
right
now
is
14th
of
March,
so
you
can
kind
of
a
guess
we
could
do
bidding
on
which
day
we're
actually
releasing
that
and
just
a
rid
of
an
example.
B
We
do
not
release
anything
on
Friday
because
you
should
never
ship
anything
on
Friday,
so
just
letting
everybody
know
that
so
1.8
is
coming
out
relatively
soon.
The
number
one
big
thing
there
is
the
general
availability
of
creating
marks
or
themes
taps
using
SharePoint
framework
that
goes
to
GA
right
now,
we'll
also
g8.
The
single
part
update,
is
and
isolated
web
parts,
so
absolute
web
part
is
there
for
creating
the
limiting
the
permission
and
access
tokens
access
between
the
web
parts,
so
we're
automatically
creating
applications
to
your
sure
ad.
B
If
you're
using
this
option
and
the
single
part
update
is,
is
the
full
page
rendering
of
a
web
part
really
cool
capability
as
well.
We're
also
kind
of
support,
typescript
3
point
X.
We
do
get
a
lot
of
questions
related
on.
Why
don't
you
support
the
latest
possible
thing?
Why
don't
you
upgrade
on
the
things?
Why
don't
you
upgrade
the
on-premises
and
and
I'm
gonna
spend
two
seconds
quickly
on
explaining
this,
so,
first
of
all
for
SharePoint
Online,
we
build
off
our
own
customizations
using
SharePoint
framework
as
well.
B
So
whenever
we
create
the
first
part
experience
is
we
will
get
you
into
the
rain
same
version.
We
can
not,
however,
give
you
a
newer
version
of
the
type
script
or
react,
and
then
what
we
are
using
in
the
first
part,
because
that's
not
how
it
works,
plus
the
fact
that
we
have
quite
a
few
first
party
wet
parts
and
you
eyes
and
experiences
which
we
need
to
test.
So
this
actually
makes
the
the
upgrading
of
delayed
to
the
latest
versions
slightly
more
complicated.
B
Then
externally,
people
might
actually
think
because
we
need
to
operate
things
at
the
same
time.
No,
no
there
was
originally.
There
was
also
a
feedback.
You
know
some
of
the
kids
have
issues
related
on.
Why
don't
you
have
greater
the
on-premises
version
of
the
supported,
SP
FX
version
in
on-prem
and
then
so?
For
that,
one
is
that
we
actually
can't,
because
not
because
we
wouldn't
want
to,
we
will
have
the
used
latest
and
greatest
and
the
version
which
was
released
yesterday,
but
that's
just
not
reality.
B
The
only
way
we
can
update
the
version
is
that
we
update
the
server-side
dependence
as
well
off
the
type
script
or
react,
and
then
what
we
are
using
in
the
first
part,
because
that's
just
not
how
it
works,
plus
the
fact
that
we
have
quite
a
few
first
party
wet
parts
and
you
eyes
and
experiences
which
we
need
to
test.
So
this
actually
makes
the
the
upgrading
of
delayed
to
the
latest
versions
slightly
more
complicated.
Then
externally,
people
might
actually
think
because
we
need
to
upgrade
things
at
the
same
time.
No,
no
there
was
originally.
B
There
was
also
a
feedback.
You
know
some
of
the
kids
have
issues
related
on.
Why
don't
you
upgrade
on-premises
version
of
the
supported,
SP
FX
version
in
on-prem
and
then
so?
For
that,
one
is
that
we
actually
can't,
because
not
because
we
wouldn't
want
to,
we
will
have
to
use
the
latest
and
greatest
and
and
the
version
which
was
released
yesterday,
but
that's
just
not
reality.
The
only
way
we
can
update
the
version
is
that
we
update
the
server-side
dependence
as
well.
B
John,
can
you
make
yourself
please
thank
you,
so
so
the
only
way
we
can
update
the
the
version
is
to
update
also
the
server
side
and
in
SharePoint
Online.
We
control
the
server
side
and
that's
why
we
can
actually
update
you.
I
went
online
relatively
fast
for
one
Prem.
We
do
not
have
any
permissions
to
up
create
your
servers,
and
that
means
that
the
only
way
we
can
actually
upgrade
the
dependencies
are
as
part
of
the
service
packs
or
a
major
versions.
B
So,
even
though
we
would
love
to
give
you
a
SharePoint
framer
of
1.8
in
SharePoint
2016,
it's
just
not
easily
doable
the
logistics
and
everything
else
are
insanely.
Difficult
and
I'll
probably
explain
this
in
a
future
blog
post
at
some
point,
because
it's
good
that
people
understand
that
we
would
love
to
do
that.
But
it's
just
the
implications
are
hard
now
coming
back
on
the
list
of
things.
B
So
the
support
for
types,
two
point:
seven
and
three
point
X
you
can
actually
choose
which
one
you
use,
which
is
a
cool
thing,
provided,
hosted
solutions
in
SharePoint,
so
teams
applications
in
inside
of
the
SharePoint.
Basically,
the
classic
teams
tabs.
So
if
you
implement
an
assasin
tab
implementation,
those
who
are
working
with
SharePoint,
but
it's
still
in
preview,
there
are
certain
things
which
we
found
out
relatively
late,
so
we
need
to
fix
those
most
likely
to
occur
GA
before
1.9
and
we'll
communicate.
All
of
this.
B
When
that
happens,
the
library
components
for
SharePoint
framework
solutions
is
gonna,
go
to
preview
as
part
of
1.8,
which
sassoon,
which
can
add
in
assume
that
it's
going
to
go
GA
in
1.9,
which
will
probably
happen
roughly
on
built
SPSA
timeframe,
which
is
relatively
good
way
of
putting
that.
So,
typically,
we
release
stuff
during
the
big
conferences,
so
you'll
see
the
1.9
coming
at
that
point.
1.8
coming
relatively
fast
good
store
an
app
store
story
for
SharePoint
framework
still
in
progress,
but
we
are
actively
working
on
that
one.
B
B
The
park
at
porcupine
Park
a
porcupine
situation
as
we'll
get
more
details
from
Parker
as
fast
as
possible
as
well.
Whenever
the
time
is
right
now,
so
somebody
needs
to
tell
me
thanks.
You
go.
Somebody
needs
to
tell
me
when
the
screen
sharing
is
actually
working.
It's
not
just
confirming
that
you
can
say
that
you'd
shown
correct
David
got
it
excellent,
excellent,
so
we're
good
to
go
so
I'm
running
a
1.8
release,
candidate
second
version.
So
to
say
this
is
PR
one.
B
It's
not
just
our
internal
code
names,
and
so
it's
it's
basically
a
release
candidate
to
because
we
are
zero
is
the
first
one
and
then
we
always
find
something,
and
then
we
follow
up
on
things.
But
what
I've
done
here?
This
is.
Actually
this
is
the
web
part
solution.
So
let
me
change
the
library
solution
or
actually,
let
me
show
this
one
in
here.
So
if
I
create
ad
quickly
a
library
compound,
folder
and
I
can
go
to
the
library,
folder
and
I
can
do
y
ou,
Microsoft
SharePoint
and
they
find
the
plus
beta.
B
B
B
In
this
case,
this
is
just
a
library
test
library
it
has
a
name
probably,
which
will
then
return.
This
information
is
coming
from
a
custom
library
at
a
certain
time.
So
really
simple,
things
has
to
verify
that
things
are
actually
working
now
after
I
implement
it
a
library
or
when
I
have
the
baseline
done.
B
So,
let's
see
what
we
actually
have
be
sorry
library,
nope
test,
no
better.
So
let
me
do
it
called
bundle.
Just
a
shipped
and
I'll
do
a
quickly
package
solution
as
well,
and
we'll
get
this
one
deployed
basically
to
the
catalog.
This
the
demo
doesn't
make
take
too
long.
What
I
wanted
to
actually
go
through
the
steps
what's
actually
happening
here,
so
the
library
solution
everything
is
available.
B
Let
me
do
also
the
the
packet
solution
and,
yes,
you
know
later
we
will
actually
have
a
one
command
which
will
do
both
of
these,
but
it's
it's
slightly
awkward
that
you
always
need
to
do
this
both
now,
that's
actually
now
getting
executed.
So
that's
going
to
be
updated
in
a
second
and
let's
get
that
one
deployed
there,
we
go
1619.
So
now,
if
I
go
to
my
tenant
app
to
catalog,
let's
go
to
the
solution.
There's
my
library
test.
B
It's
maybe
80
false,
that's
just
getting
that
one
on
the
app
catalog
available
for
the
webparts
to
actually
reference
and
take
advantage
now.
Okay,
we
want
that
to
be
available
across
all
of
the
sites,
because
the
webparts
might
be
anywhere
in
a
ten
and
so
again
slightly
debatable.
Technically,
you
can
do
as
Sai
collection,
app
catalog
library
as
well.
Now
what
about
the
wet
part
so
we're
consuming
that
slavery
in
wet
bar
sites?
And
this
wasn't
this
one
was
the
library
part.
B
B
Thank
you
now
so,
what's
going
to
happen
next
is
that
we
link
we
need
to
do
NPM
link,
and
all
of
this
is
going
to
be
documented
in
this
solution
in
the
solution
folder
and
after
that
we
are
just
able
to
reference
the
library
in
our
code.
So
basically
what
we
need
to
do.
We
don't
need
to
update
any
conflicts.
B
We
don't
need
to
update
anything
more
than
say
import
as
my
awesome
library
and
the
NPM
linking
the
name
which
we
use
for
impairment
linking
and,
in
this
case,
I'm
just
creating
an
instance
of
that
library.
Again,
how
do
you
implement
a
life
or
what
does
the
library
do
it?
That's
up
to
you.
That's
just
a
a
simple
usage
scenario:
it's
my
instance
and
I'm
actually
adding
that
name
property
inside
of
this
rendering
of
the
of
the
HTML.
B
Now,
what's
really
cool
about
this
one,
the
only
thing
what
we
need
to
do
in
this
web
part
is
the
NPM
linking
for
development
time,
and
then
we
need
to
make
sure
that
we
have
a
dependency
included
in
here.
So
let
me
actually
do
that
for
the
library
itself.
So
in
this
case
our
library
is
library
test
beta,
no
beta,
zero,
zero
one
and
how
did
I
know
that's
if
I
go
here.
The
de
package.json
I
can
actually
say
that
my
library
name
is
death.
B
Better
know,
better
swear,
zero
one,
so,
basically
in
our
dependencies
of
the
web,
part
I'm
saying
hey.
So
we
have
a
dependence
on
this
basic
setup
and
my
custom
setup,
which
is
this
one
in
here
cool
and
then
we're
basically
good
to
go.
So
let
me
get
in
the
common
to
comander
get
in
here
web
part.
Library
test,
do
call
bundle
and
does
that
ship.
B
Da-Da-Da-Dah
Russell:
how
does
it
know
where
to
load
the
library
from
where
it's
deployed
it's
magic?
So
basically
it?
What
happens
in
runtime
is
that
the
web
part
is
saying:
hey,
so
I
have
a
dependency
on
this
library
ship
one.
Can
you
help
me
and
SharePoint
says?
Oh
yeah
I
got
that
this
is
for
you
and
voila.
B
B
Dynamically
runtime
in
your
webparts
cross
the
whole
tenant
in
an
efficient
way
and
you're
able
to
version
that
centralized
library
completely
is
independently,
so
you're
able
to
introduce
stuff
to
change
this
stuff,
and
that
will
completely
do
modifications
on
all
sides
what
if
I,
were
doing
a
library,
packets
versus
a
custom
NPM
packets?
Well,
basically,
it's
just
matter
of
a
reference
to
be
fair.
If
you
do
a
custom
NPM
package,
then
you
need
to
host
that
in
somewhere.
You
need
to
reference
that
dynamically.
B
You
need
to
host
that
in
somewhere
else,
then
actually
to
have
catalog
technically,
and
you
can
actually
make
that
happen
as
well.
But
the
way
we
get
the
library
now
exposed
is
super
super
easy.
So
let
me
actually
get
in
here
and
let
me
get
to
the
vape
a
library
test.
Let
me
get
the
SharePoint
and
solutions
folder
and
there
we
go
library
test.
This
is
available
over
there.
So
let
me
get
my
app
catalog
available
here.
We
go
voila
getting
everything
installed
there
we
go
and
it's
a
normal
webparts
solution.
B
I
will
click
check,
check
box
and
that
month,
and
we
are
deployment-
should
be
completed.
So
now,
if
I
go
to
communication
sites
refresh,
let's
create
a
new
page
at
a
page,
and
let's
call
this
demo
in
here.
We
should
have
something
related
on
library
and
let
me
be
library
test,
and
there
is
our
report,
which
is
actually
dynamically
getting
referenced,
referencing
that
library
implementation
inside
of
the
code.
B
The
only
thing
like
that
was
the
the
runtime
dependency
and
now,
if
I,
do
any
changes
on
the
library,
I'll
just
drag
and
drop,
this
be
PKG
file
to
the
app
catalog
and
poof
updates
are
immediately
available.
I
don't
need
to
recompile.
I
don't
need
to
do
any
changes
on
a
webpart
side
to
be
able
to
version
the
functionality,
which
is
absolutely
one
of
the
key
advantages
of
the
library
component,
comparing
indian
packages
because
well
theoretically,
you
can
dynamically
render
that
as
well,
but
that's
pretty
impressive.
B
So
now
I
can
do
modifications
on
the
underlying
packages
without
impacting
the
web
party
if
needed.
Now
that
was
a
really
good,
really
fast.
Demo
super
fast
demo.
But
let's
get
back
on
the
slides.
We
do
have
two
awesome
community
demos
coming
up
as
well
and
we
wanted
to
actually
show
some
new
stuff
which
is
going
to
be
released
to
preview
as
part
of
1.8
release.
A
Wow,
taking
over
as
presenter
all
right,
quick
updates
through
the
PMP
stuff,
so
we
can
get
to
the
remaining
demos
p.m.
PJs.
We
did
get
the
1
3
0
release
out
on
March
8th,
that
was
last
Friday,
so
we
did
bump
the
minor
version
to
1.3
from
1.2
that
reflected
the
full
rewrite
of
the
client
side.
Page
code
so
did
want
to
say
thank
you
very
much
to
everybody
that
helped
test
that
very
quickly
that
week
it
was
kind
of
a
crazy
week,
but
got
that
done,
and
that
seems
to
be
mostly
working
for
folks.
A
Of
course,
if
you
do
see
issues,
please
report
them
in
the
issues
list
and
we'll
do
our
best
to
take
a
look
and
get
those
resolved
more
graph
coverage
also
is
included
in
that
release.
So
we've
got
a
pretty
good
graph
footprint
at
this
point
in
terms
of
coverage,
so
excited
to
see
that
and
I
was
excited
to
continue
for
that,
to
continue
expanding,
so
some
great
work
there
and
I
gotta
other
greats.
Smaller
updates
made
it
in
stuff
from
the
issues
list
that
have
been
there
for
a
little
bit.
A
We
got
those
in
so
check
out
the
changelog
check
out
the
new
release
when
you
get
a
chance
and,
of
course
appreciate
all
your
feedback
on
that
we
are
doing
lots
of
work
behind
the
scenes
on
2.0.
We
do
have
the
road
map
labels
I've
mentioned
before
in
the
issues
list.
So
if
you
would
like
to
comment
on
those
or
submit
an
issue,
slash
suggestion
for
2.0
something
you'd
like
to
see
change
very
happy
to
hear
that
feedback.
A
A
The
new
client-side
page
stuff
and
everybody
that
helps
gives
us
feedback
and
issues
do
very
much
appreciate
that
PNP
github
I
owe
slash
pink
PJs
for
all
the
documentation.
You
can
follow
the
hashtag
PPG
s
on
twitter
and
you
can
follow
me
at
mediocre
bowler
on
twitter,
and
that
is
a
great
way
to
keep
up
to
date
with
what's
going
on
with
PJs
and
the
pnp
program
as
a
whole.
A
I
don't
want
to
make
a
quick
note,
because
I
were
seen
an
uptick
in
a
certain
type
of
comment
and
the
issues
list,
and
I
just
want
to
remind
folks
PPG-
is
a
project
that
I
and
everybody
else.
So
not
just
me
is
working
on
in
our
free
time,
so
that's
time
away
from
family
health,
exercising
hobbies,
etc.
So,
please
be
respectful
of
that
time.
The
alternative
is
that
nobody
supports
it
right
and
it
burnout
is
real
on
open
source
projects.
A
If
you
look
around
the
open
source
world,
you
see
a
lot
of
people
walking
away
from
their
projects
due
to
burnout,
and
that's
not
what
I'm
saying
is
about
to
happen
here,
but
I
am
saying,
do
be
respectful
of
folks
time.
So
I
just
highlighted
one
comment
on
a
recent
issue
and
the
comment
was
basically:
can
you
guys,
you
know
figure
out
if
you're
gonna
do
something
on
this
or
not?
Let
me
know
before
I
waste,
my
time
and
the
idea
that
that
your
time
is
more
valuable
than
my
time
is
just
not
one.
A
That's
gonna
fly
so
keep
that
in
mind
be
respectful.
We
all
have
a
lot
of
stuff
going
on
in
our
lives.
Not
just
me,
this
isn't
just
about
me.
It's
about
all
of
us,
so
we're
doing
our
best
to
support
this.
You
know.
I
was
up
a
lot
of
late
nights
a
couple
weeks,
sir
last
week
for
the
client-side
pages
stuff.
So
this
isn't
a
question
of
caring.
This
isn't
a
question
of
really
wanting
to
do
things
very
well,
it's
just
a
matter
of
time
and
trying
to
balance
these
things
out
in
our
lives.
A
So
please
understand
we're
not
ignoring
your
issue.
We
don't
it's
not
that
we
don't
care
about
your
issue,
it's
that
we
have
a
lot
of
competing
priorities
and
we're
doing
our
best
to
answer
everybody's
questions
and
do
those
things
and
a
great
way
to
help
with
this
kind
of
thing.
Is
you
have
a
few
times
a
few
minutes
to
help
try
and
help
out
somebody
else's
question
right?
You
might
have
an
issue
that
you're
not
sure
on,
but
maybe
you
might
have
an
answer
to
somebody
else's
so
just
want
to.
A
You
know
and
just
trying
to
keep
things
balanced
for
all
of
us
in
the
community,
and
this
isn't
just
I
mean
I
said
p.m.
PJs,
but
this
is
across
all
the
PNP
stuff.
So
just
something
to
keep
in
mind.
You
know
when
you're
demanding
others
spend
their
time
on
your
issues.
So
please
try
and
be
a
little
respectful
of
everybody's
time.
As
we
look
at
this
stuff.
A
Moving
on
to
things
I,
the
new
beta
115
is
out
with
commands
for
managing
teams,
apps
and
settings,
removing
lists
and
site
columns
and
undeclared
records,
which
is
an
off
asked
for
thing,
and
you
know
it's
a
really
cool
feature:
undeclared
records
I've
been
on
projects
where
that's
been
a
real
headache
and
so
nice
to
see
that
functionality
make
it
into
the
CLI
in
progress.
Of
course,
more
commands
for
teams
flow
power,
apps
and
SharePoint,
and
then
as
well.
A
You
can
always
install
the
latest
beta
using
NPM,
install
G
and
then
the
at
PNP
office,
365
CLI
at
next
we'll
get
you
the
latest
beta
more
information.
As
always
a
kms
office,
365
CLI,
that's
for
the
documentation.
You
can
follow
the
hashtag
office,
365
CLI,
on
Twitter
and
as
well.
There's
a
git,
er
channel,
git,
er,
IM,
slash
office,
just
85
CLI,
so
do
check
that
stuff
out
and
a
CLI
is
again
a
really
valuable
tool
to
have
in
your
toolbox.
A
You
know
for
doing
your
SharePoint
projects
and
managing
your
SharePoint
clients
so
for
sure
check
that
stuff
out
SPF
X,
reusable
components,
no
big
updates
this
week,
but
do
wanna
remind
folks
these
exist
and
are
really
super
helpful
inside
your
SP
FX
projects
to
jumpstart
your
development.
So
we
have
two
libraries.
The
property
controls
are
used
primarily
in
the
Edit
pane.
So
when
you
edit
your
webpart,
these
are
controls
that
allow
you
to
easily
pick
things
like
color
taxonomy
terms,
set
titles
and
things
like
that
and
then
there's
a
whole
other
library
of
content
controls.
A
So
those
content
controls
are
really
fantastic
for
helping
you
in
the
body
of
your
web
parts
laying
things
out-
and
these
are
things
like
graphs
and
charts
and
maps,
and
things
like
that
in
the
body
of
your
web
parts
as
well.
People
picker
control
lots
of
great
controls
in
these
save
you
a
lot
of
time.
A
They
are
styled
with
the
office
UI
fabrics
that
are
going
to
give
you
that
nice
office,
or
that
nice
out-of-the-box,
look
in
SharePoint,
so
they're,
nice
and
polished
and
again
really
jumpstart
your
development
in
terms
of
SPF,
X,
webparts
and
application.
Customizers
so
definitely
check
those
out
two
links
down
out
there
down
there
at
the
bottom:
sharepoint
github,
io,
SPF,
SP,
dev
des
FX
does
property
controls
and
the
second
one
SP
dev
FX
controls
react.
Those
are
the
property
controls
and
body
controls.
Consonant
controls
respectively
so
definitely
check
those
out.
A
That's
certainly
a
really
fast
way
to
jump-start
your
SharePoint
framework
development
and
then
one
it
as
well
to
update
folks
on
the
yoga
generator.
If
you
haven't
check
this
out,
lots
of
great
work
has
been
going
into
this
recently.
This
is
a
community
supported.
Spf
X
yeoman
generator
that
is
built
on
top
of
the
standard
SharePoint
framework
generator.
So
at
the
end
of
running
this,
you
do
get
a
normal
SharePoint
framework
project
with
all
the
same
underlying
files,
capabilities,
references,
etc,
but
it
does
have
some
extra
stuff
in
it.
A
C
So
yeah
my
name's
Laura
and
today
I'm
presenting
to
this
public
teams,
I'm,
not
a
member
of
web
part
which
I
contributed
to
the
SPF
examples.
A
little
woke
up
and
I
originally
implemented
this
as
a
conference
demo
for
ESPC,
2018
and
I
got
this
idea
from
a
colleague
of
mine
and
basically
the
situation
went.
She
was
having
conversation
on
a
team's
channel
about
a
certain
topic
and
then
another
person
comes
in
and
says
you
know:
we've
been
talking
about
the
same
thing
in
another
team.
C
So
how
about
you
come
over
there
and
let's
continue
to
chat
over
there
and
she
was
lucky
I'm
sure.
But
how
I
wasn't
able
aware
of
this
team
before
at
this
moment?
Like?
Is
there
some
place
where
I
could
see
all
the
public
teams
that
aren't
in
our
tenant?
Because
if
we
go
to
teams
and
click,
this
join
our
create
team?
When
we
get
here
are
just
recommendations,
this
doesn't
list
all
teams
in
terms.
So
of
course
you
can
go
in
for
a
simple
start
searching
for
a
team,
and
then
it
returns
something
to
you.
C
But
out
of
the
box,
there
is
no
place
where
you
could
see
a
list
of
all
public
teams
in
a
tenant.
So,
for
example,
if
you
would
be
interested
in
marketing,
you'll
know
that
there's
a
team
or
you
can
join
and
discuss
about
that
territory,
but
that
web
part
allows
you
to
do
that.
So
for
somebody
who
I
wanted
to
join
this
team
with
cats
because
I
like
cats,
that
adds
me
to
that
team
for
at
least,
should
I
marketing
it
to
more
effect.
C
Yeah
it
added
me
and
then,
if
we
refresh
the
page,
we
naturally
don't
get
the
team
here
anymore,
because
we're
a
member
of
that
and
this
webpart
uses
graph
for
fetching
the
teams
and
also
for
adding
the
person
into
the
team
and,
let's
take
a
look
at
the
code.
In
the
end,
this
is
a
very,
very
simple
web
part.
There's
like
132
lines
of
code.
It's
very
simple
here.
C
In
the
beginning,
we
reference
the
MS
craft
client
for
Colin
graph
and
I've
implemented
some
helper
methods
down
here
for
both
get
and
post
requests
and
they
used
his
call
graph
that
fat
free
chose
the
response
and
the
requests
are
done
to
craf
synchronously,
because
we
need
the
response
before
can
do
stuff
with
it
and
for
the
web
part
we
need
to
assign
permissions
to
craft.
So
these
are
the
three
permissions
that
are
needed.
So
when
you
deploy,
this
were
part
to
the
app
catalog.
C
C
C
We
can't
give
the
caramel
is
directly
from
Kraft.
We
need
to
first
get
the
team's
that
the
user
is
a
member
of,
and
then
all
the
teams
and
then
make
a
difference
between
these
two
arrays,
and
we
also
need
to
filter
team
space
of
the
public
visibility
property,
because
craft
doesn't
allow
you
to
do
that
directly.
C
How
come
back
to
these
two
rows
in
a
bit
and
when
we
have
this
missing
team
IDs
or
the
IDS
of
the
teams
that
the
user
is
not
yet
a
member
of
we
create
this
chased
an
object
that
contains
the
team
objects
of
those
teams,
because
we
might
want
to
use
all
the
values
all
the
properties
of
those
teams
as
well.
In
addition
to
the
ID,
for
example,
the
display
name
so
I
can
just
write
into
our
product.
C
So
we
get
the
container
element
and
then
we
also
get
the
user
ID
from
graph
for
the
currently
logged
in
user.
Because
not
sure
we
need
that
if
we
want
to
add
the
user
to
the
team's
and
for
each
of
the
teams
that
we
did
use
that
the
user
doesn't
belong
to.
Yet
we
create
a
row
for
each
of
them,
then
add
a
button
to
the
beginning
of
the
row
and
we
save
this
team
ID
as
the
button
ID.
C
You
could
just
pass
this
as
a
parameter
later
on
as
well,
but
I
figured
might
as
well
start
here,
because
we
need
to
use
the
button
M
and
relation
one
two
and
then
change
the
body
text.
And
here
we
add
this
I,
remember
event
handler
to
the
onclick
listener.
At
the
bottom,
a
button
reaches
add
a
spectrum,
and
that
contains
the
team
displayed
and
in
this
errand
handler
we
get
the
source,
which
is
the
bottom,
the
user
clicks
and
then
the
user
ID,
and
we
disable
the
button.
C
So
the
user
can't
click
several
times,
because
the
user
select
click
and
then
we
changed
the
NSX
to
join
so
they
feel
like
yes,
I
did
something
useful
by
clicking
with
the
bottom,
and
then
we
built
the
body
for
the
Croft
request.
That
is
basically
a
reference
to
the
user
object
and
then
make
a
post.
How
do
we
get
the
team
ID
from
the
bottom
ID?
C
Because
it's
the
same,
because
we
have
this
in
here
and
that's
basically,
everything
that
is
worth
bought,
dusk
and
I
promise
to
come
back
to
these
two
laws
occur
so
yeah
I.
Can
they
mentioned,
unfortunately,
crafters
and
hours
to
build
a
groups
based
on
visibility.
So
you
can't,
at
this
hour
data
filter
visibility,
equals
public
here
and
only
receive
public
teams.
C
What
this
line
actually
does
it
returns
all
teams,
wanna,
say
all
teams
I
mean
all
teams,
including
private
teams,
that
the
user
is
not
a
member
of
so
you
might
want
to
discuss
if
you
plan
on
using
this
in
a
customer
environment
when
what
to
discuss
with
them.
Is
it
okay,
like
are
your
users
very
tech
savvy?
You
do
they
have
people,
because
if
they
have
people
up
and
running
and
they
refresh
the
page,
they
can
see
the
requests
going
on
and
the
response
contains
display
names
for
all
the
priorities,
entertainment.
C
C
So
you
know
when
you
generate
this
as
B
of
X
a
project,
you
get
this
team's
folder
that
contains
the
manifest
file
and
the
logo
files,
and
then
you
put
it
together
into
a
zip
file
and
that
you
can
install
it
to
your
tenants,
app
catalog
in
here
by
uploading,
a
custom
app
another
that
you
can
pin
it
as
a
tab
and
then
it
gets
rendered
in
here.
So
this
can
be
quite
useful.
C
C
A
D
Right,
thank
you
so
good
morning
or
good
evening.
Firstly,
thank
you
for
to
me
this
opportunity
to
present
my
work
in
shape
on
Facebook.
So
today
this
sample
I'm
going
to
demonstrate,
is
about
consuming
the
Google.
Api
is
in
SharePoint
framework
client-side
web
part.
So
something
about
me
for
those
who
don't
know
me
myself
and
entities
Knutson
and
I'm
from
Pune
India
and
have
been
working
with
Shay
Point
office,
365
and
Microsoft
Azure
for
years.
These
are
some
social
handles
to
get
connected
with
me,
so
we're
coming
to
this
sample.
D
There
are
quite
a
few
interesting.
A
peer
is
available
in
the
Google
side
and
the
purpose
of
this
sample
is
to
explain
the
process
of
existing
them
from
a
SpaceX.
So
the
sample
is
part
of
a
larger
concept,
around
enterprise
scenario,
of
how
Google
APs
can
be
used
in
shape
one
framework,
so
this
particular
sample
is
developed
specifically
to
consume
Google
feed
API
and
display
the
Fitness
data
in
SPF
X
of
the
part.
D
So
the
sample
is
developed
using
the
react.js
and
SPF
X
version,
1.7
point
1,
so
this
sample
can
be
accessed
from
this
particularly
URL,
which
is
here.
It
describes
all
about
how
to
install,
configure
and
use
the
sample.
So,
firstly,
that
we
will
have
to
generate
this
earth
2.0
tokens
and
all
those
things
we
will
go
over
it
in
a
demo.
But
this
page
explains
entire
information
about
how
to
get
it
installed,
configured
and
start
using
the
sample
all
right.
D
So
so
then
I
saw
somebody
like
there,
a
number
of
fitness
bands
and
apps
available
in
the
market
and
app
stores.
So
the
reason
for
going
with
the
Google
fit
is
that
it's
free,
it's
a
mobile,
app
and
once
the
app
is
downloaded
to
mobile,
it
gives
like
of
all
your
activities,
and
the
second
thing
is:
it
does
not
need
any
additional
band
to
be
tied
up
to
the
Everest
and
the
third
important
point
was
we
wanted
to
explore
like
how
we
can
integrate
the
Google
restful
appears
with
his
prefix.
D
So
as
a
developer,
I
wanted
to
go
one
step
further
and
start
programming
against
the
fitness
data
so
that
we
can
use
it
in
any
application
or
mold
it
further.
So
Google,
but
in
step
here,
is
just
help
us
doing
that
and
it
enables
to
store
and
access
the
user
data
in
the
fitness
store.
So
coming
back
to
like
how
we
can
get
started
with
this
Google
REST
API
edge.
D
So
the
first
and
foremost
thing
is
that
we
should
have
a
Google
account
to
start
using
this,
and
the
second
thing
is
that
we
should
generate
both
2.0
client,
ID
and
client
secret.
So
for
that
we
can
use
this
console
dot
developers.google.com
and
from
here
we
can
generate
a
client,
ID
and
client
secret.
So
let
me
just
refresh
this
alright
so
from
here
we
can
create
a
new
project
and
start
using
it,
but
just
to
save
the
time
I
already
have
one
project
created.
I
will
start
using
this.
D
So,
firstly,
that
will
have
to
setup
the
credentials
so
I
already
have
a
set
it
up,
but
this
page
will
help
us
to
set
up
the
credentials
like
which
API
do
we
want
to
lose?
Maybe
fitness,
API
or
other
api's,
and
from
where
this
ApS
will
be
called
from,
so
it
could
be
from
JavaScript
enabled
web
browsers
or
from
Android
or
iOS
or
anything.
In
our
case,
we
are
using
a
web
browser
because
we
are
calling
this
from
from
any
sphere
fix
web
part
and
then
what
kind
of
data
element
exists
like?
D
Is
it
a
user
data
or
application
data?
So
since
we
want
to
get
the
information
about
the
user
activities,
we
are
going
ahead
with
user
data,
so
I
already
have
created
the
credentials.
Maybe
let's,
however,
look
at
it.
So
this
is
how
the
credentials
look
like.
We
have
a
plant
ID
client
secret
to
access
this
aps
and
since
it
is
kind
of
an
interaction
of
Google
APs
from
SPF
X.
So
for
that
reason
it
is,
it
is
a
cross
domain
call
so
to
avoid
any
kind.
D
Of
course
we
we
need
to
use,
or
we
need
to
authorize
the
JavaScript
origins.
So
for
that
reason
you
can
see
that
I
have
added
my
SharePoint
comm
site
here
as
authorized
of
JavaScript
origin
and,
for
example,
if
you
want
to
test
it
on
a
SharePoint
local
work
means.
You
can
also
add
this
local
host
:,
four
three,
two
one
as
the
authorized
JavaScript
origin.
So
this
will.
D
This
will
help
us
to
build
a
secure
connection
between
Google
API
Schuylkill
recipe
as
and
SPF
x,
so
yeah.
So
that's
about
this
and
then
the
next
thing
is
that
before
we
start
using
the
ten
SPF
X,
we
we
again
have
one
playground
offered
by
by
Google,
wherein
we
can
start
using
or
start
testing
this
API.
So
once
we
have
generated
this
client,
ID
and
client
secret,
we
can
taste
the
Google
API
using
Google
developer
playground.
So
here
is
the
playground.
D
Let
me
help
you
flush
this,
so
this
will
just
help
us
to
test
our
recipes
or
the
Google
recipes.
So
this
earth
2.0
playground
for
Google
developers
platform
is
it
is
available
from
here,
and
this
playground
will
help
to
developers
to
explore
various
Google
API
s
and
understand
their
request
responses
and
create
query
they
if
he
has
to
fetch
the
data.
So,
for
example,
you
can
see
here
that
we
can
query
the
Ad
Exchange,
we
can
even
query
the
adsense
and,
for
example,
the
more
interesting
part
will
be
email
part.
D
So
let
me
scroll
bit
down
for
email
yeah
so
from
here
we
can
also
start
using
or
start
using
the
ApS
for
Gmail,
so
we
can
read
compose
and
send
the
emails
using
these
ApS.
So
there
are
numerous
some
helpful
Google
APs
available
here
which
can
be
consumed.
So
even
there
are
some
Google
Analytics.
Yet
this
because
of
a
welcome
api's
and
all
of
those
things.
So
for
this
demo
we
are
going
to
explore
more
about
these
Fitness
APs.
D
So
for
this
we
should
explore
this
fitness
v1
and
once
you
hover
on
each
of
the
activities,
so
there
are,
these
all
are
called
as
an
activity
inside
this
restful
ApS.
So
it
will
show
you
some
help
text
about
what
what
this
API
can
help
us.
So
this
one
is
for
grooving
the
activity,
information
about
the
Google
flick,
and
then
here
are
some
other
for
maybe
reading
the
glucose
level,
reading
the
temperature
and
and
all
other
things
so
just
for
demo
purpose.
D
Maybe
let's
select
all
so
that
we
want
to
query
all
of
this
REST
API.
So
let
me
select
those
very
quickly,
so
we
have
selected
almost
all
of
the
ApS
which
are
available
from
Fitness
v1.
Then
we
will
click,
this
authorize
ApS
so
that
we
we
will
get
authorized
to
use
this
API.
So
this
will
ask
us
for
the
user
account.
I
am
selecting
my
account
here
alright.
So
then
it
will
ask
us
for
for
the
confirmation
that
we
are
going
to
use
these
many
api's
from
here.
D
So
once
you
click
allow,
then
you
will
be
able
to
access
all
those
api's.
So
then
Google
gives
this
authorization
code,
which
is
kind
of
an
unique
authorization
code
which
we
can
help
to
exchange
the
tokens
between
the
calls.
So
for
that
we
can
just
click.
This
exchange
authorization
code
for
tokens
and
then
we
get
the
Refresh
token
and
access
token,
and
from
here
we
will
be
able
to
make
or
test
our
recipients
so
for
that
I
already
have
some
list
of
ApS
available.
D
So
all
these
estimator
steps
will
give
us
the
information
about
how
many
steps
we
have
worked
so
far,
and
then
there
are
also
other
things
like
LEDs
and
all
those
things
which
can
be
tracked
from
here.
So
then
so
so
that
means
in
a
response
all
the
available
data
sources
for
that
particular
user
will
be
listed
along
with
the
data
type
and
then
estimated
steps
is
one
of
the
example
which
gives
us
the
number
of
steps.
So
just
to
explore
more
about
this
estimated
steps
we
will.
D
We
will
try
to
get
the
number
of
steps
which
which
kind
of
I
executed
today
so
for
that
we
will
use
this
post
HTTP
method
and
with
this
request,
URI,
which
is
kind
of
getting
the
or
acquiring
the
fitness
API.
For
me
for
this
currently
logged-in
user,
and
it
is
trying
to
get
the
aggregate
data
set
and
for
that
we
have
to
pass
in
some
information
like
this.
One
I
will
explain
what
this
is
so
this
is
from
here.
D
We
are
saying
that
Tom,
we
just
want
to
know
the
number
of
estimated
steps
which
have
been
executed
by
the
user
and
during
which
time
duration.
So
this
is
just
one
one
sample
start
time
and
end
time
during
which
we
want
to
calculate
the
number
of
steps.
So,
for
example,
if
you
want
to
get
the
current
time,
then
probably
you
can
do
something
like
this
all
right,
so
you
can
just
type
new
date.
D
In
and
this
will
give
you
the
numeric
representation
of
what
is
the
time
now
and
you
can
probably
have
it
in
the
start
time
and
then
you
can
go
out
to
the
M
fill
M
of
this
way.
Look
at
the
end
time.
So,
once
we
have
this,
we
can
send
it
as
a
request
body
and
then
just
click
send
the
request,
and
here
we
we
get
the
entire
response,
like
how
many
number
of
steps
that
I
have
I
have
a
bob
today.
D
So
in
this
we
can
just
search
for
ink
well
so,
which
is
the
data
type
for
this
particular
instrumented
steps.
So,
for
example,
now
you
can
see
that
there
are
five
intervals
in
which
I
have
walked
today.
So,
for
example,
if
we
sum
up
all
those
intervals,
so
it
will
give
give
us
the
list
of
all
steps
which
which
is
run
by
or
which
is
executed
by
that
user.
D
So,
similarly,
we
can
get
the
number
of
calories
burn
and
all
those
things
so
so
it
is
for
that,
for
the
implementation
of
this
particular
sample,
I
have
used
the
NPM
package,
which
is
react.
Google
authorize
so
this
particular
NPM
package
help
to
get
authorized
to
to
Google
and
then
from
there
we
can
execute
the
recipients
against
the
Google.
D
So
this
is
the
client
ID
which
which
is
coming
from
here,
which
we
can
add
to
this
particular
component,
and
then
this
one
will
be
shown
up
as
an
button
and
we
can
have
one
code
on
the
success
of
this
authorization
and
on
failure
of
this
authorization.
So
maybe
let's
get
to
the
demo
of
this.
So
this
is
how
it
looks.
So
this
is
the
button
which
is
which
is
executed
by
that
react
component
which
helped
us
to
authorize
against
the
Google
APs.
D
So
it
will
not
ask
me
for
the
login
from,
but
here
we
get
a
little
like
number
of
hours
or
number
of
minutes
and
spend
today
with
any
of
the
activity,
the
distance,
what
I
have
traveled
and
the
calories
which
I
have
burned
and
the
number
of
steps
I
have
calculated.
So
this
is
not
very
much
encouraging
data
for
everyone,
but
ya
miss
at
least
from
here.
We
are
able
to
make
a
call
to
Google
the
REST,
API
and
Radhika,
so
then
how
it
is
implemented.
D
So
let
me
go
to
the
widget
studio
core
to
explain
the
entire
code,
so
we
will
start
with
this
render
method
and
inside
this
we
have
this
component
called
as
Google
authorized.
So
this
component
will
help
us
to
authorize
to
to
the
Google
so
that
we
can
call
the
rest
APs
and
to
this
we
are
passing
on
this
blue
scopes.
So
that
means
we
want
to
read
thin
user
activities
and
then
we
want
to
read
how
many
kilometers
or
how
many
meters
he
has
walk.
D
So
we
want
to
get
the
location
data
so
to
the
scope.
We
can
define
these
two
activities
and
then
we
can
pass
in
the
client
data
with
which
we
are
kind
of
getting
from
the
web
part
property
and
then
on
the
success
and
failure.
We
can
have
a
core.
Probably
I
can
directly
jump
to
that
part.
So
this
is
the
onsuccess
method,
and
here
we
are
calling
the
read
step,
count:
read
calories,
distance
and
read
activity
time
to
get
the
number
of
first
steps
and
calories
and
all
those
things.
D
So
here
we
have
that
particular
methods
which
are
just
calling
the
services
to
get
the
number
of
steps
number
of
calories.
So
probably
we
will
directly
jump
to
this
service.
So
in
the
service
we
have
only
one
generic
method
called
as
get
google
fit
data
to
which
we
are
passing
the
activity
which,
with
which
we
want
to
get
the
data
from,
and
once
we
have
the
data.
We
are
just
kind
of
accumulating
all
those
data
or
adding
all
those
data
to
get
the
exact
number
of
exact
number
of
steps.
D
We
have
executed
or
exact
number
of
calories,
which
you
have.
We
have
one
because
this
happens
at
a
regular
interval
because
maybe
I
have
walked
now
for
10
minutes
and
then
maybe
after
half
an
hour,
I
walk
for
10
minutes.
So
it
will
calculate
or
adds
up
all
those
data
to
show.
So
I
will
quickly
move
to
this
main
method,
which
is
get
Google
food
data
and
go.
D
Alright,
so
just
give
me
one
minute:
I've
ever
tried
to
finish
it
up
so
almost
at
the
end
of
the
demo.
So
this
is
the
main
maker.
You
get
google
food
data
and
from
here
we
are
calling
this
Google
API
restful
api
and
passing
the
activity
scope
and
from
here
we
get
the
entire
response
in
in
a
JSON
format,
and
then
we
are
passing
it
to
be
a
component
to
show
it
on
on
on
a
page,
and
this
is
how
it
looks
like
alright,
so
yeah,
so
that
was
that
was
all
for
this
demo
yeah.
A
Great
start
really
exciting
stuff,
it's
really
cool
to
see
how
to
interface
there
with
the
Google
API,
so
always
very
cool
and
shows
a
new
capability
so
point
in
data
from
different
sources
and
surfacing
that
in
the
SharePoint
framework
is
really
a
lot
of
what
SharePoint
framework
is
all
about.
Our
next
SharePoint
framework,
JavaScript,
maybe,
will
be
March
28
2019,
that
is
in
two
weeks.
A
The
next
general
dev
meeting
will
be
next
Thursday,
March
21st,
hope
to
see
you
there
I
want
to
thank
visa
for
his
demos,
Laura
and
then
a
deep
for
their
demos,
great
stuff.
As
always.
Thank
you
all
very
much.
Thank
you
all
have
a
great
rest
of
your
week.
Thanks
for
attending
and
look
forward
to
talking
to
you
soon
take
care.