►
From YouTube: Core dev call #37
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).
A
B
B
Yeah,
the
pull
request
is,
is
ready
right
now
on
the
status
go
and
it
is
also
ready
in
stock
slab.
It
could
be
tested,
basically
what
I've
done.
I've
created
a
new
service
and
I've
connected
the
events
that
wallet
triggers
with
the
this
service
and
when
a
new
event
on
the
wallet
is
called.
I
check
if
this
event
has
some
useful
information
for
a
local
notification.
B
If,
yes,
then
I
a
notification
and
send
an
event
to
status
react,
and
this
event
includes
inside
all
the
information
needed
to
build
a
notification
and
based
on
this
information,
the
status
drag,
decides
how
to
show
a
notification
on
ios
and
on
android,
because
there
are
different
native
calls.
It
will
be
based
on
on
json.
It
will
generate
all
notifications,
also,
I've
created
a
table
which
will
store
all
the
subscriptions
to
the
notifications
right
now.
B
B
B
Currently
we
do
everything
in
java.
So
when
an
event
in
chat
happens,
we
build
a
notification
in
we
check
the
event
in
java
and
create
an
education
from
it,
because
of
that
all
the
localizations
should
be
also
available
in
java,
and
we
don't
have
access
to
status
react
at
all,
but
the
approach
that
I
used
right
now
is
to
create
a
react
native
headless,
javascript
task.
B
What
does
it
mean?
It
means
that
we
can
call
from
java
when
something
a
new
event
happens.
We
can
call
a
new
event.
This
new
event
will
start
a
javascript
engine
and
we'll
execute
all
javascript
code
there.
So,
basically
we
can
use
our
closure
script
code
in
this
task.
So
basically,
when
a
new
notifications,
a
new
notification,
came,
I
trigger
this
task.
This
task
starts.
Javascript
builds
the
all
the
context
for
the
notification
in
the
current
transactions.
We
need
localization
for
strings
and
we
also
use
the
logos
for
the
tokens.
B
So
basically,
if
you
receive
an
status
token,
you
will
see
the
logo
of
status
talking
in
the
push
notification.
All
this
information
is
created
in
status,
react
in
the
javascript
part,
then
it
generates
json,
and
this
json
is
pushed
back
to
trigger
the
actual
platform
notification.
B
B
C
Okay,
okay,
you've,
I
I
noticed
you've
got
a
question
on
the
pr,
so
this
is
on
whether
or
not
I
have
a
background
service
running.
So
I
I
looked
at
this
on
friday,
but
I
didn't
know
the
answer
to
this
question,
but
it
seems
like
is:
is
this
something
that
is
required.
B
Well,
yeah,
I
can
we
better
explain
what
it
do
does
right
now
when
the
app
is
in
foreground,
so
you
look
at
it.
B
B
So
if
we
want
to
have
the
notification
for
the
transaction,
then
it
means
that
even
if
the
app
is
in
background,
we
need
to
watch
for
them.
So
basically
my
concern
here,
I
just
disabled
this
code,
but
I
think
it
will
be
better
to
keep
it
in.
For
example,
if
a
user
disables
the
notifications,
then
it
means
that
we
don't
need
to
watch
also
the
wallets.
So
I
think
in
a
ideal
case,
we
need
to
check
here.
If
the
user
is
subscribed
to
wallet
transactions,
then
we
don't
disable
this
service.
B
C
B
Yeah,
the
idea
is
that
I
I'm
not
sure
how
to
stop
it,
because
it
means
that
we
need
to
do
a
request
into
the
database
to
check
if
the
condition
is
enabled,
and
it
means
that
in
this
place
we
will
need
to
also
add
select
from
database
and
I'm
not
sure
how
to
approach
this,
because
we
don't
have
such
cases
here
in
in
this
part
of.