Merge remote-tracking branch 'upstream/main'

Author: Lulalaby

docs/developer_tools/Embedded_App_SDK.mdx

@@ -175,6 +175,7 @@ Developers can use these commands to interact with the Discord client. The follo
 | [setActivity](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/setactivity)                                           | Modifies how your activity's rich presence is displayed in the Discord client            |
 | [setConfig](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/setconfig)                                               | Set whether or not the PIP (picture-in-picture) is interactive                           |
 | [setOrientationLockState](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/setorientationlockstate)                   | Set options for orientation and picture-in-picture (PIP) modes                           |
+| [shareLink](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/sharelink)                                               | Presents a modal for the user to share a link to your activity with custom query params  |
 | [startPurchase](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/startpurchase)                                       | Launches the purchase flow for a specific SKU, per the sku_id                            |
 | [userSettingsGetLocale](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/usersettingsgetlocale)                       | Returns the current user's locale                                                        |
 
@@ -691,6 +692,39 @@ await discordSdk.commands.setOrientationLockState({
 
 ---
 
+
+### shareLink()
+
+Presents the user with a modal to share a link 
+
+#### Supported Platforms
+| Web | iOS | Android |
+|-----|-----|---------|
+| ✅   | ⛔️  | ⛔️      |
+
+#### Required Scopes
+
+No scopes required
+
+#### Signature
+
+<Monospace>
+shareLink(args: [ShareLinkRequest](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/sharelinkrequest)): Promise\<[ShareLinkResponse](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/sharelinkresponse)\>\<void\>
+</Monospace>
+
+#### Usage
+
+```js
+const { success } = await discordSdk.commands.shareLink({
+  message: 'This message is shared alongside the link!',
+  referrer_id: 'some_referrer_id',
+  custom_id: 'some_custom_id',
+});
+success ? console.log('User shared link!') : console.log('User did not share link!');
+```
+
+---
+
 ### startPurchase()
 
 Launches the purchase flow for a specific SKU ID.
@@ -759,6 +793,7 @@ Developers may use the following events alongside the `subscribe()` SDK method t
 | [ACTIVITY_LAYOUT_MODE_UPDATE](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/activitylayoutmodeupdate)                     | Received when a user changes the layout mode in the Discord client                        |
 | [ORIENTATION_UPDATE](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/orientationupdate)                                     | Received when screen orientation changes                                                  |
 | [CURRENT_USER_UPDATE](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/currentuserupdate)                                    | Received when the current user object changes                                             |
+| [CURRENT_GUILD_MEMBER_UPDATE](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/currentguildmemberupdate)                     | Received when the current guild member object changes                                     |
 | [THERMAL_STATE_UPDATE](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/thermalstateupdate)                                  | Received when Android or iOS thermal states are surfaced to the Discord app               |
 | [ACTIVITY_INSTANCE_PARTICIPANTS_UPDATE](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/activityinstanceparticipantsupdate) | Received when the number of instance participants changes                                 |
 | [ENTITLEMENT_CREATE](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/entitlementcreate)                                     | Received when an entitlement is created for a SKU                                         |
@@ -943,6 +978,33 @@ Received when the current user object changes.
 
 ---
 
+### CURRENT_GUILD_MEMBER_UPDATE
+
+Received when the current guild member object changes.
+
+#### Required Scopes
+
+- identify
+- guilds.members.read
+
+#### Sample Event Payload
+
+```javascript
+{
+  "user_id": "7173771622812225536",
+  "nick": "beef_supreme",
+  "guild_id": "613425648685547541"
+  "avatar": "abcdefg",
+  "avatar_decoration_data": {
+    "asset": "abcdefg",
+    "sku_id": "123456789"
+  },
+  "color_string": "#ffff00"
+}
+```
+
+---
+
 ### THERMAL_STATE_UPDATE
 
 Received when Android or iOS thermal states are surfaced to the Discord mobile app.
@@ -1258,6 +1320,17 @@ No scopes required
 | deaf      | boolean                                             |
 | mute      | boolean                                             |
 
+#### GuildMemberRPC
+
+| Property                | Type                                                                                        |
+|-------------------------|---------------------------------------------------------------------------------------------|
+| user_id                 | string                                                                                      |
+| nick?                   | string \| null                                                                              |
+| guild_id                | string                                                                                      |
+| avatar?                 | string \| null                                                                              |
+| avatar_decoration_data? | [AvatarDecorationData](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/avatardecorationdata) \| null |
+| color_string?           | string \| null                                                                              |
+
 #### Image
 
 | Property   | Type   |
@@ -1398,6 +1471,20 @@ No scopes required
 | picture_in_picture_lock_state | [OrientationLockState](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/orientationlockstatetypeobject) |
 | grid_lock_state               | [OrientationLockState](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/orientationlockstatetypeobject) |
 
+#### ShareLinkRequest
+
+| Property    | Type           |
+|-------------|----------------|
+| message     | string \| null |
+| referrer_id | string \| null |
+| custom_id   | string \| null |
+
+#### ShareLinkResponse
+
+| Property | Type    |
+|----------|---------|
+| success  | boolean |
+
 #### Sku
 
 | Property       | Type                                                                  |
@@ -1604,4 +1691,4 @@ No scopes required
 | DLC          | 2     |
 | CONSUMABLE   | 3     |
 | BUNDLE       | 4     |
-| SUBSCRIPTION | 5     |
+| SUBSCRIPTION | 5     |

docs/interactions/Overview.mdx

@@ -45,7 +45,7 @@ A list of all message components and details on sending and receiving component
 
 ### Modals
 
-**[Modals](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-response-object-modal)** are single-user pop-up interfaces that allow apps to collect form-like data. Modals can only be opened in response to a user invoking on of your app's commands or message components.
+**[Modals](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-response-object-modal)** are single-user pop-up interfaces that allow apps to collect form-like data. Modals can only be opened in response to a user invoking one of your app's commands or message components.
 
 ![Modals in the Discord client](overview-modals.png)
 
@@ -169,4 +169,4 @@ On the **General Overview** page, look for the **Interactive Endpoint URL** fiel
 
 ## Handling Interactions
 
-Once your app is prepared for interactions, you can explore the [Receiving and Responding](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING) documentation which goes into the technical details of handling interactions requests in your app.
+Once your app is prepared for interactions, you can explore the [Receiving and Responding](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING) documentation which goes into the technical details of handling interactions requests in your app.

docs/quick_start/Getting_Started.mdx

@@ -502,6 +502,10 @@ const componentId = data.custom_id;
       // Get user ID and object choice for responding user
       // User ID is in user field for (G)DMs, and member for servers
       const userId = context === 0 ? req.body.member.user.id : req.body.user.id;
+
+      // User's object choice
+      const objectName = data.values[0];
+
       // Calculate result from helper function
       const resultStr = getResult(activeGames[gameId], {
         id: userId,

docs/quick_start/Overview_of_Apps.mdx

@@ -38,7 +38,7 @@ With the right API endpoints and proper [permissions](#DOCS_TOPICS_PERMISSIONS),
 
 ### Update user metadata and presence
 
-Apps can update a Discord's user metadata with data from a party game or app in a few ways.Apps can also update a user's profile with actionable data from a game or app by integrating **[Rich Presence](#DOCS_RICH_PRESENCE_OVERVIEW)**. Apps can also use **[role connection metadata](#DOCS_RESOURCES_APPLICATION_ROLE_CONNECTION_METADATA)** to associate third-party metadata (like stats or account type) with Discord users, which server admins can use to set up roles based on. You can explore more in the [configuring metadata for linked roles](#DOCS_TUTORIALS_CONFIGURING_APP_METADATA_FOR_LINKED_ROLES) tutorial.
+Apps can update a Discord's user metadata with data from a party game or app in a few ways. Apps can also update a user's profile with actionable data from a game or app by integrating **[Rich Presence](#DOCS_RICH_PRESENCE_OVERVIEW)**. Apps can also use **[role connection metadata](#DOCS_RESOURCES_APPLICATION_ROLE_CONNECTION_METADATA)** to associate third-party metadata (like stats or account type) with Discord users, which server admins can use to set up roles based on. You can explore more in the [configuring metadata for linked roles](#DOCS_TUTORIALS_CONFIGURING_APP_METADATA_FOR_LINKED_ROLES) tutorial.
 
 ### Add premium features
 

docs/resources/Audit_Log.md

@@ -71,7 +71,7 @@ The table below lists audit log events and values (the `action_type` field) that
 
 The **Object Changed** column notes which object's values may be included in the entry. Though there are exceptions, possible keys in the `changes` array typically correspond to the object's fields. The descriptions and types for those fields can be found in the linked documentation for the object.
 
-If no object is noted, there won't be a `changes` array in the entry, though other fields like the `target_id` still exist and many have fields in the [`options` array](#DOCS_RESOURCES_AUDIT_LOG/audit-log-entry-object-optional-audit-entry-info).
+If no object is noted, there won't be a `changes` array in the entry, though other fields like the `target_id` still exist and many have fields in the [`options` object](#DOCS_RESOURCES_AUDIT_LOG/audit-log-entry-object-optional-audit-entry-info).
 
 > info
 > You should assume that your app may run into any field for the changed object, though none are guaranteed to be present. In most cases only a subset of the object's fields will be in the `changes` array.