Sharkey/packages
dakkar 421f8d49e5 Never return broken notifications #409
Since notifications are stored in Redis, we can't expect relational
integrity: deleting a user will *not* delete notifications that
mention it.

But if we return notifications with missing bits (a `follow` without a
`user`, for example), the frontend will get very confused and throw an
exception while trying to render them.

This change makes sure we never expose those broken notifications. For
uniformity, I've applied the same logic to notes and roles mentioned
in notifications, even if nobody reported breakage in those cases.

Tested by creating a few types of notifications with a `notifierId`,
then deleting their user.
2024-02-11 12:25:50 +00:00
..
backend Never return broken notifications #409 2024-02-11 12:25:50 +00:00
frontend merge: fix: Update l-sushi.json5 to ensure the hashtag colour matches the main accent colour (!406) 2024-02-09 17:45:22 +00:00
megalodon add: Bubble timeline 2023-12-04 02:10:51 +01:00
misskey-bubble-game fix(dev): pnpm devで依存関係更新が一部反映されない (#13091) 2024-01-27 09:18:09 +09:00
misskey-js merge: upstream 2024-02-03 20:19:44 +01:00
misskey-reversi fix(dev): pnpm devで依存関係更新が一部反映されない (#13091) 2024-01-27 09:18:09 +09:00
shared chore: use @misskey-dev/eslint-plugin (#12860) 2023-12-31 15:26:57 +09:00
sw merge: upstream 2024-01-22 19:58:43 +01:00
meta.json refactoring 2021-11-12 02:02:25 +09:00