Skip to content
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

3.12.1 Release + don't try to backfill notification sender ids after username changes #176

Merged
merged 2 commits into from
May 30, 2024

Conversation

lugehorsam
Copy link
Contributor

@lugehorsam lugehorsam commented May 30, 2024

If a user changes their account username, their old records for tournaments, notifications etc., won't be updated to reflect the new username.

To mitigate this, upon listing records, we automatically compare the record username to the session username and if they differ, we assume it's because of a username change and correct the record username to the session username: #148

However, for notifications, the sender id can differ from the user ID simply by being from another user. So we just don't have a way to know if the user sent it to themselves but with an older username, or if it was sent to them from another user.

@lugehorsam lugehorsam requested a review from novabyte May 30, 2024 16:35
@lugehorsam lugehorsam changed the title don't try to backfill notification sender ids after username changes 3.12.1 + don't try to backfill notification sender ids after username changes May 30, 2024
@lugehorsam lugehorsam changed the title 3.12.1 + don't try to backfill notification sender ids after username changes 3.12.1 Release + don't try to backfill notification sender ids after username changes May 30, 2024
@lugehorsam lugehorsam merged commit c277826 into master May 30, 2024
1 of 2 checks passed
@lugehorsam lugehorsam deleted the luke/notifs-senderid branch May 30, 2024 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants