Skip to content

chore(kno-13491): clarify cross-platform payload overrides for Expo#1471

Merged
cellomatt merged 2 commits into
mainfrom
mk-kno-13491
Jun 3, 2026
Merged

chore(kno-13491): clarify cross-platform payload overrides for Expo#1471
cellomatt merged 2 commits into
mainfrom
mk-kno-13491

Conversation

@cellomatt
Copy link
Copy Markdown
Member

Description

This PR adds guidance on how to handle payload overrides when working with an Expo channel so that custom data will appear under notification.request.content.data regardless of which platform the recipient device uses.

@linear-code
Copy link
Copy Markdown

linear-code Bot commented Jun 3, 2026

KNO-13491

@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jun 3, 2026 8:36pm

Request Review

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk LOW: Adds a new subsection to the Expo push integration docs clarifying how to structure payload overrides so custom data is accessible on both iOS and Android via expo-notifications.

Reasons

  • Only a single .mdx content file is modified (content/integrations/push/expo.mdx)
  • Small diff: 22 additions, 0 deletions — well under the 50-line threshold
  • No new pages added, no sidebar or navigation changes
  • No component, layout, library, style, or config files touched
  • No dependencies or build configuration modified

Notes

  • Verify the external links to Expo and Firebase docs resolve correctly
  • Confirm the Liquid template syntax {{ data.url }} in the JSON code block renders as expected in the docs site
Open in Web View Automation 

Sent by Cursor Automation: Docs PR classifier

@cellomatt cellomatt merged commit dcdf7f7 into main Jun 3, 2026
6 checks passed
@cellomatt cellomatt deleted the mk-kno-13491 branch June 3, 2026 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant