Scrum4Me/components/notifications/notifications-bridge.tsx
Madhura68 4d2e4b0b4b fix: drop \{ not: null }\ filters — Prisma 7 rejects them at runtime
PrismaClientValidationError ('Argument \`not\` must not be null') hit at
runtime when notifications-bridge mounted post-M12 schema change.
Although StringNullableFilter typings allow \`not: null\`, the v7 query
engine rejects it.

Removed the WHERE-side filter in 3 places — null-narrowing already
happens client-side via flatMap / Boolean filter:
- components/notifications/notifications-bridge.tsx
- app/api/realtime/notifications/route.ts
- lib/insights/verify-stats.ts (task_id filter)

Idea-questions / idea-jobs will be routed via separate channels in
T-502 + T-507; for now, story-question + task-job paths simply ignore
NULL rows in their post-fetch mapping.

Tests: 479/479 green; tsc clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 19:44:48 +02:00

69 lines
2.3 KiB
TypeScript

// ST-1105: Mount-component voor de notifications-realtime hook (M11).
//
// Server Component dat de initial open-questions fetch't met
// productAccessFilter en doorgeeft aan een minimal client-island; client opent
// daarna de SSE-stream voor live updates.
import { prisma } from '@/lib/prisma'
import { productAccessFilter } from '@/lib/product-access'
import { NotificationsRealtimeMount } from './notifications-realtime-mount'
import type { NotificationQuestion } from '@/stores/notifications-store'
interface NotificationsBridgeProps {
userId: string
}
export async function NotificationsBridge({ userId }: NotificationsBridgeProps) {
const products = await prisma.product.findMany({
where: { archived: false, ...productAccessFilter(userId) },
select: { id: true },
})
const productIds = products.map((p) => p.id)
const openQuestions =
productIds.length === 0
? []
: await prisma.claudeQuestion.findMany({
where: {
status: 'open',
expires_at: { gt: new Date() },
product_id: { in: productIds },
// Skip idea-questions (story_id NULL): they have a separate
// realtime channel and aren't shown in this product-scoped bell.
// Narrowing happens in the flatMap below — Prisma 7 rejects
// `story_id: { not: null }` at runtime.
},
orderBy: { created_at: 'desc' },
take: 100,
select: {
id: true,
product_id: true,
story_id: true,
task_id: true,
question: true,
options: true,
created_at: true,
expires_at: true,
story: { select: { code: true, title: true, assignee_id: true } },
},
})
const initial: NotificationQuestion[] = openQuestions.flatMap((q) => {
if (!q.story || q.story_id === null) return []
return [{
id: q.id,
product_id: q.product_id,
story_id: q.story_id,
task_id: q.task_id,
story_code: q.story.code,
story_title: q.story.title,
assignee_id: q.story.assignee_id,
question: q.question,
options: Array.isArray(q.options) ? (q.options as string[]) : null,
created_at: q.created_at.toISOString(),
expires_at: q.expires_at.toISOString(),
}]
})
return <NotificationsRealtimeMount initial={initial} />
}