Cross-repo audit: bugs, typos, and broken links across Discord open-source repos

[Akenove]

Summary

Ran an audit across Discord's public repos and found several issues. Consolidating everything into one issue instead of opening multiple PRs.

Bugs

discord/linked-roles-sample

• Metadata key mismatch: register.js registers key as bakingsince but server.js pushes metadata as firstcookiebaked — linked roles silently fail to display
• Missing express.json() middleware: /update-metadata endpoint reads req.body.userId but no body parser is configured — always undefined
• Null token crash: updateMetadata() crashes with TypeError if user has no stored tokens

discord/access

• Broken notification URLs: Both notifications.py and notifications_slack/notifications.py generate /requests/{id} links for role requests, but the frontend routes them to /role-requests/:id — every notification link 404s (fixes Document channel-icons/ CDN endpoint #383)
• Typo: occured → occurred in modify_group_users.py:197 and modify_role_groups.py:197

discord/getting-started-activity

• No error handling on token exchange: server.js returns {access_token: undefined} when Discord API returns an error
• Package name typo: getting-starter-activity-server → getting-started-activity-server

discord/discord-interactions-js

• 4 missing component types: FileUpload (19), RadioGroup (21), CheckboxGroup (22), Checkbox (23) are in the API docs but not in the npm package
• No MODAL_SUBMIT test coverage: InteractionType 5 is the only type without a test case

Typos (discord-api-docs)

Already fixed via merged PRs #8198 and #8202:

• attache → attach
• Guilt Template → Guild Template
• prefered → preferred
• have have → have
• the the → the
• to to → to
• Missing space before inline code in gateway-events.mdx

Old Docs URLs

Multiple repos still reference discord.com/developers/docs/ instead of the new docs.discord.com/developers/ format. The old URLs 301 redirect so nothing is broken, but for consistency:

Repo	Count
discord-api-docs	187
discord-interactions-js	43
embedded-app-sdk-examples	20
discord-example-app	16
user-install-example	9
embedded-app-sdk	7
heroku-sample-app	5
linked-roles-sample	5
cloudflare-sample-app	4
avatar-remix-bot	3
getting-started-activity	2
social-sdk-unity-sample	2

Happy to submit PRs for any of these if helpful — just wanted to consolidate everything in one place first.

[Akenove]

Update: Deep Audit Results (discord-api-docs)

Ran a deeper scan across the docs. Here are the additional findings:

---

Invalid JSON Examples (21 blocks)

Multiple json code blocks fail strict JSON parsing. Most use // comments or ... ellipsis for documentation purposes — these should probably use the jsonc language tag instead.

File	Blocks	Issue
webhook-events.mdx	7	// user data comments
voice-connections.mdx	5	Trailing commas, ... ellipsis, "secret_key": [ ...251, 100, 11...]
rpc.mdx	1	C++ in JSON: "start": time(nullptr)
change-log.mdx	1	// Forward comment
permissions.mdx	1	Fragment JSON without wrapping {}
application-commands.mdx	1	Trailing comma
gateway-events.mdx	1	Comment in JSON
lobby.mdx, application.mdx, channel.mdx, user-actions.mdx	4	Comments in JSON

---

game-sdk.mdx: Avatar Field Missing Nullable

game-sdk.mdx defines avatar as string in two places (lines 597 and 1368), but user.mdx correctly defines it as ?string. Users without custom avatars return null.

---

Old Internal Links (199 occurrences)

After the docs reorganization in #8200, there are 199 references still using /developers/docs/ instead of /developers/. Most (179) are Social SDK class reference links in:

• using-unreal-engine.mdx
• using-c++.mdx
• lobby.mdx
• change-log.mdx

---

Broken GitHub Links (5)

Links pointing to the legacy-gamesdk branch that may not resolve:

• application.mdx:30 — GetTicket
• reference.mdx:364 — Achievement Icon struct refs
• game-sdk.mdx:311-313 — ApplicationManager methods

---

Code Block Language Inconsistency

Preferred	Count	Alternative	Count
js	288	javascript	51
py	42	python	31
cs	64	csharp	11

---

Happy to submit PRs for any of these — particularly the json → jsonc fix since that's mechanical and low-risk.