Skip to content

fix: migrate defaultReminder properly - #8818

Open
SebastianKrupinski wants to merge 1 commit into
mainfrom
fix/migrate-default-reminder-properly
Open

fix: migrate defaultReminder properly#8818
SebastianKrupinski wants to merge 1 commit into
mainfrom
fix/migrate-default-reminder-properly

Conversation

@SebastianKrupinski

Copy link
Copy Markdown
Contributor

Summary

  • added a migration to migrate the legacy "defaultReminder" user preference
  • removed "defaultReminder" from back end code
  • removed "defaultReminder" from front end code

@codecov

codecov Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/utils/alarms.js 0.00% 0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
$result = $qb->executeQuery();

$migrated = 0;
while ($row = $result->fetch()) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No chunking?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey!

So in the current design we updated the preferences for each user one by one. Therefore I was just pulling one record at a time.

I thought about a chunked bulk update, but could decide on a deceive way to handle per-existing "defaultReminderPartDay" and "defaultReminderPartDay"

Maybe, I should revisit the idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews

Projects

Status: 🏗️ In progress

Development

Successfully merging this pull request may close these issues.

2 participants