From b564bc75c212bca33a4398a7d2593feac37190f6 Mon Sep 17 00:00:00 2001 From: Andrew Giel Date: Thu, 23 Jan 2025 12:09:43 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Colin Loretz --- docs/activities/Development_Guides.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/activities/Development_Guides.mdx b/docs/activities/Development_Guides.mdx index c9a99fe9b6..27774d3792 100644 --- a/docs/activities/Development_Guides.mdx +++ b/docs/activities/Development_Guides.mdx @@ -898,7 +898,7 @@ Incentivized sharing can help grow your Activity through network effects. This g When implementing sharing, you'll need to: 1. Generate a unique ID for tracking the promotion -2. Call the `shareLink` command +2. Call the [`shareLink`](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/sharelink) command 3. Track the share attempt ```javascript @@ -966,6 +966,8 @@ async function handleReferral() { - Handle edge cases like expired promotions gracefully - Consider implementing cool-down periods between shares +--- + ### Preventing unwanted activity sessions Activities are surfaced through iframes in the Discord app. The activity website itself is publicly reachable at `.discordsays.com`. Activities will expect to be able to communicate with Discord's web or mobile client via the Discord SDK's RPC protocol. If a user loads the activity's website in a normal browser, the Discord RPC server will not be present, and the activity will likely fail in some way.