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
This is a follow-up to #4359 where we discovered that MysqlImport::runIt() checks for the existence of a file, and this behavior wasn't covered by a test.
This gives us two things to do:
Generate test coverage for:
// Attempt to resolve resource file name from file path.
if (($file_path = \Drupal::service('file_system')->realpath($this->resource->getFilePath(TRUE))) === FALSE) {
return $this->setResultError(sprintf(
'Unable to resolve file name "%s" for resource with identifier "%s".',
$this->resource->getFilePath(TRUE),
$this->resource->getUniqueIdentifier())
);
}
Determine why MysqlImport performs this check on the file, but ImportJob does not. If needed, turn this file check into a separate method on ImportJob and then both subclasses can use it.
The text was updated successfully, but these errors were encountered:
This is a follow-up to #4359 where we discovered that MysqlImport::runIt() checks for the existence of a file, and this behavior wasn't covered by a test.
This gives us two things to do:
MysqlImport
performs this check on the file, butImportJob
does not. If needed, turn this file check into a separate method on ImportJob and then both subclasses can use it.The text was updated successfully, but these errors were encountered: