►
Description
In this episode we get a general project update as well as a discussion on open PRs from Alex
A
A
If
talked
about
the
import,
yeah
I
made
a
presentation
they
are
related
to.
The
import
service
was
a
lot
of
interest,
but,
as
usual
I
see
the
same
faces
here,
yeah
so
from
a
technical
side.
Last
week,
yeah
last
week
there
was
a
guy
in
a
channel
to
discover
the
a
synchronous,
API
back,
which
is
quite
was
quite
big
part
related
to
the
import
by
using
the
stores,
so
I
just
won't
show
the
pull
request,
which
Alex
was
also
here
made
last
week,
I
even
wasn't
this
week
when
it
was
completed.
A
So
yeah
the
issue
was
that
store
was
not
transferred
if
you
using
the
bulk
API,
which
is
quite
logically,
let's
have
to
be
transferred,
but
yeah,
it's
not
it's
not
supported.
It
was
not
supported
by
citrus
operations
that
when
you,
even
if
you
using
the
source
when
you
post
in
the
request
and
the
message,
is
sent
arriving
in
queue,
there
was
no
store
transferred
to
the
revenue
and
then
it's
not
pulled,
then
the
consumers
as
they
executed
it.
So
yeah
this
pull
request
is
completed.
A
It
will
be
accepted.
That's
good!
That's
a
good
news,
not
so
good
news
that
it
will
not
go
into
three
two.
It
will
only
go
into
three
stream,
but
again
you
knew
good
news
that
I
do
will
deliver
it
like
a
page
and
it
could
be
installed
separately
to
provide
the
fix
for
the
developers
and
merchants
who
will
use
API
I
need
this
solution
works
before
two
three
three
will
come
out:
yeah.
That's
one.
A
We
still
have
that
still
on
my
side,
I
had
no
time
because
of
the
event
to
check
the
implementation
of
the
input.
I
know
Alex
already
working
on
a
like.
He
basically
working
with
our
client,
who
has
the
case
and
well
we're
gonna
use
it,
and
we
will
share
best
practices
somewhere
and
maybe
next
or
over
next
meeting,
how
we
used
it,
and
we
have
something
else
for
today.
Oh
yeah
Marlin
Marlin
basically
wanted
to
proceed
with
ready
storage.
A
Yeah
we
headed
to
discussion
also
last
week,
was
born
and
Alex
related
to
related.
If
you
need
a
framework,
if
you
don't
need
a
framework,
so
basically
we
don't
need
a
frame
and
currently
and
then
idea,
Marland
and
that's
for
you
that
we
will
implement
already
storage
in
a
current
asynchronous
operation
implementation.
A
Just
basically
don't
put
it
in
the
same
modules.
You
can
make
a
new
model
which
called
Magento
essentials,
operation,
Redis,
already
storage
and
implement
functionality,
resource
which
is
required
by
our
park.
Api
in
this
module.
So
and
if
it's
like
enabled
it
will
replace
the
database
for
finality
if
it's
used
and
if
not
then
database
will
get
the
default
one
yeah,
that's
the
plan.
A
A
C
I'm
just
thinking
it
might
be
a
good
idea
from
a
visibility
point
of
view
and
if
you've
got
a
patch
available
for
older
versions
to
have
an
issue
someplace.
So
if
someone
searches
for
it
and
finds
it,
they
can
find
the
issue
the
pull
request,
the
fact
it's
merged.
And
then,
if
you
have
a
patch
that
can
be
applied
by
a
composer
or
something
like
that,
then
they
could
also
apply
that
okay.