1 Commits (388d6e57260fc40bf9ec7e40afb5fb0d1f61e58b)

Author	SHA1	Message	Date
Your Name	c0f29d4a4b	Fix web notifications not loading (#7195) ... Notification status hydration compared item_type strictly against Status::class (App\Models\Status). Rows created before the App\ -> App\Models\ namespace migration store the legacy 'App\Status' morph-map alias, so the comparison failed and favourite/comment/mention notifications came back with no attached status. The web UI filters those out client-side but keeps paginating (response never empty), leaving the infinite-scroll loader spinning forever. - NotificationTransformer + Mastodon NotificationTransformer: match both the legacy alias and the current FQCN when hydrating status. - NotificationService::buildNotification: same alias-aware deleted-item guard. - NotificationService::getMaxPage/getMinPage: filter out unrenderable notifications (status-type without a hydrated status) so the endpoint never returns rows the UI discards, fixing pagination termination; warn on unexpected notification types. - Tests for transformer hydration (legacy + current), renderable filtering, the unexpected-type warning, and pagination termination.	2 weeks ago