Warning messages appear when the CSV's header are not following the suggested headers

Uploading a new patch to handle warning messages.

Uploading a new and improved patch to handle undefined array keys warning messages.

+++ b/src/Form/MigrateRedirectForm.php
@@ -171,6 +171,19 @@ my-source-path,https://example.com,und,302',
+          $csvHtml = t('Header line shoud follow the following labels: source,destination,language,status_code');

t() calls should be avoided in classes, use \Drupal\Core\StringTranslation\StringTranslationTrait and $this->t() instead

Marking as needs review.

I have the following questions...

1. +++ b/src/Form/MigrateRedirectForm.php
   @@ -171,6 +171,19 @@ my-source-path,https://example.com,und,302',
   +          $file->delete();
   

   Do we need to delete the file during validation when it doesn't contain the correct CSV header row?

2. +++ b/src/Form/MigrateRedirectForm.php
   @@ -171,6 +171,19 @@ my-source-path,https://example.com,und,302',
   +          break;
   

   Should we return rather than break here?

I note that the class is already using t() calls and doesn't use \Drupal\Core\StringTranslation\StringTranslationTrait and $this->t() instead. This is probably something to address in a separate issue I suppose.

Thank you for the patch @meralvingrita24.

Patch committed including some of the suggestions added by @chOP.

Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.