Previously, whenever a user accepted an invitation to a Party or Group Plan, the inviting user would receive a GROUP_INVITE_ACCEPTED notification. This notification was not displayed on the client, and thus it was possible for a user to continue to accumulate junk data in this array over time.
Now:
GROUP_INVITE_ACCEPTED notifications are no longer posted to the user in these flows.
We no longer check for GROUP_INVITE_ACCEPTED notifications in related tests.
A migration has been created to remove extant GROUP_INVITE_ACCEPTED notifications from affected users.
For now, GROUP_INVITE_ACCEPTED remains as an enum in the user model notifications property. We shouldn't remove this until the migration has been run over all users. Once no more such notifications remain in the database, we can delete the enum.
Fixes #10752
Previously, whenever a user accepted an invitation to a Party or Group Plan, the inviting user would receive a GROUP_INVITE_ACCEPTED notification. This notification was not displayed on the client, and thus it was possible for a user to continue to accumulate junk data in this array over time.
Now:
For now, GROUP_INVITE_ACCEPTED remains as an enum in the user model
notificationsproperty. We shouldn't remove this until the migration has been run over all users. Once no more such notifications remain in the database, we can delete the enum.