►
Description
Recording of the import/export weekly call from the 2nd of July 2018.
This project focuses on the https://github.com/magento-engcom/import-export-improvements repository with the aim to provide some key bug fixes in the 2.3 release of Magento 2.
If you would like to get involved in the project please see the github issues or contact the Magento Community Engineering team for more information.
A
Right,
okay,
cool,
so
this
is
the
an
employee
at
work.
Weakling
I'm
joined
by
constant
and
yeah
we're
gonna
gonna
highlight
a
few
things
because
we've
had
in
the
last
two
weeks,
we've
had
quite
a
lot
of
cool
requests
come
in
and
we
have
fortunately
not
had
a
meeting
for
a
while,
so
I
thought
I
would
give
him
an
update
yeah.
A
So
we
need
to
double
check
that
and
we've
also
had
a
pull
request
in
the
last
couple
of
days
and
from
Ty,
and
he
has
improved
some
error
messages
which
I
think
is
pretty
pretty
useful
in
the
import.
So
we
will
talk
through
that,
so
how
about
add
cast-
and
we
start
with
your
requests.
So
let's
start
with
this
one.
Yeah
yeah.
B
B
The
store
ID
is
not
set
on
this
connection
and
core
code
will
set
it
to
one
to
the
idea
of
the
store
one
if
we
don't
set
it
otherwise
and
I
think
even
in
the
original
issue.
I
one
commented
that
he
did
it
this
way,
but
some
tests
fail
and
I
have
to
save.
You
and
I
have
not
yet
managed
to
run
functional
tests
on
my
local
system,
but
I
looked
at
the
code
and
the
test
sees
file
and
that's
the
solution.
My
solution,
yeah.
B
B
This
seems
to
be
I,
don't
know
intended
behavior
or
or
it
was
just
that
the
cat
I
think
the
test
was
written
to
reflect
the
code
and
maybe
not
the
other
way
around
and
yeah.
The
test
won't
fail
if
I
change
the
to
admin
to
address
the
category
and
part
of
the
issue
was
that
they
want
to
address
the
category
with
the
admin
name,
reasonable
and
I
think
it
was
like
that
in
magenta
one
as
well.
A
A
The
other
thing
of
note:
is
it
probably
a
good
option
too,
to
do
a
documentation
change
with
this
one
as
well,
since
we're
changing
it,
and
so,
when
this
gets
processed
or
during
the
processing
point,
I
will
probably
also
talk
with
the
dev
docs
team,
or
maybe
the
dev
docs
team.
For
this
to
talk
about
how
the
best
way
it
would
be
to
demonstrate
this
or
a
board
to
document
that
you
alright
and
the
next
one
is
the
empty
validation
right.
Yeah.
B
A
B
A
B
A
A
A
B
A
A
A
With
these
changes,
but
I
want
again
just
to
get
the
the
core
core
architectures
to
have
a
look
at
it,
especially
because
we
are
adding
in
some
new
classes
and
interfaces.
So
I
just
wanted
to
double
check
that
that's
okay
and
buddies
come
across
some
tests
as
well.
So
I
think
it
should
be,
should
be
good,
but
I
want
to
pass
that
on
to
them.
A
There
are
three
new
checks
that
the
HP
code,
if
the
edge
because
doesn't
exist,
it's
not
in
the
global
scope
and
also
if
it
is
not
a
select
type
and
because,
in
that
case,
you
can't
use
them
for
configurable
options,
also
making
sure
that
the
attribute
is
super
as
well
and
checking
the
it's
got
valid
options
yeah.
There
are
a
few
things
that
I
would
like
to
update
in
this
pull
request.
A
So
I
will
just
message
the
contributor,
with
my
feedback
of
this,
but
again
everything
in
itself
looks,
looks
relatively
okay
and
it
is
clearer
as
to
what
the
validation
is
doing.
It
also
helps
the
user
with
when
the
an
admin
user
is
using
the
username
port.
So
I
think
this
is
a
good
change.
We
just
need
to
make
sure
that
everything
is
everything
is
clean
and
to
standard
and
then
I
think
that
will
be
fun
all
right
other
than
that
I.
Don't
think
that
is
yeah
I,
don't
think.
There's
much
more.
A
Is
it
also
helps
to
clarify
what's
going
on
as
well
in
terms
of
validation,
points
and
stuff,
so
I'm
happy
with
how
that's
going
yeah
well
than
that?
I
think
that's
pretty
much
it
for
today,
and
so
thank
you
for
joining
and
yeah
keep
up
today
in
the
slack
Channel,
and
if
you
have
anything
you
need
from
either
me
or
anyone
else
feel
free
to
drop
a
drop.
A
message
in
there.