►
Description
- Base Async Import Endpoint module implementation for Async Import by Alexander Lyzun- https://github.com/magento/async-import/pull/29
- Basic LocalPathProcessor created by Stepan Furman - https://github.com/comwrap/async-import/pull/1
A
B
B
B
Here
is
it.
It
looks
like
the
one
import
and
what
it's
doing
it's
the
idea
that
it
has
to
take
the
file
and
place
it
on
someplace
on
there
on
the
server.
But
this
current
pull
request
is
not
implementing
any
file
uploads,
it's
only
delivers
the
interfaces,
for
that
is
deliver
the
Web
API
endpoint.
Also,
what
was
done
is
it
was
done,
processors,
pull
that
source
processor
pool.
Why
are
we
defining
the
import
type,
so
we
have
sold
a
local
pass.
B
B
So
yeah
that's
an
example
of
the
old
API
call,
so
we're
doing
the
post
called
forest
import
with
such
body
as
I
showed
you
I
have
here,
the
the
import
type
is
local
pet
and
there
is
the
dis
parameter,
which
defines
the
input
type
and
when
I
send
it
is,
will
return
me.
Currently
it's
empty.
It's
not
regeneration,
because,
as
I
said,
there
is
no
implementation
for
for
this
processor
I
guess
it's
only
return.
B
B
B
A
That
or
get
the
processor
from
both
the
scope
and
run
the
protest,
support
yeah.
You
can
see
it
as
proxy
and,
first
of
all
in
process
a
lot
function
without
validation
source.
Here
we
check
if
T
this
valid
existing
system
and
it's
readable
and
then
I
inject
your
source
type
validator.
So
in
this
validator
we
able
first
of
all
check
that
we
match
allowed
maintains
and
with
this
file,
so
the
allowed
mym
times
we
can
at
your
right
in
as
argument
to
this
validator.
So
right
now
we
show
only
CSV.
A
A
A
Yeah,
so
we
save
this
in
the
database,
then
fuel
responsibility,
the
source,
Eddie
and
sir
status
and
return.
Ok
and
now
I'll
try
this.
So
we
felt
this.
This
file
I
place
this
in
the
water
you're
like
testing
suite,
and
it
woke
up
us
and
CSV
first
type,
so
sandy
return,
source
type
source,
ID
status,
uploaded
and
now
errors.
You
can
see.
So
we
go
to
the
import
service
source
table
database
and
you
can
see
that
it
does
is
uploaded.
A
Csv
local
I'll
send
the
path
to
the
file
that
was
uploaded.
So
we
also
can
check
that
uploaded
to
the
VAR
import
right
now,
but
now
I
decided
that
we
can't
we
can
discuss
it
later,
which
we
reach
your
place.
We,
you
should
choose
for
this,
but
right
now
it's
in
work
were
CSV
so
and
it
returns
to
it
returns
such
an
answer.
So
that's
all
I
will
somebody
have
a
question.
B
You
looks
nice
no
I
wanted
to
us
join
with
the
magenta
guys
related
to
the
statuses
I
mentioned
that,
let's
say
any
bulk:
a
syncope
I
use,
integers
and
statuses,
and
then
a
developer
have
to
dig
deep
to
find
out
what
does
it
mean
or
either
the
documentation?
Others
like
some
best
practices,
should
we
use
also
in
integers,
or
we
can
define
like
like
we
made
before
those
texts,
one
like
uploaded,
completed,
failed
and
so
on.
D
C
Text
or
it
should
be
complex
value,
which
is
text
and
ID,
depends
on
your
use
case
like
if
you
believe
that
you
will
need
ID.
So
you
get
something
and
then
you
have
to
submit
a
customer
choice
include
an
ID,
then
probably
need
object.
If
you
do
get
and
your
usual
use
cases
just
display
label,
then
you
need
to
return
just
label,
but
otherwise
you
will
have
to
do
like
extra
hole
or
you
have
to
keep
some
mapping
on
your
client.
A
B
You
my
idea
that,
because
this
poll
request
was
done
in
a
in
a
cover-up,
River
repository
because
we
had
those
base
module,
implemented,
I
would
say
the
good
idea
will
be
that
we
can
review
my
full
request
and
merge
it
to
this
repo
and
after
that,
I
guess.
Step
on
you
can
just
change
the
destination
of
your
request
and
then
deliver
the
pull
request
in
the
main
asking
for
you.
D
C
Yeah,
just
just
to
show
that
the
whole
sequence
of
actions
is
possible.
That
is
compatible
and
let's
say
you
don't
end
up
in
situation
when
you
do
one
request
in
return
to
Sampson
and
then
for
subsequent
requests.
You
need
some
other
data
which
you
don't
have,
but
so
when
we,
the
problem
is
one
will
do
this
independent
implementations
for
each
request.
You
may
just
end
up
with
incompatible
requests
and
then
you
have
to
fix
them.
So,
ideally,
we
should
have
the
whole
flow
described
before
we
even
implemented
like
in
form
of
vapor
request,
just
response.
B
B
B
C
And
then
it
will
be
also
nice.
If
we
can
just
somehow
say
say
you
have
flow
and
form
of
table,
for
example,
then,
across
each
of
this
requests
you
can
say
hey
this
one
is
done
just
check
mark
and
then
you
can
see
the
whole
picture
that
to
complete
the
whole
flow,
we
need
to
say
five
requests.
Three
of
them
are
done
and
up
one
more
left
and.