Conversation
- Added richContent optional field with image, audio, and video properties - Updated both the Convex schema validator and TypeScript types - Follows Expo push notification specification for rich content support Co-authored-by: ian <ian@convex.dev>
|
Cursor Agent can help with this pull request. Just |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
commit: |
- Updated generated component types to include richContent field - Added build:codegen npm script - Upgraded convex package to latest version - richContent supports image, audio, and video URLs for iOS notifications Co-authored-by: ian <ian@convex.dev>
|
@cursor can you merge in changes from main? |
|
❌ Unable to add follow-up after multiple attempts. The agent may be experiencing issues. Please try again later or Open in Web to view the status. Learn more about Cursor Agents |
|
The docs for the richContent field says: Currently supports setting a notification image. Provide an object with key image and value of type string, which is the image URL. Android will show the image out of the box. On iOS, you need to add a Notification Service Extension target to your app. See this example on how to do that. |
|
@cursor can we add any other missing fields? See https://docs.expo.dev/push-notifications/sending-notifications/#message-request-format Also, the richContent field has type |
|
❌ Unable to add follow-up after multiple attempts. The agent may be experiencing issues. Please try again later or Open in Web to view the status. Learn more about Cursor Agents |
Add
richContentfield to the notification schema to support rich media (image, audio, video) in Expo push notifications.