From ef4e8bf353a9f1df17019dc4bb935045f33da1f4 Mon Sep 17 00:00:00 2001
From: Akarshan <akarshan@menlo.ai>
Date: Thu, 30 Oct 2025 12:36:18 +0530
Subject: [PATCH] refactor: allow nullable metadata in MessageMetadataDialog

The metadata prop was previously required, but callers sometimes pass
null or undefined. Updating the type to allow null/undefined prevents
runtime errors and simplifies usage.
---
 web-app/src/containers/dialogs/MessageMetadataDialog.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/web-app/src/containers/dialogs/MessageMetadataDialog.tsx b/web-app/src/containers/dialogs/MessageMetadataDialog.tsx
index 429c7c4b5..4df87b439 100644
--- a/web-app/src/containers/dialogs/MessageMetadataDialog.tsx
+++ b/web-app/src/containers/dialogs/MessageMetadataDialog.tsx
@@ -58,7 +58,7 @@ interface MessageMetadata {
 }
 
 interface MessageMetadataDialogProps {
-  metadata: MessageMetadata // Use the specific interface
+  metadata: MessageMetadata | null | undefined // Use the specific interface
   triggerElement?: React.ReactNode
 }