►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
But
we
did
want
to
as
always
start
off
with
what
is
the
special
interest
group
all
about?
What
are
we
here
to
do?
We
are.
The
specialist
group
is
part
of
the
larger
sharepoint
patterns
and
practices
program
which
which
exists
under
SharePoint
engineering
in
the
product,
or
cannot
hear
a
thing
interesting.
A
A
B
Lost
my
place
yes
didn't
mind.
My
whole
thing
look
part
of
get
back
on
the
script:
yep
pekan
script,
part
of
the
larger
sharepoint
patterns
and
practices
program,
and
what
the
special
interest
groups
do
is
allow
folks
with
a
special
interest
in
certain
topic
areas.
So
this
one
is
client-side
development.
We've
also
got
one
for
the
PowerShell
and
the
core
library
components
as
well
bi-weekly
meeting.
B
So
if
you
can,
of
course
attend
both
attend
one,
the
other
kind
of
wherever
you
have
that
interest,
but
lets
folks
have
a
little
bit
more
deeper
dive
into
these
special
topics
because,
as
the
program
was
growing,
the
monthly
call
just
wasn't
enough
to
cover
everything.
And
so
we
decided
to
sort
of
break
things
out,
provide
a
little
bit
more
focus
in
certain
areas.
B
We
talked
about
the
JavaScript
core
component
that
we've
built
and
is
available
that
just
went
out
in
106
we'll
talk
about
that
here
in
a
little
bit
and
then
two
links
down
at
the
bottom
of
the
SharePoint
pnp
community
is
what
we've
now
replaced
G
amber
with
it's
the
microsoft
tech
community.
That's
where
you
can
go
for
questions
discussions,
things
like
that,
especially
around
the
SharePoint
framework,
and
then
we've
got
dev
office,
calm,
/
SharePoint!
B
That
is
your
jumping
off
point
for
everything,
sharepoint
development,
so
SharePoint
framework,
as
well
as
all
the
classic
development,
which
is
still
obviously
100,
sent
valid.
One
hundred
percent
still
used.
So
if
you
have
questions
on
that,
also
SharePoint
community
or
dead
at
office
com
are
the
great
resources
to
have
their
and
specific
to
the
core
component.
You
can
also
use
the
git.
Er
channel
is
a
great
place
as
well.
That's
linked
off
the
homepage
of
the
project
so
moving
on
specifically
this
week.
What
are
we
going
to
talk
about
updates
to
the
SharePoint
framework?
B
Not
a
lot
there?
The
the
big
last
update
was
released,
number
five,
but
will
touch
on
some
stuff
there.
Some
updates
around
the
j
s
core
component,
and
then
we've
got
two
great
community
demos,
one
from
kevin
talking
about
managing
state
in
these
client
side
frame
works
with
redux
and
mama
box,
and
then
Sergei
is
going
to
talk
about
using
the
j
s
core
from
node.
B
Those
of
you
might
be
familiar
with
Sergei,
with
his
work
on
things
like
SP
save
and
some
of
the
SP
authentication,
libraries
and
then
hopefully,
at
the
time
at
the
end,
we'll
have
time
for
an
open
discussion
QA.
So
you
can
have
a
chance
to
ask
us
questions
or
ask
the
folks
that
did
the
demos
questions
as
well.
You
can
always
ask
things
in
the
eye
on
window.
Will
do
our
best
to
keep
up
with
that
pardon
me
so
jumping
into
the
SharePoint
framework,
Developer
Preview
updates,
yeah.
A
So
and
my
animations
are
completely
messed
up,
so
that's
final,
that's
actually
yeah.
Thank
you.
So
nothing
really
as
super
super
new
from
a
two
weeks
perspective.
So
we
don't
know
we're
still
on
the
top
five
like
Patrick
mentioned,
the
the
following
thing
is
that
we're
looking
all
ready
at
this
point
to
come
up
with
their
release
candidate
relatively
soon
again,
soon
or
sooner
or
later,
is
a
relative
thing,
but
the
following
trough
will
be
already
a
release
candidate
and
then,
after
that,
we're
moving
to
GA.
A
So
all
of
our
engineers
who
are
actually
building
their
special
effects
are
super
super
busy
on
on
finalizing
the
whole
setup.
So
we
can
actually
push
out
the
first
version
of
the
SP
FX
out
relatively
soon,
it's
not
matter
of
days
in,
but
still
and
obviously
we
don't
want
to
push
well,
let's
not
actually
even
speculate
that
cool
the
other
thing
yeah,
the
other
thing.
What
will
happen
is
that
we
are
opening
up
to
the
Developer
Preview
also
for
first
release
tenants,
so
you
will
then
be
able
to
start
using
the
SharePoint
framework.
A
If
you
are
using
a
tenant
which
has
the
first
list
in
April,
there
will
be
warning
signs
that
there
will
be
messaged
miss
a
post
in
the
in
the
tenant
messaging
center,
and
we
clearly
want
to
make
sure
that
people
do
understand
them.
That's
still
a
developer
preview.
You
should
not
use
SPF
X
at
that
point
yet
in
production,
even
though
it
will
work
in
the
first
release.
Tenants,
we
will
announce
whenever
we
are
ready
for
GA.
A
A
A
This
new
web
casts
released
as
well
more
coming
soon,
so
next
Monday's
webcast
it's
around
SPF
X
as
well.
So
the
last
webcast
was
around
how
to
use
your
existing
JavaScript,
implementations
or
customizations,
which
you
built
in
the
context
of
SharePoint
framework.
The
next
one
is
around
building
multi-page
or
multi-view
client-side
web
part.
So
how
do
you
remain
the
state
in
an
angular
case
in
angular
implementation,
and
we
are
working
on
a
react
based
at
page
sample
as
well,
and
more
articles
and
documentation
is
in
q4
depth
of
circumcision.
A
The
following
slide
is
is
essentially
just
listing.
What
do
we
have
as
a
new
samples
so
as
part
of
the
the
November
release,
which
meant
live
black
mentioned
on
Monday
this
one,
two,
three,
four,
five,
six,
seven,
eight
well
nine
or
eight
new
samples,
one
of
them
are
from
community.
So
thank
you
for
those
because
they
are
extremely
valuable
for
people
learning
how
to
get
started
within
the
ship
with
SharePoint
framework.
Some
of
them
are
super
simple
and
they
show
a
specific
scenario
and
that's
by
an
intention.
A
So
they're
not
production,
already
samples,
some
of
them
are
much
more
complex
and
they
they
combine
multiple
different
services
like
flow
or
bot
framework
or
and
so
on.
So
there's
multiple
different
scenarios
then
combined
in
the
sample
and
that's
we're
kind
of
taking
the
similar
kind
of
approach.
What
we
did
with
the
classic
BNP
with
the
Addie
model,
where
we
will
provide
the
community,
simplistic
samples.
A
So
they're
not
uber
complex,
not
necessarily
production
ready,
but
they
concentrate
on
showing
certain
scenario
so
you're
able
to
learn
the
scenario
and
then
we're
able
to
start
using
that
within
your
production,
already
wet
pots,
HTTPS
kids
up
that
comes
our
sharepoint
SB
EDF
FX
webparts
is
the
repository
where
we're
actually
getting
this
in
and
sharing
them
out.
There's
quite
a
lot
of
Oracle's
are
coming
sooner
or
later
from
the
engineering
guys.
A
So
we're
working
on
on
that
one,
as
well
as
an
example
to
angular
2
prototype
is
something
which
came
out
of
the
SharePoint
engineering,
together
with
the
work.
What
we
did
with
angular
2
guys,
so
we
are
actually
working
with
Google
on
some
of
this
stuff
as
well,
so
making
sure
that
we
are
aligning
on
the
on
the
models
and
their
stuff
is
working
properly
with
us
and
vice
versa.
It's
a
completely
different
world
nowadays,
which
is
super
cool
on
a
Widow's
and
webcasts.
Like
mentioned,
the
the
new
video
will
come
out
next
monday.
A
It's
around
building
multi-view
web
parts
with
angular
because
on
how
to
handle
essentially
the
US
states,
transitions
and
there's
a
lot
of
existing
web
web
casts
out
there.
We're
trying
to
give
these
webcasts
and
nowadays,
quite
short,
so
they're
like
15
to
30
minutes
max
I'm,
concentrating
on
one
topic.
So
you
will
more
easily
find
a
time
to
have
a
look
on
it
or
whenever
you
are
then
implementing
stuff
in
the
future.
After
GA,
you
can
go
back
and
see
it
webcast
and
okay,
that's
how
it's
actually
done.
A
Excellent
I'll
just
copy
this
example
and
get
moving
on
my
implementation
and
those
are
all
in
the
PMP
youtube
video
section
where
we
have
a
lot
of
other
videos
as
well.
But
I
think
that
sums
up
the
SharePoint
framework
status,
like
mentioned,
not
super,
super
a
massive
amount
new
from
engineering
side,
but
a
lot
of
new
samples
to
have
a
local
out
of
new
samples
to
play
with
and
we'll
come
up
with
a
a
new
stuff
from
an
engineering
sites
relatively
soon
as
well
and.
B
It's
not
tied
directly
to
the
SharePoint
framework,
but
we
did
record
as
well
a
really
cool.
You
got
the
whole
core
team
together,
so
we've
got
that'll
be
coming
out
sometime.
The
next
couple
weeks
here
at
the
MVP
summit,
so
that'll
be
a
really
I
think
interesting
thing
for
folks
out
in
the
community
to
listen
to
just
because
it's
a
quick
hit
on
hearing
about
all
the
different
stuff.
The
past
practices
is
working
on,
so
that'll
be
a
fun
thing
as
well.
B
Not
it
talks
about
sharepoint
train
work,
but
talks
about
everything
else
as
well,
so
I
just
popped
into
my
head,
as
we
were
talking
about
webcasts,
so
that'll
be
cool,
so
that's
upcoming
as
well.
So
now
update
on,
what's
been
going
on
with
the
jas
core
component
and
thank
you,
as
always
to
our
contributors,
really
appreciate
all
the
great
work
that
goes
on
there
and
actually,
this
morning
before
I
woke
up,
somebody
had
asked
a
question
and
somebody
else
mauricio
had
actually
answered
that
question
before
I
was
even
out
of
bed
this
morning.
B
So
great
work
to
both
of
folks
asking
and
answering
so
awesome
to
see
people
helping
each
other.
That's
really
really
exciting.
It
really
helps
build
the
community
up
and
help
support
everybody
learning
more.
So,
what's
been
going
on,
we
released
10
at
six
this
week,
so
new
features
largely
driven
by
great
feedback
from
the
community.
B
So
both
suggestions
for
new
functionality
and
suggest
your
issues
being
reported
so
really
appreciate,
hearing
from
the
community
on
those
topics
and
then
hopefully
showing
that
you
know
we
take
that
feedback
to
heart
and
make
changes
and
updates
to
the
library
to
to
support
that
feedback
so
really
appreciate
it.
Keep
that
going
as
you're
out
there
using
the
library.
B
Just
let
us
know
if
you
run
into
trouble
or
have
ideas
on
making
it
better,
because
that
again
feeds
back
to
benefit
everybody
so
also,
as
we've
been
out
here
been
meeting
with
the
product
group,
which
is
really
exciting,
I.
Think
for
all
of
us,
in
the
program
for
the
patterns
and
practices
program,
we're
getting
a
little
bit
closer
to
engineering
as
well
as
I
did
want
to
share
Engineering
wanted
to
recognize
the
great
work
everybody
the
community's
done
and
sort
of
extending
their.
B
Thank
you
to
all
of
you
to
say
thank
you
as
well
for
the
great
work,
so
it
they're
really
impressed,
I
have
to
say,
with
the
patterns
of
practice
program
and
what
all
of
you
have
been
doing
so
feel
good
about
that.
That's
that
the
praise
doesn't
come
lightly
from
that
team,
so
very
cool
to
get
that
recognition
for
all
the
great
work
all
of
you
have
been
doing
so.
Thank
you
give
me
my
theme
hate
to
see
ya.
This
is
a
is
a
taskmaster
and
then
did
what
touched
on
again.
Issues
are
being
reported.
B
Thank
you.
Thank
you.
Thank
you
for
that
really
appreciate
it.
We
are
able
to
fix
all
the
current
issues
for
the
release,
so
that's
great.
So
keep
those
issues
and
ideas
coming
as
well.
Do
you
want
to
remind
folks
if
you
find
an
issue
and
have
some
time
you
can
always
submit
a
pull
request
to
address
that
issue
as
well?
So
I've
got
a
few
of
those
in
the
last
release
as
well.
B
So
that's
really
fantastic
from
the
community
two
links
down
there
at
the
bottom
again
to
the
tech
community
and
then
to
the
git
er
page,
which
is
also
a
great
place
for
sort
of
informal
quick
questions.
I've
seen
a
lot
of
good
conversations
on
both
places,
so
those
are
how
to
get
involved,
how
to
jump
in
and
how
to
reach
out
to
us
opportunities
to
contribute
really
unchanged.
I
think
next
week,
I'm
going
to
update
this
letter
for
the
next
meeting.
B
I
want
to
update
this
slide
just
somehow,
but
the
big
thing
one
remind
folks
if
you
would
like
to
write
a
web
part
or
do
something
with
SharePoint
framework
or
the
JavaScript
core
and
would
like
to
show
it
off
on
this
call.
Just
let
us
know
we'd
love
having
the
demos
from
the
community,
it
really
showcases
what
folks
are
doing
out
there
as
well
as
scenarios
that
you
know
we
may
not
even
have
thought
of
ourselves
to
see
what
people
do
with
the
SharePoint
framework
in
the
library
so
keep
that
stuff
coming.
B
A
C
D
So
it's
basically
the
same
principle
as
in
every
react
application
but
applied
to
the
pods,
which
basically
gives
you
the
same
benefits
and
so
I
know.
A
lot
of
guys
are
new
to
react.
Development
and
I
did
this
for
a
while,
now
Zaun,
probably
a
bit
more
knowledgeable,
and
the
basic
problem
is
that
so
this
is
the
under
samples
repository
and
how
all
of
the
rapids
usually
look
like
in
the
beginning.
D
You
just
compare
like
this
property
change
and
then
I
need
to
load
data
and
set
a
state
of
my
component
and
something
else
happens.
I
set
another
state,
and
this
is
fine
for
like
smaller
parts,
but
the
problem
is
that
SEO,
rapid
growth
or
application
and
stuff
can
get
really
messy,
and
it's
really
hard
to
get
like
our
view
over
the
complete
application
state
and
just
see
what
but
actually
currently
is
loaded
and
or
something
throws
an
error
that
you
can
stall
the
arrow.
And
how
do
you
get
into
other
components?
D
All
those
questions
are
usually
starting
to
come
up
as
here
rapid
grows
bigger
and
what
I
want
to
show
you
today
is
basically
how
to
serve
those
problems
with
two
different
frameworks
and
another
thing
that
they
try
to
solve.
Is
that
currently,
and
the
other
part,
is
your
main
component
keine
or
a
trellis,
your
main
component
right
here
and
everything
that
you
want
to
pass
down
to
your
sub
components?
You
actually
have
to
pass
down
as
properties
and
depending
on
how
big
your
back
part
is.
D
This
can
be
like
a
four
or
five
level
hierarchy,
and
so
you
have
to
test
those
properties
down
basically
order.
I
will
get
3
which
gets
tedious
to
ride
and
how
to
update,
because
if
you
want
to
add
another
one,
you
have
to
pass
it
down
the
whole
Shane,
basically,
which
is
not
that
nice
and
yeah.
Those
two
frameworks
basically
want
to
solve
those
problems
by
giving
you
a
nicer
way
to
handle
the
application
state.
D
D
It
easier
for
me,
ok,
so
basically,
there
are
two
frameworks
that
currently
try
to
solve
the
state
management
in
react.
Applications.
First,
one
is
ma
pigs,
which
is
a
bit
newer,
I
would
say,
and
it's
a
bit
easier,
the
beginning
to
learn,
because
ma
Biggs
is
basically
an
object-oriented
framework
and
the
basic
idea
is
that,
first,
you
define
your
store,
which
is
just
the
object
that
holds
all
your
application
state,
so
no
state
lifts
into
components,
but
everything
lives
in
a
store
and
photos
demo.
D
So
the
basic
principle
is
actually
quite
easy,
but
instead
of
a
race
or
opportunity
of
naps
and
also
all
the
maps
and
observe
we
raised,
but
the
API
is
exactly
the
same
as
native
JavaScript
classes,
though
everyone
who
has
used
a
reactive
library
like
RX
chairs
before
is
probably
familiar
with
their
with
this
stuff,
but
it's
actually
quite
easy
and
a
lot
of
magic
is
happening
in
the
background.
So
it's
you
don't
have
to
do
a
lot.
D
This
is
basically
all
we
need
to
do
to
define
our
store,
and
in
our
that
part,
you
basically
create
a
new
store
as
a
private
field,
and
now
the
the
magic
is
that
we
hookin
to
the
lifecycle
methods
of
the
other
part,
which
is
called
on
property
changed
which
allows
us
to
update
our
stores
with
the
new
properties
that
are
set
by
the
by
the
user
in
the
in
the
property
pain.
So,
basically,
all
we
need
to
do
is
basically
terrible
store.
Add
an
especially
the
web
parts
store
that
our
properties
change.
D
Anyone
except
the
new
property
path,
which
is
what
did
we
define
here?
So
we
just
defined
the
name
property
and
the
property
path
will
be
named
a
new
value.
We
believe
the
new
value
that
the
user
entered,
and
this
is
basically
how
we
tell
our
store
that
something
change
and
that
you
should
update
it,
and
we
also
do
this
on
in
it
to
load
the
distort
properties
or
the
safe
properties
by
the
user.
D
So
this
is
basically
one
time
setup
for
the
web
part
and
get
yourself
to
clear
all
the
properties
and
then
March
those
properties
that
are
set
on
the
underwear
park.
So
I
guess
the
weapons
clusters
on
in
the
local
storage
of
the
browser
queuing
development,
so
this
gets
loaded
and
on
in
a
distant
chord,
and
then
you
have
two
properties
term,
that's
actually
quite
quite
easy
and
there's
also
like
in
nonreactive
webparts.
There's
another
car
back.
D
D
D
It's
not
okay,
and
now
the
question
basically
is:
how
do
we
get
our
state
that
is
stored
in
our
store
to
our
components
and
they
actually
two
elements
to
that?
The
first
one
is
this
provider
component
that
is
supplied
by
ma.
Pix
react,
which
are
the
react
bindings
from
objects
for
react,
and
the
only
thing
we
need
to
do
here
is
basically
pass
all
ours
subscores
as
properties
to
deserve
provider.
So
we
just
grab
everything
which
is
basically
the
same
as
writing
this
one.
D
So
we
just
want
to
access
all
the
stops
tours,
because
our
stores,
just
a
collection
of
sub
stores
and
our
components,
probably
just
wanna-
have
access
to
a
specific
sub
store,
so
I
spread
this
store
in
Judar
component.
I
could
also
do
something
like
like
this,
and
it
doesn't
really
matter
that
much
and
then
remove
the
rest,
but
I
like
to
spread
all
the
sub
stores.
That's
just
personal
preference,
but
it
still
works.
D
And
then
what
I
like
to
do
is
make
a
difference
between
container
components
which
has
thrown
containers
and
components,
and
the
difference
is
that
container
components
are
basically
is
smart
components.
So
I
will
show
you.
This
is
a
different,
cleaner
and
all
the
containers
are
hooked
up
with
our
global
state.
So
with
our
stores-
and
they
are
responsible
for
fetching
the
data
and
pass
it
through
the
components
which
are
just
dump
components
and
just
present
some
data,
but
they
don't
load
it.
They
don't
do
anything
with
the
data
they
just
presented
to
the
user.
D
D
There's
also
from
the
from
the
react,
bindings
justice,
inject
method
and
that
you
can
use
to
hook
up
this
function
with
our
store
and
then
tell
two-component
what
it
actually
wants.
What
tells
us
not
what
you
want
to
retrieve
so
we
get
like
the
complete
store
or
capacitive
provider,
and,
let
me
say:
okay:
we
want
to
get
our
web
part,
which
is
started
back
hard
as
a
property
into
our
component.
D
It
might
be
a
bit
hard
to
read
in
the
beginning,
because
it's
a
lot
of
functional
stuff,
but
it
works.
You
probably
just
need
to
copy
this
from
there
from
greet
me
with
no
eggs,
but
it
works.
You
can
also
use
like
the
decorator
pattern,
but
it
doesn't
work
for
functional
components
which
disease
so
we'll
probably
get
easier
to
read,
and
another
thing
that
we
need
is
to
add
this
observer
to
our
default
container.
D
D
D
Okay,
so
basically,
what
the
cells
just
lend
us
the
name
that
we
that
we
input
here
and
it
updates
to
feel
directly,
and
we
basically
see
here
that
the
why
one
method
was
called
like
four
times
so
far.
We
input
the
enter
I
get
a
new
update
and
it
basically
says
that
if
I
contain
our
free,
the
brenda
was
called
because
something
changed
in
our.
D
D
The
property
changes
which
might
not
be
an
optimal
thing,
because
if
you
do
a
lot
of
loading
in
your
component
bit
mound
a
lot
of
computation
or
a
lot
of
guessing
calls,
you
do
this
every
time
something
changes
which
is
not
that
performant,
but
because
now
everything
goes
directly
to
the
store
and
the
reg
bindings
update
our
sub
components
that
subscribe
to
those
stores.
We
just
have
to
render
the
rain
the
main
web
part
once
and
everything
works.
So
this
is
quite
a
big
performance.
A
Absolutely
just
a
a
side
comment
from
the
presentation,
and
over
said,
we
were
just
think
that
in
the
room
as
well,
so
this
super
valuable
sample
actually
because
it
shows
the
pattern
and
obviously
Thank
You
Patrick.
It
does
require
the
basic
understanding
of
SPF
X
and
the
react
to
be
able
to
understand
the
value
of
what
you're
actually
showing,
and
you
know
that.
But
but
this
is
so
from
my
perspective
and
that
the
whole
team
perspective.
A
D
Does
make
my
own
a
little
bit
most
likely?
No
I
guess
so?
Yes,
yeah
better.
All
of
you
extra
man
yeah,
I
just
wanna,
show
you
the
direct
stuff
for
ya.
Yes,
that's
exactly
the
same
thing,
but
the
array
redox
handles
the
state
update
is
bit
different,
but
it's
actually
even
better
from
a
developer
perspective
if
you
get
overview
about
your
complete
stadium,
so
I
just
want
to
show
this
and
then
the
console
output
will
be
a
lot
cleaner
and
then
probably
a
bit
easier
to
understand.
D
So
relax
is
a
is
a
more
functional
approach
to
the
whole
state
management
thing,
and
but
a
lot
of
stuff
is
actually
the
same,
so
we
still
create
a
store
which
is
tired
for
our
complete
stay
in
our
my
part.
We
still
have
to
only
render
it
once
and
there's
also
this
kind
of
provider
component
that
doesn't
magic
and
we
tell
what
store
we
want
to
use
for
this
component
and
we
still
hook
up
to
the
lifecycle
methods
of
the
web
part.
D
But
this
time
we
tell
our
store
dispatch,
update
property
or
fly
robert
e
action,
and
I
will
just
show
you
how
this
looks
like
exactly
I'm.
So
those
up
a
property
apply
properties
actually
actually
create
us
that
great
action
that
we
dispatch,
then
in
our
store.
So
that's
like
the
names
that
you
have
to
learn.
If
you
want
to
use
red
ox
so
I
can
creators,
great
actions
and
actions
are
spatula
store
and
the
reducers
which
I
will
come
to
now,
basically
handle
those
actions
and
updates
stayed
in
the
store.
D
We
can
also
define
like
or
what
does
this
like?
Sub
store
look
like,
and
it
also
has
justice
properties
property.
We
can
you
find
initial
state.
This
is
the
default
statement,
application
loads
and
what
I
will
reduce
it
does
is
this
year
we
choose
it
as
a
pure
function
that
takes
a
state
and
connection
and
returns
like
the
new
state
and
it's
a
pure
function,
because
it
shouldn't
modify
the
state
but
create
a
new
state
object
and
return.
D
This
one,
which
gives
you
a
lot
of
nice
stuff
like
easy
testing
and
even
like
time
to
revel,
debugging
and
stuff
like
that.
So
this
is
really
awesome,
but
I
think
I
don't
have
time
to
show
it
today.
So
how
does
this
works?
Well,
as
I
said,
we
could
we
get
action,
and
so
this
is
really
nice
and
typescript,
because
we
can
say:
okay,
I
get
action
which
is
either
update.
D
Property
action
apply
poverty
action
and
then
we
do
a
switch
case
on
the
type
and
typescript
we
do
all
the
hard
stuff
to
actually
give
us
intelligence
for
everything
which
is
really
awesome
so
in
case
of
a
singer
update
property
thing,
which
is
copy
the
state
by
using
a
flick,
design,
empty
object
and
the
state
which
basically
just
copies
the
whole
state,
and
then
we
say
also
copy
over
the
properties
object
by
copying
the
whole
property's
object
and
just
designing
one
field.
I
want
property
with
that
name.
D
Value,
so
this
is
basically
the
same
as
this
one
I
hope
this
is
kinda
understandable,
but
you
get
used
to
those
stuff.
If
you
write
a
lot
of
reduces
anyway
so
for
applied
properties,
you
basically
the
same,
except
that
we
just
copy
to
complete
properties
object
over
those
are
the
two
action
creators
that
I
just
showed
and
those
create
just
a
plain
in
action:
object
which
just
holds
the
type
and
the
payload,
which
is
property
name
and
a
value
or
all
the
properties.
In
the
other
case,
cool
this.
D
Basically
everything
you
need
to
do
so,
it's
it's
more
typing
with
redux,
but
it's
a
lot
less
magic
and
you
basically
have
more
control
or
what
happens.
So
this
is
nicer.
If
you
don't
like
magic
in
your
code
which
I
do
then,
which
is
fire
the
example.
Let
me
get
some
nice
output,
so
I
will
have
another
reactive
apart
and
what
we
see
here.
We
see
how
that
the
action
was
handled
by
the
by
the
store,
and
it
was
the
fly
properties
action.
D
So
this
was
this
happened
on
the
on
in
it
car
back
and
we
see
well
state.
We
had
before-
and
this
was
just
like
an
MP's
property
public-
not
an
empty,
but
name
was
basically
empty
and
our
action
had
this
this
property
subject,
so
the
disabled,
reactive
property,
which
was
additionally
past
to
it,
and
then
our
new
state
is
basically
everything
updated.
D
This
is
really
nice,
because
if
I
now
have
some
input,
we
see
that
for
every
keystroke
I
do.
A
new
update
property
is
invoked
on
new
update
property
actions
dispatched
to
the
store,
and
we
see
that
you
know
but
I
type,
the
value,
changes
and
I
can
see
for
every
action.
What
was
the
state
before
and
after-
and
this
gives
you
a
lot
of
power
if
you
debug
stuff
or
want
to
know
how
something
works
right
and.
D
Yeah,
how
does
this
get
to
the
well
to
the
components?
So
the
components
are
basically
exactly
the
same
as
in
the
mob
weeks.
Example,
they
don't
have
any
logic
at
all.
They
just
take
properties
and
presented
to
the
user,
but
our
container
looks
a
bit
different.
This
is
just
a
redox
version
of
what
we
did
before.
D
So
how
we
looks
works
is
basically,
we
say,
map
staple
crops
which
is
basically
get
me
all
the
stage
and
I
want
to
extract
from
those
global
application
state
like
the
name
and
reactive
property
which
is
stored
in
state
apart
properties,
name
over
them,
and
those
two
values
get
passed
through
the
container
with
the
same
name.
Basically,
and
then
we
render
them,
and
then
we
used
to
connect
method
which
is
defined
in
the
react
bindings
for
we
dogs
give
it
the
the
map,
stage,
props
function
and
our
container
and
it
works.
D
So
that's
basically
automatic
is
to
hook
up
the
state
with
little
container
yeah.
That's
basically,
it
I
was
have
like
another
example,
which
is
some
more,
which
has
some
icing
stuff,
which
actually
makes
it
useful,
I
guess,
except
for
just
doing
properties.
But
I
don't
know
if
I
have
time
for
that.
I.
A
Yeah
we
have.
The
second
aim
account
also
Kira,
because
actually
this
would
be
no
some
time
to.
If
there's
any
question
so
I
know
the
deal
is
try
to
jump
on
the
under
whenever
a
percent.
There
was
a
question
from
bill.
That
is
this.
Like
view
model,
but
not
precisely,
but
it's
separation
of
concerns,
yeah
and
essentially
both
of
these
are
implementations
of
flux.
So
thinking
on
how
to
win
consensually
remain
the
state
yeah.
C
C
D
Elaborate
yet
to
separate
your
state,
your
application
state
from
your
components
that
rendered,
if
you
use
like
component
stage
to
store
your
application
state,
you
basically
need
those
components
to
live
right
because
the
state
is
stored
in
them.
And
what,
if
you
store
your
state
and
your
components,
you
know
separately,
you
can
just
use
another
completely
new
UI
layer
or
whatever
render
that
state
or
just
switch
out
components.
How
we
like,
because
now,
instead
of
a
list,
you
want
to
have
some
tab,
control
or
whatever.
D
C
C
D
Modern
model
and
because
actually
some
components
may
have
stay
on
state
like
let's
say,
for
example,
a
drop-down
control,
and
that
wants
to
store,
if
it
struggled
or
not
right.
So
if
it
has
to
display
like
the
list
of
items
or
just
the
value,
the
selected
value-
and
you
probably
don't
want
to
start
this
information
in
your
application
state
right,
agreed
yeah.
That's
that
isn't
that
way,
faster
control.
D
D
Both
frameworks
are
really
good,
although
I
I
have
some
key
takeaways
they're,
still
from
a
blog
I,
actually
link
the
blog
post
last
time,
so
basically
how
you
should
learn
this
stuff.
It's
like
learn
reactions
that
stayed
first
like
storing
everything
in
components,
and
if
you
use
that
a
lot
you
you
might
find
out
why
it's
not
a
good
idea
to
do
that.
D
Bigger
River,
Park
grows
bigger,
but
I
think
Rapids
are
usually
bit
smaller
in
scope,
so
you
probably
don't
need
to
use
redux
I
prefer
redox
or
mob
weeks
anyway,
because
I
don't
know
I,
just
like
it
more,
but
it's
powerful
preferences
and
but
but
still
to
contain
and
presenter
components
pattern
still
valid
for
both
and
really
really
useful.
Even
if
you
something
else
for
state
management,
splitting
your
components
in
containers
like
smart
components
and
presentation,
components
like
the
dump
ones,
it's
really
good.
A
A
You
can
actually
just
to
steal
the
presentation
for
your
screen
and
we
can
keep
on
chatting
before
we
before
that
starts,
but
like
mentioned,
this
also
requires
some
level
of
an
understanding
already
previous
knowledge
on
client-side
web
parts,
but
super
super
valuable
for
those
who
started
the
client-side
web
development
already
but
Sergei.
So,
let's
switch
to
you
and
get
moving
on
that
one.
E
E
You
know
that
in
order
to
use
SharePoint
rest
api,
you
need
to
authenticate
all
your
quest
and,
while
you're
working
inside
sharepoint
context
is
the
in
pjs
call
from
the
browser.
You
already
have
all
authentication
data
available
and
this
data
usually
them
automatically
by
the
browser.
The
HTTP
requests
like
cookies,
for
example,
alpha
noches
since
are
different,
then
phrenologist.
E
For
for
current,
for
my
current
demo,
I'm
going
to
use
my
own
knowledge
as
model
called
Nantes,
POS
and
I'm
going
to
use
it
in
order
to
to
get
authentication
data,
let
me
show
you
some
really
small
demo
around
nor
these
pills
and
how
to
use
it.
You
see
the
github
give
her
page.
So
actually,
this
small
model
contains
only
one
method
called
get
out.
You
need
to
pass
your
SharePoint
URL
and
some
credential
options
object.
This
credential
options
depends
on
your
authentication
strategy
now.
E
E
I'll
gettin
some
small
demonstration
around
all
these
pills,
so
I'm
getting
bills
the
required.
Now
I
am
I'm
calling
getpos
method
passing
my
local
and
brains,
sharepoint
and
I,
using
ad
FS
commercials.
You
see
my
username,
the
mail
super
strong
password
and
relying
party
and
AD
FS
URL
right
after
that
here.
If
your
promises,
I
am
receiving
some
authentication
and
she
lives.
So
let
me
let
me
run
it
to
make
a
little
bit
bigger,
just
not
indexed
urges
and
we
will
see
the
power
just
received
my
authentication
header,
let's
actually
Fidel's
cookies.
E
E
If
you're
familiar
with
team
teachers.call
company,
you
may
know
that
the
in
pjs
core
uses
the
interfacial
limitation
in
order
to
sound
53
queries
to
sharepoint
and
follow
gents.
The
trick
is
to
replace
global
face
implementation.
There
is
no
jazz
version
now.
Actually
it's
not
another
bloody
big
deal
and
this
can
be
done
pretty
easily.
I
would
say
you
see
this
around
20
lines
of
code,
how
you
can
do
it
from
oh
geez,
I'm
using
a
special
largest
model
called
node
fish.
E
That's
been
to
fish
windows,
go
to
age
limitation
for
largest
I
need
to
sign
some
global
variables.
This
is
required
for
the
mtgs
call
Denzel,
as
I
said
before,
to
override
a
global
dogfish
function.
So
what
I'm
doing
here
I'm
overriding
a
global
fish
and
call
so,
as
I
said
before,
I
need
authentication
data
for
HTTP
request
so
before
before
the
formula
to
request.
I
need
to
get
this
data
using
not
SP
house
elaborate
thread
so
I'm
getting
my
authentication.
He
lives
passing
some
credentials
with
me
with
credentials.
E
This
is
the
same
credentials.
I
show
you
a
few
minutes
before
this,
my
local
on-premise,
a
deaf
as
user,
so
I'm
passing
time,
passing
these
credentials
and
getting
authentication
hitters
cookies
I'm.
Attaching
these
cookies
to
to
my
page
options
right
there
and
now
I'm
ready
to
return.
My
patient
limitation
is
authentication
already
available.
So
basically
that's
it.
That's
all
you
need
two
down
in
order
to
use
in
pjs
core
from
merges
and
now
at
this
part
you
can
use
npg
score.
For
example,
I
am
creating
you.
E
E
So
let
me
also
demonstrate
this
time
using
ATM
scripts
for
the
purpose.
Let
me
play
em
around
built,
so
now
it's
transparent,
typescript
and
actually
running
it.
Then
you
see
my
web
type
of
my
sub
web
title
and
my
list
under
the
sub
web,
so
we
can
just
put
based
in
purposes
we
can
open.
Our
subside
can
just
copy
this
URL
and,
let's
say
I-
want
to
change
this
title
to
something.
E
And
you
see
that
my
Uli's
titleist
animals,
so
so,
basically,
that's
it.
This
is.
This
was
a
small
demonstration
on
how
you
can
integrate
the
mpg
score
into
your
own
RJ's
application
in
this
sample.
I
used
my
my
own,
oh
geez,
model
for
an
addendum
to
the
point
authentication,
but
depending
on
your
needs,
you
may
use
different
approach,
but
approach
form
for
a
verizon
and
global
ethic
object
in
order
to
make
vintage
a
score
to
work
with
node.js
is
pretty
similar.
B
E
E
B
Great,
we
got
a
little
bit
of
time
there,
any
other
questions,
just
general
questions
or
for
Sergei
or
Kevin
on
their
presentations
didn't
want
to
say
great
job
for
both.
You
guys
really
appreciate
it.
I
think
those
are
really
interesting,
really
valuable
for
folks
to
see
some
great
approaches
to
two
different
problems,
but
both
solved
very
cleverly,
so
so
good
stuff,
good
stuff.
Absolutely.
B
Alright,
so
thanks
again
Kevin
and
Sergey,
really
great
stuff
and
then,
as
I
said
before,
if
anybody
has
presentations
they
would
like
to
do
in
the
future.
Please
just
let
us
know
really
welcome
that
from
the
community.
I
think
it's
really
good
stuff,
I,
don't
see
any
other
questions.
Our
next
meeting
I
did
want
to
bring
up.
The
next
meeting
would
actually
be
scheduled
for
November
24th,
which
is
a
holiday
here
in
the
United
States.
So
I
will
not
be
working
so
we're
gonna
go
ahead
and
cancel
that
meeting.
B
So
the
next
meeting
will
now
be
december.
Eight
december
eight.
For
the
next
meeting.
We
will
pop
up
a
slide
on
the
twenty-fourth
to
remind
folks
again
that
the
meeting
was
cancelled,
but
december
eight
would
be
the
next
meeting
for
the
special
interest
group.
So
just
heads
up
there
we
don't
really
have
a
great
way
to
update
the
calendar
item.
So
just
please
make
a
note,
please
remember
december,
eight
for
the
next
meeting,
and
so
for
myself,
for
visa
for
bert
and
for
Sergei
and
Kevin
I
want
to
say
thanks.