[Docs] Add in-depth guide for message reactions#2718
Merged
Conversation
18 tasks
heyitsaamir
reviewed
Mar 11, 2026
corinagum
force-pushed
the
feat/msg-reactions
branch
from
4e5c210 to
cb0b081
Compare
heyitsaamir
reviewed
May 8, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new in-depth documentation page for Teams message reactions and updates the “Sending Messages” essentials page to point to it, with new per-language include fragments for C#, Python, and TypeScript.
Changes:
- Add new in-depth guide page: “Message Reactions” (preview note, add/remove/receive, reaction IDs, skin tones, rate limits, best practices).
- Add new language include fragments with reaction code samples for TypeScript/Python/C#.
- Update “Sending Messages” essentials page to reflect preview status and link to the new guide; remove the old reactions preview-note include fragments.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| teams.md/src/pages/templates/in-depth-guides/message-reactions.mdx | New in-depth guide page covering message reactions concepts and guidance. |
| teams.md/src/pages/templates/essentials/sending-messages/README.mdx | Updates “Reactions” section to preview + links to the new guide. |
| teams.md/src/components/include/in-depth-guides/message-reactions/typescript.incl.md | TypeScript samples for adding/removing/listening to reactions + example IDs. |
| teams.md/src/components/include/in-depth-guides/message-reactions/python.incl.md | Python samples for adding/removing/listening to reactions + example IDs. |
| teams.md/src/components/include/in-depth-guides/message-reactions/csharp.incl.md | C# samples for reactions + experimental opt-in guidance. |
| teams.md/src/components/include/essentials/sending-messages/typescript.incl.md | Removes now-unused reactions preview-note section. |
| teams.md/src/components/include/essentials/sending-messages/python.incl.md | Removes now-unused reactions preview-note section. |
| teams.md/src/components/include/essentials/sending-messages/csharp.incl.md | Removes now-unused reactions preview-note section (moved to new guide). |
corinagum
force-pushed
the
feat/msg-reactions
branch
from
c13452a to
2dc2acc
Compare
MSFTRickyCastaneda
approved these changes
May 12, 2026
Contributor
MSFTRickyCastaneda
left a comment
MSFTRickyCastaneda
left a comment
There was a problem hiding this comment.
Looks good to me Corina, +1 to needing to publish the Teams Reaction Reference page once it's been live from Learn :)
Member
nickwalkmsft
left a comment
nickwalkmsft
left a comment
There was a problem hiding this comment.
I saw the recent review activity and so gave it a quick pass. Looks great!
corinagum
force-pushed
the
feat/msg-reactions
branch
from
2dc2acc to
dd92799
Compare
Collaborator
|
Ok to merge - waiting on green light from reactions / learn docs side. |
…r C#, Python, and TypeScript
Per project convention (#2735), C# handler lambdas take (context, cancellationToken) and thread the token through Send, Task.Delay, and SDK calls. The reactions guide didn't follow this. Uses named-arg form (cancellationToken: cancellationToken) for the reaction API calls because AddAsync / DeleteAsync have an optional AgenticIdentity parameter sitting between reactionType and the token. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
corinagum
force-pushed
the
feat/msg-reactions
branch
from
ffecbc0 to
42b1950
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an in-depth guide for message reactions covering outbound add/remove and inbound
messageReactionhandling, plus links the existing "Reactions" section in the Sending Messages essentials page to the new guide.What's covered in the guide
api.reactions.add/api.reactions.delete/Reactions.AddAsync/Reactions.DeleteAsync)messageReactionactivity handlers across all three SDKs, plus the .NET-onlyOnMessageReactionAdded/OnMessageReactionRemovedsub-handlerslike,heart,1f440_eyes,2705_whiteheavycheckmark,launch,1f4cc_pushpin)-tone1…-tone5)What's intentionally omitted
ApiClientconstructor that doesn't exist in the current SDK; removed rather than rewritten.Coordination
Send,Task.Delay, and reaction API calls).api.reactions.delete()ahead of microsoft/teams.ts#567, which renamesremove()→delete()to align with teams.py and teams.net.Test plan
npm startregenerates docs cleanly with no content gapsessentials/sending-messages→ in-depth guide resolves correctly