You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the bug applicable and reproducable to the latest version of the package and hasn't it been reported before?
Yes, it's still reproducable
What version of Laravel Excel are you using?
3.1.55
What version of Laravel are you using?
10.48.7
What version of PHP are you using?
8.3.8
Describe your issue
When using both SkipsFailures trait and WithChunkReading interface, it seems that only the chunk import instance failures collection is populated, not the original import one, which means it isn't possible to execute a code similar to the one from the documentation:
$import = newUsersImport();
$import->import('users.xlsx');
foreach ($import->failures() as$failure) {
$failure->row(); // row that went wrong$failure->attribute(); // either heading key (if using heading row concern) or column index$failure->errors(); // Actual error messages from Laravel validator$failure->values(); // The values of the row that has failed.
}
In the above example, $import->failures() will always be empty.
Is the bug applicable and reproducable to the latest version of the package and hasn't it been reported before?
What version of Laravel Excel are you using?
3.1.55
What version of Laravel are you using?
10.48.7
What version of PHP are you using?
8.3.8
Describe your issue
When using both
SkipsFailures
trait andWithChunkReading
interface, it seems that only the chunk import instancefailures
collection is populated, not the original import one, which means it isn't possible to execute a code similar to the one from the documentation:In the above example,
$import->failures()
will always be empty.How can the issue be reproduced?
What should be the expected behaviour?
It'd be great to have a way to populate
failures
in the import instance.The text was updated successfully, but these errors were encountered: