egirlskey/packages/backend
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
..
.vscode
assets upd: add misskey icon to font 2023-12-07 01:48:57 +01:00
migration merge: upstream 2024-02-03 20:19:44 +01:00
src Never return broken notifications #409 2024-02-11 12:25:50 +00:00
test chore: change sfm registry and name 2024-02-03 15:01:09 +01:00
test-server enhance(backend): テストの高速化 (#12939) 2024-01-08 17:43:52 +09:00
.eslintignore
.eslintrc.cjs
.madgerc
.swcrc fix swcrc 2023-12-14 11:35:17 +09:00
check_connect.js
generate_api_json.js fix: api-docが開けない問題を修正 (#13132) 2024-02-02 12:47:07 +09:00
jest.config.cjs enhance(backend): テストの高速化 (#12939) 2024-01-08 17:43:52 +09:00
jest.config.e2e.cjs enhance(backend): テストの高速化 (#12939) 2024-01-08 17:43:52 +09:00
jest.config.unit.cjs enhance(backend): テストの高速化 (#12939) 2024-01-08 17:43:52 +09:00
jsconfig.json
ormconfig.js
package.json merge: upstream 2024-02-03 20:19:44 +01:00
README.md
tsconfig.json
watch.mjs

Misskey Backend