mirror of
https://activitypub.software/TransFem-org/Sharkey
synced 2024-09-29 19:34:30 +00:00
421f8d49e5
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. |
||
|---|---|---|
| .. | ||
| .vscode | ||
| assets | ||
| migration | ||
| src | ||
| test | ||
| test-server | ||
| .eslintignore | ||
| .eslintrc.cjs | ||
| .madgerc | ||
| .swcrc | ||
| check_connect.js | ||
| generate_api_json.js | ||
| jest.config.cjs | ||
| jest.config.e2e.cjs | ||
| jest.config.unit.cjs | ||
| jsconfig.json | ||
| ormconfig.js | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| watch.mjs | ||
Misskey Backend
