-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve email notfication migration #602
Conversation
WalkthroughThe changes involve the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
api/app/Console/Commands/EmailNotificationMigration.php (1)
Line range hint
79-90
: Add null checks for notification data fields.The code assumes that
notification_sender
exists in the existing data. Consider adding null checks or default values for all fields to prevent potential issues.Apply this fix:
} else if ($integration->integration_id === 'submission_confirmation' && isset($existingData->notification_subject)) { $integration->integration_id = 'email'; $integration->data = [ 'send_to' => $this->getMentionHtml($integration->form), - 'sender_name' => $existingData->notification_sender, + 'sender_name' => $existingData->notification_sender ?? 'OpnForm', 'subject' => $existingData->notification_subject, - 'email_content' => $existingData->notification_body, - 'include_submission_data' => $existingData->notifications_include_submission, + 'email_content' => $existingData->notification_body ?? '', + 'include_submission_data' => $existingData->notifications_include_submission ?? true, 'include_hidden_fields_submission_data' => false, 'reply_to' => $existingData->confirmation_reply_to ?? null ];
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- api/app/Console/Commands/EmailNotificationMigration.php (3 hunks)
🔇 Additional comments (2)
api/app/Console/Commands/EmailNotificationMigration.php (2)
Line range hint
68-92
: Verify transaction safety for the migration.While the code handles errors and uses chunking, consider wrapping the integration updates in a transaction to ensure data consistency in case of failures.
Let's check if transactions are used elsewhere in similar migrations:
#!/bin/bash # Search for transaction usage in migrations rg -B 2 -A 2 "DB::transaction|->transaction" --type php app/Console/Commands/Consider wrapping the update in a transaction:
public function updateIntegration(FormIntegration $integration) { if (!$integration->form) { return; } + return \DB::transaction(function() use ($integration) { $existingData = $integration->data; // ... existing code ... + }); }
Line range hint
68-78
: Consider validating email addresses before saving.While the logic for handling email integration looks good, it might be worth validating the email addresses in
notification_emails
before saving to ensure they are in the correct format.Let's check if there's any existing email validation in the codebase:
Consider adding email validation:
if ($integration->integration_id === 'email' && isset($existingData->notification_emails)) { + $emails = is_array($existingData->notification_emails) + ? $existingData->notification_emails + : [$existingData->notification_emails]; + foreach ($emails as $email) { + if (!filter_var($email, FILTER_VALIDATE_EMAIL)) { + throw new \InvalidArgumentException("Invalid email format: {$email}"); + } + } $integration->data = [
return $integration->save(); | ||
} | ||
return $integration->save(); | ||
return; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Consider adding logging for audit purposes.
Since this is a one-time migration script, it would be helpful to log successful migrations for audit purposes and troubleshooting.
Consider adding logging:
if ($integration->integration_id === 'email' && isset($existingData->notification_emails)) {
// ... existing code ...
+ $this->info("Migrated email integration {$integration->id} for form {$integration->form_id}");
return $integration->save();
} else if ($integration->integration_id === 'submission_confirmation' && isset($existingData->notification_subject)) {
// ... existing code ...
+ $this->info("Migrated submission confirmation integration {$integration->id} for form {$integration->form_id}");
return $integration->save();
}
+ $this->warn("Skipped integration {$integration->id} - no matching conditions");
return;
Committable suggestion was skipped due to low confidence.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (3)
api/app/Console/Commands/EmailNotificationMigration.php (3)
64-64
: Consider documenting the return type.The method has inconsistent return types (boolean|void). Consider adding a return type declaration and documenting the expected behavior.
- public function updateIntegration(FormIntegration $integration, $isDryRun = false) + public function updateIntegration(FormIntegration $integration, bool $isDryRun = false): ?bool
Line range hint
70-85
: Enhance data validation and dry run logging.The email notification data structure validation could be more robust, and the dry run logging could provide more context.
Consider these improvements:
if ($integration->integration_id === 'email' && isset($existingData->notification_emails)) { + // Validate email format + $emails = is_array($existingData->notification_emails) + ? $existingData->notification_emails + : [$existingData->notification_emails]; + + foreach ($emails as $email) { + if (!filter_var($email, FILTER_VALIDATE_EMAIL)) { + $this->warn("Invalid email format found: {$email}"); + } + } + $newData = [ 'send_to' => $existingData->notification_emails ?? null, 'sender_name' => 'OpnForm', 'subject' => 'New form submission', 'email_content' => 'Hello there 👋 <br>New form submission received.', 'include_submission_data' => true, 'include_hidden_fields_submission_data' => false, 'reply_to' => $existingData->notification_reply_to ?? null ]; if ($isDryRun) { - $this->info('Dry run: Would update integration ' . $integration->id . ' with data: ' . json_encode($newData)); + $this->info("Dry run: Would update email integration {$integration->id} for form {$integration->form_id}"); + $this->line("Current emails: " . json_encode($existingData->notification_emails)); + $this->line("New configuration: " . json_encode($newData, JSON_PRETTY_PRINT)); } else {
Line range hint
86-104
: Standardize return behavior and improve error handling.The method has inconsistent return behavior and could benefit from better error handling.
Consider this refactor:
} elseif ($integration->integration_id === 'submission_confirmation' && isset($existingData->notification_subject)) { $newData = [ 'send_to' => $this->getMentionHtml($integration->form), 'sender_name' => $existingData->notification_sender, 'subject' => $existingData->notification_subject, 'email_content' => $existingData->notification_body, 'include_submission_data' => $existingData->notifications_include_submission, 'include_hidden_fields_submission_data' => false, 'reply_to' => $existingData->confirmation_reply_to ?? null ]; if ($isDryRun) { - $this->info('Dry run: Would update integration ' . $integration->id . ' with data: ' . json_encode($newData)); + $this->info("Dry run: Would update submission confirmation {$integration->id} for form {$integration->form_id}"); + $this->line("New configuration: " . json_encode($newData, JSON_PRETTY_PRINT)); + return true; } else { $integration->integration_id = 'email'; $integration->data = $newData; return $integration->save(); } } - return; + $this->warn("No updates required for integration {$integration->id}"); + return false;
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- api/app/Console/Commands/EmailNotificationMigration.php (5 hunks)
🔇 Additional comments (1)
api/app/Console/Commands/EmailNotificationMigration.php (1)
16-16
: LGTM! Well-documented command option.The dry run option is clearly documented and follows Laravel command conventions.
$isDryRun = $this->option('dry'); | ||
|
||
$query->with('form')->chunk(100, function ($integrations) use ($progressBar, $isDryRun) { | ||
foreach ($integrations as $integration) { | ||
try { | ||
$this->updateIntegration($integration); | ||
$this->updateIntegration($integration, $isDryRun); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Consider adding summary statistics logging.
While error handling is present, it would be helpful to track the overall success/failure rate of the migration.
Add counters and summary logging:
$isDryRun = $this->option('dry');
+ $successCount = 0;
+ $errorCount = 0;
- $query->with('form')->chunk(100, function ($integrations) use ($progressBar, $isDryRun) {
+ $query->with('form')->chunk(100, function ($integrations) use ($progressBar, $isDryRun, &$successCount, &$errorCount) {
foreach ($integrations as $integration) {
try {
$this->updateIntegration($integration, $isDryRun);
+ $successCount++;
} catch (\Exception $e) {
$this->error('Error updating integration ' . $integration->id . '. Error: ' . $e->getMessage());
ray($e);
+ $errorCount++;
}
$progressBar->advance();
}
});
$progressBar->finish();
$this->newLine();
+ $this->info("Migration completed with {$successCount} successful updates and {$errorCount} failures");
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
$isDryRun = $this->option('dry'); | |
$query->with('form')->chunk(100, function ($integrations) use ($progressBar, $isDryRun) { | |
foreach ($integrations as $integration) { | |
try { | |
$this->updateIntegration($integration); | |
$this->updateIntegration($integration, $isDryRun); | |
$isDryRun = $this->option('dry'); | |
$successCount = 0; | |
$errorCount = 0; | |
$query->with('form')->chunk(100, function ($integrations) use ($progressBar, $isDryRun, &$successCount, &$errorCount) { | |
foreach ($integrations as $integration) { | |
try { | |
$this->updateIntegration($integration, $isDryRun); | |
$successCount++; | |
} catch (\Exception $e) { | |
$this->error('Error updating integration ' . $integration->id . '. Error: ' . $e->getMessage()); | |
ray($e); | |
$errorCount++; | |
} | |
$progressBar->advance(); | |
} | |
}); | |
$progressBar->finish(); | |
$this->newLine(); | |
$this->info("Migration completed with {$successCount} successful updates and {$errorCount} failures"); |
Summary by CodeRabbit
New Features
Bug Fixes