taichanne30
5dae5ba3b4
Refactor: DONT REPEAT YOURSELF
...
Note: GroupedNotificationはNotificationの拡張なのでその例外だけ書けば基本的に共通の処理になり複雑な個別の処理は増えにくいと思われる
2024-02-21 04:19:31 +09:00
taichanne30
0cf8946fc7
filterの改善
2024-02-21 03:15:08 +09:00
taichanne30
a4ad66bd5b
Merge branch 'fix-10650' of https://github.com/kakkokari-gtyih/misskey into notification-hide-muting-user
2024-02-21 03:07:42 +09:00
taichan
7c9bacbbd8
use isNotNull
2024-02-20 15:44:13 +09:00
taichan
823b7c3269
Fix condition
2024-02-20 15:40:36 +09:00
taichan
f5ae6630bd
Refactor: 判定部分を共通化
2024-02-20 15:36:30 +09:00
taichan
ff7f7c8835
Fix packGrouped
2024-02-20 15:22:59 +09:00
taichan
3693ce9f00
Improve performance
2024-02-20 15:21:23 +09:00
taichan
ffb853bf2d
Revert "Remove duplication of valid notifier check"
...
This reverts commit 239a6952f7
.
2024-02-20 15:18:26 +09:00
taichan
d53b837994
add filter notification is not null
2024-02-20 15:03:10 +09:00
taichan
239a6952f7
Remove duplication of valid notifier check
2024-02-20 14:57:20 +09:00
taichan
ef65252148
通知作成時にpackしてnullになったらあとの処理をやめる
2024-02-20 14:48:49 +09:00
taichan
b09abb8c59
enhance: Check if notifierId is valid in NotificationEntityService
2024-02-20 14:34:50 +09:00
taichan
45a067788b
Remove unused imports
2024-02-20 14:32:00 +09:00
taichan
1304a9fbb5
Revert API handling
2024-02-20 14:28:28 +09:00
taichan
f0c1c08314
Revert "enhance: 通知が凍結も考慮するようにする"
...
This reverts commit b1e57e571d
.
2024-02-20 14:26:18 +09:00
taichan
19296a0d6b
Fix: typo
2024-02-20 09:57:21 +09:00
taichan
c70c2e7534
Remove unused import
2024-02-20 01:35:14 +09:00
taichan
c21b6d95ae
fix: notifierIdがない通知が消えてしまう問題 (grouped)
2024-02-20 01:30:14 +09:00
taichan
094e10a278
Add tests (通知がミュートを考慮しているかどうか)
2024-02-20 01:28:34 +09:00
taichan
09a9484e4f
fix: notifierIdがない通知が消えてしまう問題
2024-02-20 01:22:21 +09:00
taichan
b1e57e571d
enhance: 通知が凍結も考慮するようにする
2024-02-20 00:52:25 +09:00
taichan
35609b40d3
enhance: 通知がミュートを考慮するようにする
2024-02-20 00:40:33 +09:00
かっこかり
56bbb52a2e
Merge branch 'develop' into fix-10650
2024-02-19 17:53:55 +09:00
anatawa12
1b1046bcdb
fix: syuilo/misskey時代から使用してるサーバーが改変したバージョンだと誤判定される問題 (DB migrationで修正) ( #13389 )
2024-02-19 08:34:31 +09:00
anatawa12
0b636d1bf9
fix: nodeinfoにenableMcaptchaとenableTurnstileが無い ( #13387 )
2024-02-19 08:33:36 +09:00
Cocoa Hoto
b0030d148d
fix: allow moderators see role assigned users; fix #13301 ( #13315 )
2024-02-17 14:41:18 +09:00
syuilo
01de1519dd
fix of 9a70ce8f5e
...
Co-Authored-By: RyotaK <49341894+Ry0taK@users.noreply.github.com>
2024-02-17 14:26:48 +09:00
Acid Chicken (硫酸鶏)
acba96c1d3
feat: license violation protection ( #13285 )
...
* spec(frontend): aboutページにリポジトリ・フィードバックのURLを表示させる
Cherry-picked from MisskeyIO#441
Cherry-picked from MisskeyIO#438
* feat: license violation protection
* build: fix typo
* build: fix typo
* fix: farewell to the static type land
* fix: key typo
* fix: import typo
* fix: properly interpret `prominently`
* docs: add disclaimer
* docs: update CHANGELOG
* chore: add gap
---------
Co-authored-by: まっちゃとーにゅ <17376330+u1-liquid@users.noreply.github.com>
Co-authored-by: syuilo <4439005+syuilo@users.noreply.github.com>
2024-02-17 13:34:50 +09:00
tamaina
9a70ce8f5e
Merge pull request from GHSA-qqrm-9grj-6v32
...
* maybe ok
* fix
* test wip
* ✌️
* fix
* if (res.ok)
* validateContentTypeSetAsJsonLD
* 条件を考慮し直す
* その他の+json接尾辞が付いているメディアタイプも受け容れる
* https://github.com/misskey-dev/misskey-ghsa-qqrm-9grj-6v32/pull/1#discussion_r1490999009
* add `; profile="https://www.w3.org/ns/activitystreams "`
* application/ld+json;
2024-02-17 12:41:19 +09:00
zyoshoka
37959bab1d
refactor(backend): remove/replace deprecated type deps ( #13252 )
2024-02-16 20:09:07 +09:00
かっこかり
7db0971aa9
Merge branch 'develop' into fix-10650
2024-02-16 19:03:59 +09:00
syuilo
f8ac072bc3
fix type
2024-02-16 15:19:55 +09:00
syuilo
7cfe7da73d
fix
2024-02-16 15:09:05 +09:00
syuilo
f55e1ee138
refactor(backend): misc/cacheをシンプルな実装に戻した
2024-02-16 15:07:12 +09:00
MeiMei
cfa573a3a1
リモートユーザーが復活してもキャッシュにより該当ユーザーのActivityが受け入れられないのを修正 Fix #13273 ( #13275 )
...
* リモートユーザーが復活してもキャッシュにより該当ユーザーのActivityが受け入れられないのを修正 Fix #13273
* CHAGELOG
* Use Redis event
---------
Co-authored-by: tamaina <tamaina@hotmail.co.jp>
2024-02-16 14:30:53 +09:00
zyoshoka
40bbae3d6c
fix(backend): add missing schemas and fix incorrect schemas ( #13295 )
...
* fix(backend): add missing schemas and fix incorrect schemas
* fix: ci
* fix: ci (本命)
* fix: run `pnpm build-misskey-js-with-types`
* fix: typos
* fix: role-condition-formula-value contains `id`
* fix: incorrect schema
2024-02-16 14:27:33 +09:00
Kisaragi
147e8f1e3e
feat(backend): likeOnlyなどでハートにフォールバックする際異体字セレクタがない方に揃える ( #13299 )
...
* feat(backend): likeOnlyなどでハートにフォールバックする際異体字セレクタがない方に揃える
close #13298
* Update ReactionService.ts
* chore(backend): prefer single quote for string literal
2024-02-16 14:25:48 +09:00
かっこかり
9ce9c6e2e0
Merge branch 'develop' into fix-10650
2024-02-16 09:48:54 +09:00
tamaina
c1514ce91d
(re) update SPDX-FileCopyrightText
...
Fix #13290
2024-02-13 15:59:27 +00:00
tamaina
311c2172d7
Revert "update SPDX-FileCopyrightText"
...
This reverts commit 9b5aeb76d8
.
2024-02-13 15:50:11 +00:00
dakkar
417bb2d31e
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.
(cherry picked from commit 421f8d49e5d7a8dc3a798cc54716c767df8be3cb)
2024-02-13 15:21:30 +09:00
Acid Chicken (硫酸鶏)
309a943528
perf: omit search for immutable static requests ( #13265 )
...
* perf: omit search for immutable static requests
* perf: also applies to /files
* fix: exclude /proxy
* /files/:key/*を301 redirectに
---------
Co-authored-by: tamaina <tamaina@hotmail.co.jp>
2024-02-13 10:43:06 +09:00
tamaina
32c5c43b6d
enhance: 禁止ワードはリモートノートも対象に ( #13280 )
...
Resolve #13279
2024-02-13 04:54:01 +09:00
syuilo
a1e12c0ec3
Merge branch 'develop' of https://github.com/misskey-dev/misskey into develop
2024-02-12 11:37:55 +09:00
syuilo
9b5aeb76d8
update SPDX-FileCopyrightText
2024-02-12 11:37:45 +09:00
Acid Chicken (硫酸鶏)
3dc095d1c9
feat: provide tarball ( #13260 )
...
* feat: provide tarball
* build: pack on build-assets
* chore: use ignore-walk
* chore: debug
* build: dependencies
2024-02-12 10:02:27 +09:00
syuilo
7fc1d77893
update deps
2024-02-09 17:10:16 +09:00
おさむのひと
614c9a0fc6
fix: 特定文字列を含むノートを投稿できないようにする管理画面用設定項目を追加 ( #13210 )
...
* fix: 特定文字列を含むノートを投稿できないようにする管理画面用設定項目を追加
* Serviceでチェックするように変更
2024-02-09 10:07:18 +09:00
かっこかり
0f7918c51b
refactor(backend): exist -> exists ( #13203 )
...
* refactor(backend): exist -> exists
* fix
2024-02-08 16:04:41 +09:00