From f205c485738a9335dd17953815ad862713aa01ca Mon Sep 17 00:00:00 2001 From: knisaci Date: Tue, 19 May 2026 08:16:08 +1000 Subject: [PATCH] Clarify JSX usage in notifications expanded viewdocs: add note explaining JSX requirement for expanded notification view The notifications page switches from plain JS to JSX in the expanded view example without explanation, which can confuse new developers. Added a sentence clarifying that the content field requires JSX components such as Box and Text, with a link to the Custom UI docs for context. Fixes #2895 --- snaps/features/notifications.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/snaps/features/notifications.md b/snaps/features/notifications.md index 994c9a48144..1695f169066 100644 --- a/snaps/features/notifications.md +++ b/snaps/features/notifications.md @@ -67,6 +67,9 @@ Each Snap can trigger up to: In-app notifications can include an optional expanded view that displays when selected. The expanded view includes a title, [custom UI](custom-ui/index.md) content, and an optional footer link. +Note that the `content` field must use JSX components such as `Box` and `Text`. +If you are unfamiliar with JSX in Snaps, see the [custom UI](custom-ui/index.md) +documentation before proceeding. The following example displays a notification in MetaMask, with the message "Hello, world!" When the user selects the notification, the expanded view displays a page with a title, a paragraph, and a link to the MetaMask Snaps directory: