►
Description
In this episode we talk through some new pull requests around source endpoints plus see a product import prototype.
B
C
A
A
A
We
have
to
pull
requests
which
already
closed,
is
get
all
sources
and
points
where,
basically,
you
can
just
receive
all
all
sources
which
were
uploaded
to
Magento
by
using
the
search
call
and
it
will
return.
Basically,
all
all
sources
was
that's
a
crucial
here,
but
quite
useful
stuff,
just
to
see
which
data
we
have
and
then
an
expo
request
is
scouring
the
delete
of
the
sources
by
UID,
where
you
can
call
the
delete,
call
of
the
source
and
transfer
the
UID
there
of
this
source
and
it
will
be
removed
from
the
system
from
implementation.
A
Both
of
those
pro
requests,
I
mean
basically
was
quite
standard.
What
we
made
we
change
the
implementation
to
use
the
own
interface
for
each
of
the
comment
which
is
in
this
case
is:
let
me
just
show
quickly
wait:
where
was
it
you
here?
So
when
you
have
a
source
repository
and
when
we
do?
Let's
say:
delete,
we
have
a
common
delete
here
and
then
we
doing
that
and
basically
in
implements
only
one
execute
method
and
the
same
forget
list.
A
He
also
has
one
only
one
execute
method
here
and
then
we
will
get
list
interface
yeah
that
was
was
new
and
changed,
and
those
two
are
already
emerged
and
we
have
three
more
open:
it's
basically
implementing
get
operation
and
save
operations,
I
didn't
validate
them,
I,
guess
guitar.
You
still
have
some
stuff
to
do
so
to
back
merge
your
changes
here
to
resolve
the
conflicts,
as
you
told
me,
for
waiting
for
this
for
those
changes,
but
basically
yeah
they're,
like
forget
operation,.
A
Or
interpretation
sort
of
malakut
operation
it
gets
kids
is
a
source
by
your
UID
sold
rate
exact
source
and
also
the
save
the
source
which
was
already
implemented
before.
But
after
we
extend
in
the
format
with
a
format
and
mapping
feels
it's
required.
Some
additional
modifications
and
yet
was
also
done
so
waiting
just
for
final
changes.
A
The
and
a
year
saw
the
prototype
was
in
keyboard
UI,
that's
a
patently
of
your
film
part,
which
can
be
executed
like
providing
the
UI
for
Magento,
which
can
give
the
admin
user
possibility
to
execute
the
input
without
knowing
basically
the
Magento
API
so
which
will
just
be
similar
to
the
standard.
Magento
API
Magento
import,
UI
castle
will
execute
this
way
with
using
our
endpoints
and
a
synchronously.
But
it's
just
a
very
small
jobs
at
the
moment,
as
I
can
see.
A
That's
basically,
all
from
the
pro
requests
which
we
have
still
open
and
now
I
will
stop
to
share
my
screen,
and
we
have
today
the
Alex
here
who
won't
last
three
months,
two
months
on
the
prototype
for
basically
import.
That's
basically
why
we
are
all
here:
that's
an
import
over
the
products
and
Alex.
Yet
you
as
I
know
you
can
well.
You
want
to
share
with
us
some
results
which
you
have
already.
A
B
B
B
A
Idea,
as
we
discussed
also
was
that
to
provide
like
it's
called
prototype,
I
mean
yeah,
it's
not
a
production
import,
but
already
has
some
like
interfaces
and
implementations
which
will
allow
to
define
more
strict
tasks
to
other
developers
and
to
like
distribute
between
others
like
what
can
be
improved
where
we
have
to
move
in
which
direction,
and
my
idea
was
a
travel
type
to
review
it
next
week,
and
then
we
will
discuss
it
again
and
I
hope.
Maybe
we
will
get
some
support
from
Alex
Parrish,
who
is
here,
I,
see
and
from
Warwick?
A
Who
is
not
here
related
to
architecture
implementation,
but
yeah
I
would
propose
to
do
it
after
I
will
make
a
short
review.
Then
we
can,
with
Alex,
be
like
have
own
ideas
of
them
of
implementing
it,
and
then
we
can
go
like
spread
it
around
and
make
a
discussion
about
this.
That's
an
idea
already
yeah
yeah.
B
Input
field
started
from
operate,
endpoint
inputs
or
CSC.
In
my
case,
they
have
first
type
format
which
currently
not
use
it
and
have
coded
in,
but
show
you
later,
my
pink
I
think
it's
actually
will
help
to
to
parse
data
from
some
source,
XML
or
JSON,
and
write
to
another
storage
like
magenta,
restore
XML
or
another
is.
B
It's
pointed
to
the
import
start,
execute
method
which
get
tools
by
you
idea
get
reader
from
Liverpool.
In
our
case,
it
will
it's.
Yes,
he
reader
from
input,
Silesia,
see
I
actually
implemented.
Cse
in
reader
and
patch
was
over
in
the
parade
model,
because
we
have
a
lot
of
interfaces
and
implementation
in
base
model,
so
I
proposed
to
made
implementation
for
CSV
or
JSON
in
separated
more
models.
B
B
My
pink
rebuilt
item
building
item
in
a
case
of
magenta
rest
API.
We
need
to
get
JSON,
I,
don't
know.
For
now.
What
will
be
the
best
approach
to
who
which
object
we
need
to
set
for
magenta
rest,
tolerates
implementation,
I
decided
to
that
just
press
on
string
and
the
built
item
he'd
get
his
own
preference
over.
It
said
by
my
bank
Tom
value
for
dress
on
node
and
tightened
by
data,
its
rest
on
stink.
So
it's
prepared
item
four
percent
into
magenta
in
case
of
other
storage,
I.
C
B
B
B
A
I
would
basically
just
put
it
as
a
note
if
we
basically
need
this
I
mean
if
you
should
give
a
possibility
to
define
a
type
import
or
we
just
telling
it
will
be
always
Pollock
import,
but
I
get
at
some
point
to
discuss.
That's
okay
and
another
question:
where
did
you
put
the
token
like
authorization,
stuff.
B
Tolkien
and
after
ization
stuff,
I
use
deployment
config
and
it's
in
V
PHP
file.
So
now
I
have
not
import
service.
I
will
add
this
information
to
the
poor
request,
so
you
can
also
use
this
ref
URL
and
integration.
Token
yeah
horribly
I,
using
this
way,
because
if
you
can't
use
some
store
config
as
I
know,
because
it's
the
pent
of
store
manager,
which
we
cannot
use
or
now
I.
A
Saw
some
architectural
pull
request
against
some
long
time
ago,
just
we'll
just
an
article
about
how
the
manolito
of
magenta
will
communicate
with
the
services
but
as
I
understand
it's
not
defined
at
all.
Yet
they
would
way.
Oh
yeah,
that's
a
good
way
like
to
pull
it.
The
Carleton
environment,
PHP
and
you'll
see
later
how
it
will
be
resolved.
Yeah.
A
A
Sounds
like
not
good,
then
yeah,
I!
Guess
then
for
today.
That's
all
thanks!
Everybody
to
join
in.
We
will
keep
you
updated
related
to
the
architectural
decisions
and
how
we
will
proceed.
Then
I'll
try
to
review
it
and
I
guess
we
will
define
some
new
stories
where
we
can
proceed
with
the
implementation.